On Wed, Jun 4, 2008 at 12:41 PM, TL <[EMAIL PROTECTED]> wrote: > > Edward, please consider adding the following to your high-priority > ToDo list for Leo. > > Currently, Leo has some basic support for recording schedule estimates > and actuals using the Cleo plugin. Unfortunately, for many of the > @file types, all estimates and actuals assigned to an @file's sub- > nodes are not retained across Leo sessions. I think Leo should be > modified to retain node attributes for @Thin type sub-nodes and any > others if possible.
This is a FAQ, though perhaps it's not in the FAQ. Are you familiar with the discussion at: http://webpages.charter.net/edreamleo/customizing.html#adding-extensible-attributes-to-nodes-and-leo-files There was also a discussion at: http://groups.google.com/group/leo-editor/browse_thread/thread/52ee21143472840e# You can also search (in Google Groups) for 'unknownAttributes' for even more discussions. My point is simply this: there is no way to go beyond what Leo already provides. In fact, the whole "unified nodes" business was an attempt to finesse these questions, but it turned out that they remain anyway(!) In short, this is an ancient discussion that has played itself out. Edward --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
