Re: LeoWapp progress report

2018-11-04 Thread Edward K. Ream
On Sunday, November 4, 2018 at 4:48:18 AM UTC-6, Edward K. Ream wrote: > This response will be pre-writing for the info item #1011 : About Leo and flexx. I have now completed the first draft of #1011. It contains only minor edits. Edward

Re: LeoWapp progress report

2018-11-04 Thread Edward K. Ream
On Sat, Nov 3, 2018 at 3:21 PM Terry Brown wrote: Flexx is very different from other frame works because you write everything > in Python. You might try writing a web gui in Vue, React, or JQuery to get > something more typical. > Thanks for this. I am becoming convinced that flexx is exactly

Re: LeoWapp progress report

2018-11-03 Thread Terry Brown
Flexx is very different from other frame works because you write everything in Python. You might try writing a web gui in Vue, React, or JQuery to get something more typical. Cheers - Terry On November 3, 2018 3:11:12 PM CDT, "Edward K. Ream" wrote: >On Saturday, November 3, 2018 at 6:57:36

Re: LeoWapp progress report

2018-11-03 Thread Edward K. Ream
On Saturday, November 3, 2018 at 6:57:36 AM UTC-5, Edward K. Ream wrote: The skeleton defines browser-based wrappers for Leo's gui classes. The > skeleton is intended to be a common front end for frameworks such as flexx. > This organization does not look likely to survive first contact with

LeoWapp progress report

2018-11-03 Thread Edward K. Ream
The skeleton code in leo/plugins/leowapp.py is complete for now. All unit tests pass with --gui=browser. The skeleton defines browser-based wrappers for Leo's gui classes. The skeleton is intended to be a common front end for frameworks such as flexx. The BrowserGui class has a message method