I have barely begun using Android, so I know only a little about Android Outliner and NoteLynX. I have used both Android programs to read, modify, and create outlines that I also read, modify, and create using Leo-Editor.
I first tried exporting outlines in OPML from Android Outliner and importing them into Leo-Editor using read-opml-file. This worked fine. Exporting OPML from Leo-Editor using write-opml-file worked fine. But importing an OPML file into Android Outliner does not work correctly. As far as I can determine, there is no way to import an OPML file into Android Outliner and end up with any "Activity Notes" (corresponding to node body in Leo-Editor). In fact, Android Outliner does not round-trip OPML correctly! Now I export outlines in "Bonsai CSV (UTF-8)" from Android Outliner. 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. Since Android Outliner doesn't have clones, leo2aor.py just duplicates the Leo-Editor node each time it encounters a clone occurrence. Leo-Editor and Android Outliner make good partners. Unfortunately there is no way to make Android Outliner "sync" with a CSV file. So all my syncing is manual. 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. I wrote a script leo2nlx.py to generate a NoteLynX XML file from a Leo-Editor file. Since NoteLynX has clones, this script preserves clones. Unlike Leo-Editor, NoteLynX only allows one root node and it does NOT have a "hidden root node." So leo2nlx.py makes the Leo-Editor "hidden root node" the unique NoteLynX root node and it sets the "title" of this root node to the basename of the Leo-Editor file without the extension. 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. Tomorrow I may encounter a problem with Android Outliner or a benefit of NoteLynX that drastically changes my views, but right now my opinion is as stated above. -- 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.
