notes/tweaks...

Signed-off-by: Alex A. Naanou <alex.nanou@gmail.com>
This commit is contained in:
Alex A. Naanou 2023-12-18 17:21:55 +03:00
parent 430a6ce78d
commit 7904e8c42e
2 changed files with 4 additions and 1 deletions

View File

@ -1014,7 +1014,7 @@ var JSONOutline = {
// -> <elem> // -> <elem>
// //
// XXX move to config... // XXX move to config...
__code_attrs__: true, __code_attrs__: false,
parseBlockAttrs: function(text, keep=!!this.__code_attrs__, elem={}){ parseBlockAttrs: function(text, keep=!!this.__code_attrs__, elem={}){
if(typeof(keep) == 'object'){ if(typeof(keep) == 'object'){
elem = keep elem = keep

View File

@ -152,6 +152,9 @@ var setup = function(){
- do we need `.__code_attrs__` / `.__view_attrs__`??? - do we need `.__code_attrs__` / `.__view_attrs__`???
- handle attr delete correctly -- i.e. if shown attr removed from code -> delete attr... - handle attr delete correctly -- i.e. if shown attr removed from code -> delete attr...
- BUG? can't set `''` as attr value -- parser?? - BUG? can't set `''` as attr value -- parser??
- might be a good idea to render plugins in a separate block shown with code...
- _when attr added to code -> transfer to attrs block..._
- this will help with caret transfer to be more predictable...
- TOC: tweaking: add args like depth, ... -- as attributes... - TOC: tweaking: add args like depth, ... -- as attributes...
- TOC: should it be persistently generated as code and be serializable? - TOC: should it be persistently generated as code and be serializable?
- ASAP: expand sub-tree on follow link... - ASAP: expand sub-tree on follow link...