What do people imagine a 'Leo in the cloud' session would look like? I open a file which changes as I edit it, but also changes as others edit it? That sounds unsettling and not useful.
I can see a Leo file as the moral equivalent of a git working tree. I push my Leo file to a repository, others can clone it and make edits. I can fetch their edits, merge them or not. They do the same. The result is a file with history, tags and branches. A template file would include menus, buttons and commands to manage the git backend. Thanks, Kent On Sat, Mar 23, 2013 at 6:59 AM, Edward K. Ream <[email protected]> wrote: > On Wed, Mar 20, 2013 at 7:59 PM, David McNab wrote: > >> I'm writing now to ask what the thinking is regarding getting a >> cloud-ready version of Leo up and running. > > As Ville says, this is a perennial topic. And for good reason. This is one > of those "big questions" that it would be useful to discuss at length at the > Leo sprint. > > Another topic is best workflow practices. Kent and I are interested in > looking over Terry's shoulder for awhile :-) > > I would also like to discuss data base ideas. > >> Leo in the browser - here, it's well worth looking at the excellent >> Checkvist cloud-based outliner at www.checkvist.com. It's got some great >> cloud ideas Leo could borrow. > > I agree. It's impressive. > >> It's just a matter of whether Python in-browser frameworks like Pyjamas >> are up to the job, versus how hard it would be to implement Leo in >> <brain-haemorrhage>Javascript</brain-haemorrhage> > > CoffeeScript, http://coffeescript.org/, is the proper way to program in > JavaScript. It should not cause any brains to explode. Importantly, there > are tools that will convert JavaScript to CoffeeScript. I would want to do > this conversion before studying existing code. > > Having said this, programming directly in CoffeeScript looks like an > "heroic" approach. Checkvist proves that such an approach is possible. > Perhaps someone could convert Checkvist to CoffeeScript automatically, and > then relatively easily move on to Leo. But unless somebody in the Leo > community actually has a *lot* of time on their hands, basing a project on > CoffeeScript isn't likely to make much headway. > > This leaves us with the question of in-browser frameworks. I haven't paid > any attention to this important topic. I imagine that there has been > continuous incremental (or revolutionary) progress since last we looked > around. I would like to explore the possibilities at the Leo sprint. > > These are just my thoughts. Feel free to suggest new ideas here, or to > bring up new topics at the sprint. There won't be any formal agenda. > > 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?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- 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.
