Hi all, I'm wondering what thought has gone into making Leo cloud capable, whether by:
- Implementing regular polling of the .leo file, reverting from the file if a newer version of the .leo file is detected (suitable for file sync cloud setups like Dropbox), or - Implementing a browser-based leo-like editor written in <brain-haemorrhage>javascript</brain-haemorrhage> which can import/export .leo files, but stores nodes on a server, or - Having the normal Leo desktop client store its nodes on the web, perhaps with the help of some server-side code which users can set up to run under Apache. I'm feeling that the use of a .leo file as the *primary* means for outline storage has over time has turned from Leo's strength to Leo's biggest weakness. The .leo xml format is great for import/export, but I suggest that Leo should be capable of storing its nodes as database rows, or as web objects, or other forms that can work with the cloud. For interest, I recommend looking at the Checkvist<http://www.checkvist.com>online outliner. It misses all of Leo's real killer features, but for what it is, it's brilliant and can offer some ideas to Leo's future evolution. Thoughts? Cheers David PS I just used Leo to construct a long university essay. Wonderful it was to have the various pieces sitting in nodes where I could see the high-level structure and freely rearrange at will. Just another way that Leo has helped me massively over the last decade! :) -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
