On Thu, Apr 16, 2015 at 9:57 AM, Edward K. Ream <[email protected]> wrote:
> For the first time, *I can find to-do items and scripts easily*...Clones play no part in this discussion. Indeed, using clones may be a symptom of poor organization. Some further thoughts about clones: I think of the wishlist to-do list as the primary data. Each wishlist item should appear exactly once. We don't want clones in multiple places in the primary data! And we don't want clones anywhere in scripts.leo, for much the same reasons that we don't want clones in LeoDocs.leo and leoSettings.leo. Clones *could *be used to create an alternate view of the wishlist data, but the alternative view should exist *outside *the primary data. For example, I could clone all the starred (important) to-do items and move them outside of the primary to-do list. In this respect, the primary wishlist to-do list is much like an @file node. We typically don't want multiple clones in either place. In fact, however, there is not much need for a separate view of important wishlist items. They typically get promoted out of the wishlist section and into the to-do items for a particular release. That's plenty good enough. *Summary* I'll continue to use clones. For example, when working on a to-do item I almost always clone it so it is ready to hand. However, the recent Aha's show (to my satisfaction) that clones should not be used in creating an initial organization of any kind of data. This is quite a surprise to me. Your comments, please, Amigos. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
