On Sun, Apr 10, 2011 at 5:41 AM, Kent Tenney <[email protected]> wrote:
> - 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. c.db should be this "companion file". This has been agreed to get done eventually, but didn't happen so far. You should file a wishlist item so it wont get lost/forgotten. > - 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. Also agreed earlier, file a wishlist item :). > - use one of the "standard" types of ID for the node, such as a UUID I think gnx should be arbtitrary string and you should be able to specify it in code (p.gnx="hello") > - offer the capability to use .ini style files to configure Leo I'd like this as well. > 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. Don't necessarily agree with this. Once headlines are in tnodes, you can ignore the vnode segment anyway. Also, many nodes are meaningless without tree structure (e.g. @file nodes under @path nodes etc). -- 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.
