On Saturday, June 29, 2013 7:33:35 AM UTC-5, Edward K. Ream wrote: > > On Wed, Jun 19, 2013 at 1:59 PM, David McNab <[email protected]>wrote: >
> The whole computing world is headed into the cloud, and if Leo is to stay >> relevant, it needs to go there as well. >> > > I have mixed thoughts about this. If we could magically make Leo work in > the cloud, then that would be great. However, I don't want to maintain two > code bases, one in js and one in python. And nobody else will want to > maintain two code bases either. > When I wrote this reply I missed the fact that the approach is based on the Leo bridge, which contains all of Leo's core. So Terry's way would *not* seem to require Python in js, at least not write away ;-) 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/groups/opt_out.
