On Wed, Mar 18, 2009 at 1:56 AM, Edward K. Ream <[email protected]> wrote:

> An interesting idea.  Maybe @temp would be more descriptive.  The problem I
> see, however, is lost data if somebody innocently puts data in an @temp
> tree.

Perhaps it should not depend on the headline but some hidden attribute
(to facilitate various temporary data created by plugins).

E.g. a leo node that contained process list and allowed users killing
/ exploring processes should definitely be temporary (since all the
data is created by plugin), but there probably shouldn't be a parent
@temp item cluttering the tree.

We can easily flag the temporary nodes, e.g. by using different icon
or color. The write code can sanity check the tree, and warn user if
there are non-temporary items under temporary items. insert-node can
also warn the user if any parent is temporary.

-- 
Ville M. Vainio
http://tinyurl.com/vainio

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

Reply via email to