A possibility could be to specify a schema for a given json file indicating how 
to structure the document. That would expand the possibilities for Leo to 
handle flat-file hierarchical datasets for applications like bookmarks manager, 
bibliographies, etc. A similar concept is implemented in 
http://treeline.bellz.org, I believe using (less human readable) XML files. 
Just an idea...

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Reply via email to