All of us spend a huge amount of time polishing Leo's look and feel. This is natural, because this is what we see, all the time.
For me, though, Leo's gui is of secondary importance. For users, what makes Leo special are outlines and clones, and closely related features such as the clone find commands. Behind the scenes, what makes Leo special are true python objects for nodes, and closely related features such as per-node uA's. These special features are what I most want to expand and explore. However, other interesting projects beckon, especially the JavaScript world. There probably has been far more engineering work done on JS infrastructure than Python infrastructure. Joe Orr's demo <https://kaleguy.github.io/leovue/#/t/2/> shows just how powerful the overall JS platform has become. Otoh, exploring the JS world might quickly embroil me in a JS version of Leo's gui. Yes, we already have LeoWapp (Leo as a web app, aka, Leo in a browser). However, I'm not sure this is restful enough for Joe, whatever "restful" means... *Summary* Imo, thinking outside the gui box offers the greatest opportunities for useful invention. The JS world beckons, but I don't want to do a new JS gui! WebAssembly may offer a way to get the advantages of JS within Leo's present Python platform. That's probably a year or more away. I won't jump into a major JS project until then. All comments and suggestions welcome. 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/7c1ae50c-65d8-40bf-8994-3798703d8dd2%40googlegroups.com.
