Recent revs contain a major reorg of Leo's internal to-do list. All items have been moved to one of three categories: move to issues, unlikely or won't do. I'll be creating new issues today.
The "Unlikely" and "Won't do" categories will remain "forever". They document ideas that I have rejected, for the reasons stated. There are some gems in the new issues: - Miles Fidelman, HansBKK and the late Bernhard Mulder propose tools for collaborative .leo files. At least two of the proposals mention TiddlyWiki <https://tiddlywiki.com/>. - Ville proposes using Travis CI <https://travis-ci.org/> to support continuous integration in Leo. - Terry proposes rendering outlines to a canvas <http://leo.zwiki.org/GraphsInTree> and supporting cmap <https://cmap.ihmc.us/>. - Several people, including me, suggest that cross-file searches would work around the lack of cross-file clones. This idea has more force now that Leo boasts various clone-find command. - Kent proposes using pyfilesystem <https://docs.pyfilesystem.org/en/latest/>. - jasonc proposes various ways to produce more flexible output from Leo. 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
