A few thoughts on Leo's file format with the goal of making it more generic.
- declare a Leo namespace for the file - make uA's plain text by default currently they are pickles by default, need special naming to be written as text - move the session-specific stuff to a companion file the <globals> tag describes size and position data which could be stored elsewhere the a="E" attribute reflects if a node is expanded. VCS can report changes even though the file was only viewed, not edited. - make the headline text known in the <t> node currently, the <v> node knows the headline, the <t> node knows the body, they must be joined using the node ID, an unnecessary complexity. - use one of the "standard" types of ID for the node, such as a UUID - offer the capability to use .ini style files to configure Leo With these changes, the .leo file would provide a more generic datastore: the <t> nodes are a set of name:value pairs (headline:body), the <v> nodes describe how they are arranged. The sidecar file describes how the tree should look when opened. The extreme of generisizing could involve putting the <v> nodes in a companion file. This would allow Leo to embrace any set of key/value pairs, providing the full set of tools for viewing, manipulating, analyzing, ... the data while allowing the data to remain in it's native format. Thoughts? Thanks, Kent -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
