Re: attributes in thin files (was Re: Using icons to show status)
On Mon, Jun 30, 2008 at 9:59 PM, Terry Brown [EMAIL PROTECTED] wrote How about this... unknownAttributes may contain a dict called persistent or leo_persistent which, if present, is saved on the nodes... no other attributes are saved. (in the node's sentinel) So, using the cleo time required / progress example, cleo would have to (a) write info. entered by the user such as time required and progress into this dict (unknownAttributes[leo_persistent][cleo][time_required] and unknownAttributes[leo_persistent][cleo][progress]) and (b) cleo would need to regenerate icons outline wide on loading, seeing icons aren't in leo_persistent. I think the solution could work because plugins would have to make a conscious effort to put things in leo_persistent, which addresses the problem of is this attribute important or not? which is really the issue with attributes and @thin nodes. Technically, using a new uA could work (it could be made to work). However, I think this is still a dubious solution. The problem is that @thin is for situations where we want to minimize changes to the repository, and any extra attributes written to the thin derived file would work against this. @file is better than @thin when the user doesn't care about bzr/cvs conflicts: the derived file is simpler (simpler sentinels) and the outline contains all structure/attribute data. So a new option: this attribute is important isn't going to add much: we can't write any attributes to thin derived files, and we can write all attributes when using @file. In other words, the fundamental choice is whether one cares about the repository or not. Edward --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: attributes in thin files (was Re: Using icons to show status)
Digging up my own email so I don't forget it - I think the below is a solution for the sentinels in @thin files issue? - Thin files are supposed to play nice with VCS - Trivial changes to outline attributes (node visibility etc.) aren't compatible with this. - This keeps the trivial changes out by ensuring the user/plugin has to identify the changes as important (worth the VCS noise). On Tue, 24 Jun 2008 15:13:49 -0500 Terry Brown [EMAIL PROTECTED] wrote: How about this... unknownAttributes may contain a dict called persistent or leo_persistent which, if present, is saved on the nodes... no other attributes are saved. (in the node's sentinel) So, using the cleo time required / progress example, cleo would have to (a) write info. entered by the user such as time required and progress into this dict (unknownAttributes[leo_persistent][cleo][time_required] and unknownAttributes[leo_persistent][cleo][progress]) and (b) cleo would need to regenerate icons outline wide on loading, seeing icons aren't in leo_persistent. I think the solution could work because plugins would have to make a conscious effort to put things in leo_persistent, which addresses the problem of is this attribute important or not? which is really the issue with attributes and @thin nodes. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: Using icons to show status
Cool. # beforeBox beforeIcon beforeHeadline afterHeadline I hadn't realized these options were available, thank you for pointing them out. Bob On Jun 23, 9:24 pm, Terry Brown [EMAIL PROTECTED] wrote: Just posted this: http://leo.zwiki.org/ShowStatus ...icons to indicate status of nodes in a hierarchy where nodes may be inactive or active, or in an error state, or any number of states. Cheers -Terry --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: Using icons to show status
The ShowStatus approach of setting icons based on a node's text raises the possibility of a solution to the problem of retaining the Cleo's project estimates and % complete information in the sub-nodes of @thin file nodes across Leo sessions. Have Cleo keep a record of the project status within a comment in the node's text which can be read the next time the Leo file is loaded to restore the settings. TL --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: Using icons to show status
On Tue, 24 Jun 2008 01:56:54 -0700 (PDT) bobjack [EMAIL PROTECTED] wrote: # beforeBox beforeIcon beforeHeadline afterHeadline I hadn't realized these options were available, thank you for pointing them out. I'm not sure if they're all implemented, perhaps just beforeIcon and beforeHeadline. Cheers -Terry --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: Using icons to show status
On Jun 24, 2:44 pm, TL [EMAIL PROTECTED] wrote: The ShowStatus approach of setting icons based on a node's text raises the possibility of a solution to the problem of retaining the Cleo's project estimates and % complete information in the sub-nodes of @thin file nodes across Leo sessions. Have Cleo keep a record of the project status within a comment in the node's text which can be read the next time the Leo file is loaded to restore the settings. TL Interesting idea, but the body text is part of the tnode, so I don't think this is any different from putting the attributes on the tnode instead of the vnode. Not that I know, it's all greek to me ;) Bob --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: Using icons to show status
On Tue, Jun 24, 2008 at 2:09 PM, Terry Brown [EMAIL PROTECTED] wrote: But the main idea is that @thin trees have no descendant v elements: Leo builds the outline solely from the thin derived file. Ok, that makes sense. But if you wanted to store attributes, wouldn't it just be a matter of writing base64 and or pickled attributes into the sentinels which delimit the nodes in the derived file? With the benefit of complete ignorance of this part of Leo's core, it sounds not too complicated? This has nothing to do with programming, and everything to do with what @thin is supposed to do. The whole point of @thin is to make it as friendly as possible for bzr, cvs, etc. So we *must not* write inessential attributes in any form to thin derived files. Doing so would create lots of conflicts. That's why the hidden machinery exists. Edward --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com 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 -~--~~~~--~~--~--~---
attributes in thin files (was Re: Using icons to show status)
On Tue, 24 Jun 2008 14:49:33 -0500 Edward K. Ream [EMAIL PROTECTED] wrote: With the benefit of complete ignorance of this part of Leo's core, it sounds not too complicated? This has nothing to do with programming, and everything to do with what @thin is supposed to do. The whole point of @thin is to make it as friendly as possible for bzr, cvs, etc. So we *must not* write inessential attributes in any form to thin derived files. Doing so would create lots of conflicts. That's why the hidden machinery exists. Ah ha. So the issue is, for those that care about attributes in thin files, can you use @file instead... or is the bloat in the .leo file too much? If so, is it worth having a config. setting to enable writing of particular attributes (perhaps just unknownAttributes?) to the thin file, bearing in mind the cost in terms of messy diffs in VCS etc.? Trouble is unknownAttributes can still receive outline wide trivial changes that are going to be a pain in VCS. Icons... are stored in unknownAttributes, BTW. How about this... unknownAttributes may contain a dict called persistent or leo_persistent which, if present, is saved on the nodes... no other attributes are saved. So, using the cleo time required / progress example, cleo would have to (a) write info. entered by the user such as time required and progress into this dict (unknownAttributes[leo_persistent][cleo][time_required] and unknownAttributes[leo_persistent][cleo][progress]) and (b) cleo would need to regenerate icons outline wide on loading, seeing icons aren't in leo_persistent. I think the solution could work because plugins would have to make a conscious effort to put things in leo_persistent, which addresses the problem of is this attribute important or not? which is really the issue with attributes and @thin nodes. Cheers -Terry --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com 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 -~--~~~~--~~--~--~---
