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
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
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
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
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
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.
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
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
