There is certainly a lot to think about here. As Edward stated, keeping up with the Javascript world is a daunting task if you've already deeply immersed in a whole other world.
To address your OP, there is currently a long term goal of investigating using Flexx to build a web-based GUI for Leo <https://github.com/leo-editor/leo-editor/issues/338>. It's definitely long term, there are plenty of other priorities in Leo's core. I encourage you to take a look at Flexx as well as the JS GUI Widget framework it is built on, Phosphor <https://github.com/phosphorjs/phosphor>. While Phosphor is not yet super popular I predict its popularity will rise when JupyterLab <https://github.com/jupyterlab/jupyterlab> (which is also built on Phosphor) comes out of alpha. As you can see there is a strong desire in the Python universe to harness web-based GUIs. If you plan on using Vue and your project grows to any reasonable size then I encourage you take a look at Vuex <https://vuex.vuejs.org/en/intro.html> which offers some tools and constructs to help organize Vue projects. On Monday, March 6, 2017 at 5:36:19 AM UTC-5, Joe Orr wrote: > > Thanks for the welcome back! > > A few more thoughts on this topic: > > Cool trees is D3 v4: > https://bl.ocks.org/mbostock/e9ba78a2c1070980d1b530800ce7fa2b > https://bl.ocks.org/mbostock/4063550 > > I'll get the Leo Viewer project up and running within a week or so on > Github. > > I'm currently working in full stack node development with Angular / Vue on > front end + D3 at moment so I should be able to leverage some of that. Vue > seems better for this project than Angular. > > I'm thinking the Leo Viewer could be used to generate some nice display > examples from Leo generated content. Could be a good way to introduce more > people to Leo. Besides D3 there are other HTML5 components that could be > added fairly easily. For example I'm also thinking it would be cool to have > reveal.js make a slide show out of a subtree. > > Once the viewer is useful, it is simple to make an Electron version, which > makes it a complete cross platform desktop app: > https://electron.atom.io/ > > And once that is working, the viewer could become an alternate front end > to the existing Leo program by wrapping Leo in a node server. Node can talk > to Python. > > Another thing to think about down the road is making a version of Leo from > Atom, basically a similar technique (wrap Python in node). > https://github.com/atom/atom. Already thought of a good name for it: @Leo > :-) > > Joe > > > > On Monday, March 6, 2017 at 5:06:25 AM UTC-5, Edward K. Ream wrote: >> >> >> >> On Mon, Mar 6, 2017 at 3:57 AM, Edward K. Ream <[email protected]> wrote: >> >>> On Mon, Mar 6, 2017 at 3:44 AM, Joe Orr <[email protected]> wrote: >>> >>>> D3 demo: >>>> https://bl.ocks.org/kaleguy/57266b6fff9f864403e007e9efd06401 >>>> >>>> Excellent! >>> >> >> I've just purchased the ebook you referenced: d3.js tips and tricks. >> One reason I did so was to test out the leanp >> https://leanpub.com/bookstoreub distribution. Impressive. >> >> I guess I have to resign myself to always being a bit behind >> <https://groups.google.com/d/msg/leo-editor/E094jyjF0c8/1uIoxOFoDwAJ>. >> >> 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.
