On Sun, Feb 1, 2015 at 1:31 PM, SegundoBob <[email protected]> wrote:
I wrote a script aor2leo.py to generate a Leo-Editor file from a "Bonsai > CSV (UTF-8)" file. I wrote another script leo2aor.py to generate a "Bonsai > CSV (UTF-8)" file from a Leo-Editor file. > Are you willing to share these scripts? leo/scripts/scripts.leo would be a good place for them. I'll put them there if you like: just send me the scripts or include them here. Leo-Editor and Android Outliner make good partners. > Thanks for this research. I have a program that compares Leo-Editor files. This will allow me to > merge changes when I make changes to the same file using Android Outliner > and Leo-Editor--as soon as the bug described in Issue #130 is fixed. > Could you share this program as well? It could be extremely important, as I shall now explain. There is another use for a program that compares Leo files. If suitably easy to use (integrated into Leo), it could be the foundation for using @nosent files instead of @shadow files. The idea is to run the outline-compare program (script) when the tree in an an @nosent tree does not exactly match the corresponding external file. This would be kinda like what @shadow's read algorithm does, but with the following subtle, but important differences: 1. No duplicate hidden file is written when writing the @nosent node. 2. [Maybe] The user is always made aware of the differences. 3. The user is in complete charge of how to resolve ambiguous updates: changes that fall at the end of one node or the beginning of the next. 4. [Maybe] The diff algorithm (in your script) will be simpler than the diff algorithm in the @shadow code. Using @nosent should be more intuitive, simpler and faster than @shadow. This is something I definitely want to explore. Crucially, this scheme preserves both node identities (gnx's) and clone links because both are stored in @nosent trees in the .leo file. **Important**: Leo already has several flavors of outline-comparisons, but none of them are simple enough to be the basis of an automatic update of @nosent files. We want something as easy to use and understand as the best external diff/merge programs, such as the diff used in git clients such as SourceTree. I wrote a script leo2nlx.py to generate a NoteLynX XML file from a > Leo-Editor file. > Again, I would like to put this script in scripts.leo. > I stopped investigating NoteLynX when I couldn't find a way to rearrange > the "projects" (outlines) in the Project Main Menu, and, much more > seriously, I discovered that line breaks are ignored in the node body. > Also, I think the Android Outliner displays are better than the NoteLynX > displays. > This kind of "negative result" is good to know. Many thanks for your details description of the issues involved. 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.
