On Saturday, October 27, 2018 at 10:22:54 AM UTC-5, Edward K. Ream wrote: > This post is intended for Leo's devs, especially Joe Orr. This post explains why the design must be as it is.
I should state explicitly that the ultimate goal is to support turn LeoVue into LeoWapp. This will proceed in stages: 0. Create leowapp.py from mod_http.py. 1. Add a log pane and minibuffer to the web page created by leowapp.py. The look of the web page will be simplistic, as it is in mod_http.py. I'll spend little or no time on visual niceties, because LeoVue's code will eventually replace all such code. 2. Using the log panes in Leo and the web page, prototype the private api, that is, the two-way communication between Leo and the browser. On the python side, a few lines of code might implement the entire High Level Interface. That is, a single getattr might redirect calls to a method that creates messages to be sent to the web page. The python code must also handle events generated by javascript. These events can't be redirected. It's unclear how many event there will be. 3. Get all (most) unit tests working when using --gui=browser. At this point, LeoWapp will be functional, but it will not look like LeoVue. 4. Use LeoVue's javascript instead of the temporary javascript in leowapp.py. Details unclear. This is just a general road map. It may change considerably. 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.
