Re: LeoWapp plans
> > Matt, I'm not sure how this will affect your distro work. I do know that > the following pulls in a lot of packages: conda install flexx -c > conda-forge > It looks pretty straightforward, but maybe I'll wait until we know if flexx is more than an experiment before adding it as a requirement. Pip is good at adding dependent packages on install, but it doesn't remove them when the master package is uninstalled. Matt -- 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: Might be interesting for Leo WebApp
Enhancement request done! https://github.com/leo-editor/leo-editor/issues/1010 -- 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: LeoWapp progress report
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 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 >the >flex classes. Still, I'm glad to have done what I did first. It will >serve as a history. > >It's time to integrate the skeleton with a framework. I'll start with >> flexx. This will show where the skeleton needs more work, perhaps >even a >> rethink. >> > >A rethink is likely, but that does not bother me. The flexx way may be > >simpler than what I had envisioned. In any case, the present classes >in >leowapp.py can be changed easily. > >The flexx work will be done in a new flexx branch. I'll update the >> skeleton branch as needed. >> > >I'll probably continue to do work in the skeleton branch. Rather than >create a new branch, I'll create a new plugin, say leoflexx.py. A few >tweaks to the gui-related startup code in leoApp.py should suffice to >choose between various options for --gui=browser. > >This scheme should be more convenient than switching between different >branches. Instead, I'll just work on leoflexx.py, and update >leowapp.py as >appropriate as my ideas evolve. > >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 https://groups.google.com/group/leo-editor. >For more options, visit https://groups.google.com/d/optout. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: LeoWapp progress report
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 the flex classes. Still, I'm glad to have done what I did first. It will serve as a history. It's time to integrate the skeleton with a framework. I'll start with > flexx. This will show where the skeleton needs more work, perhaps even a > rethink. > A rethink is likely, but that does not bother me. The flexx way may be simpler than what I had envisioned. In any case, the present classes in leowapp.py can be changed easily. The flexx work will be done in a new flexx branch. I'll update the > skeleton branch as needed. > I'll probably continue to do work in the skeleton branch. Rather than create a new branch, I'll create a new plugin, say leoflexx.py. A few tweaks to the gui-related startup code in leoApp.py should suffice to choose between various options for --gui=browser. This scheme should be more convenient than switching between different branches. Instead, I'll just work on leoflexx.py, and update leowapp.py as appropriate as my ideas evolve. 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
LeoWapp progress report
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 that passes "payloads" to the browser. Payloads are dicts, which will probably be converted to json. Each payload has a 'kind' entry and zero or more other entries. How payloads get sent to a framework depends, of course, on the framework. Work has been straightforward. Surprisingly, running all unit tests generate only calls to gui.message(kind, **kwargs) for the following kinds: 'body-get-all-text', 'do-dialog', 'get-clipboard', 'set-clipboard', 'get-focus', 'set-focus', 'get-y-scroll' I would have expected many more. I'm not sure what this means, but there is nothing to worry about now. At worst, the skeleton may be missing a class or two. *Summary* It's time to integrate the skeleton with a framework. I'll start with flexx. This will show where the skeleton needs more work, perhaps even a rethink. The flexx work will be done in a new flexx branch. I'll update the skeleton branch as needed. Expect a working flexx prototype in a day or three. 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
