On Thu, Sep 19, 2013 at 6:19 PM, Edward K. Ream <edream...@gmail.com> wrote: > There are two reasons why Leo is unlikely ever to be a web app. > > 1. There are somewhere around a million lines of Python code in Leo's core > and plugins. Thus, a *solid* python in javascript system is required. This > isn't likely to happen. > > 2. Creating a Leo outline widget is extremely complex. Even starting with a > working javascript outliner, one has to deal with events (commands) coming > from Leo scripts rather than from the user.
I wonder how well Kivy would do? http://kivy.org/docs/gettingstarted/events.html Seth > These seem like the most important obstacles. There may be others, but this > suffice ;-) > > 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 leo-editor+unsubscr...@googlegroups.com. > To post to this group, send email to leo-editor@googlegroups.com. > Visit this group at http://groups.google.com/group/leo-editor. > 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
