On Wed, Feb 4, 2015 at 11:40 AM, Edward K. Ream <[email protected]> wrote:
> On second thought, I am going to abandon the gui-based approach for now. If updating an @nosent file creates nodes automatically, and also creates a summary of the changes (using clones), then @nosent becomes a viable candidate for replacing @auto as well as @shadow. Indeed, @nosent promises the following advantages: 1. Unlike @auto, the .leo file preserves node identity, so clone links are preserved. 2. Updating @nosent files will be very fast. Usually, there will be no changes, so nothing has to be done except compare the external file with the file that the @nosent tree will generate. Reading the external file into a string is super fast, as is writing the @nosent tree to a string. 3. Writing @nosent files will be at least twice as fast as writing @shadow trees, because only the external file (containing no sentinels) gets written. True, the entire @nosent tree must be written to the .leo file when saving an outline, but that will not take much *additional* time. This is very exciting, and I see no big problems in implementation. I'll be working on this in the next day or so... The new @nosent could reasonably be expected to cause the deprecation of both @auto and @shadow. We'll see when we have something real to play with. @nosent will never replace @file, which will always be the best form for external files when sentinels are acceptable. 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.
