I will have to think about this more, but in general it seems like a natural progression: TK --> QT --> browser. The browser is the most advanced interface available. I'm assuming that was the thinking behind ipython's notebook. Advanced Leo plugins would be simpler to build under a browser, mainly because there is so much technology already built into and around browsers. And it means as well that, with some tweaking, data and applications could be shared across the network.
I did an exercise for a Coursera python course (Interactive Python): http://www.codeskulptor.org/#user25_OYhY8H7kpx_47.py. The fact that python is in the browser means it can be shared easily, built easily, and even co-programmed easily (you can use that link's code and save another version --it generates a new link for each save). You could image Leo applications built and shared like that... just point Leonistas to a site and they get a plugin...(a bit scary, but there would be ways to make it safe, I'm assuming...) My knowledge of Leo doesn't allow me to write anything similar in Leo (ok, why would I want BlackJack in Leo? Just an example!), and I suspect that even if I knew QT well, it would not be easy to build that application, which I did without much training at all. (Of course, this was almost a fill-in-the-blank assignment..) But there are more useful cases that fall into the "difficult to do in Leo" (for me): I want to diff two nodes and then interactively update one version using the other -- a kind of interactive bzr conflict resolution, but the two files are in body text with no markup. I can do the diff easily enough, but any kind of interactive editing of parallel texts is beyond me under Leo. So I use Meld instead, outside Leo. Or I could generate a html file with the diff data from Leo and that would include a bit of javascript for editing the aligned texts. That would work, but I want to get the manual changes back to Leo. Difficult, but your plugin makes it look doable. That's where a Leo --> browser --> Leo interface (much like the ipython bridge) would be useful: allowing whatever might be done more easily in the browser to be stored in Leo and then (possibly) reworked in Leo and back to the browser... etc. I suppose I am talking about an Ajax Leo...., but I don't know what that means! Best, Bill On Friday, 22 November 2013 12:35:08 UTC-8, Terry wrote: > > On Fri, 22 Nov 2013 12:21:28 -0800 (PST) > wgw <[email protected] <javascript:>> wrote: > > > Yes, +Like from me too for this plugin (shame Google groups doesn't have > a > > "like" feature for posts... unless there is a g+ Leo group?), > > and tantalizingly reminiscent of ipython's notebook. .... if there were > a > > way to make this two-way and sync with a Leo Notebook, then Leo could > take > > advantage of browser power, like ipython. > > Two way's not that hard, or at least it's doable, not sure if it's > still fully functional, but the pygeotag extension basically > establishes two way communication with the browser for interactively > showing / selecting coordinates on a Google map. > > But apart from that particular application (a web map), what would Leo > want to do with two way communication? It's easy to make the browser > display things for you, as long as you don't mind closing the tabs > yourself. > > Cheers -Terry > > > Of course that is a big project, and much of the value is largely found > in > > the viewrendered plugin... and others. > > > > Thanks! > > > > Bill > > > > On Thursday, 21 November 2013 15:04:44 UTC-8, Fidel N wrote: > > > > > > Wow I finally got around to make this work, and its very very > impressive, > > > thanks for this! > > > > > > Do you think it could easily be tweaked to store all the open tabs on > the > > > selected web-browser? > > > This way we could use Leo to store our webbrowser sessions (and a > button > > > to restore the session from Leo is very straight fordward). > > >> > > >> > > > -- 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
