On Monday, March 6, 2017 at 7:52:43 AM UTC-6, john lunzer wrote: The differentiating factor in using Flexx rather than building the UI > elements directly in Javascript is the "talking to" part. The Flexx UI > Framework has built up a robust two way communication system between Python > and JS which I think would be difficult to replicate. >
That sounds extremely useful. This is going to be the year of client/server Leo. How that plays out is mysterious at present. wouldn't [you want] to spend your personal time on something where a > reasonable solution may already exist. > Oh yes, definitely. Although if you're more comfortable in JS than Python Flexx may be a > non-starter. > Hehe. As much as possible of Leo's existing python code must remain. I'll reject any proposal to rewrite, say, leoAtFile.py or leoNodes.py in js. Leo is, after all, about Python first. A browser-based gui does have advantages. For example, atom supports many languages. (Do Ctrl-Shift-L to see them.) Atom proves that syntax coloring in js can be very fast. Furthermore, Atom's syntax coloring supports true solarized colors. That is, selected text is shown correctly. 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.
