On Tue, 6 Feb 2018 11:31:54 -0600 "Edward K. Ream" <[email protected]> wrote:
> On Tue, Feb 6, 2018 at 10:57 AM, Terry Brown <[email protected]> > wrote: > > I can buy a new computer, connect it to the > > internet, and go to: > > > https://kaleguy.github.io/leovue/#/t/1 > > > > and I'm using Leo on the web... except it's read only. > > No, you are just accessing a web page. Well, ok, I'm accessing something that's entirely client side and has no Python process, but I'm talking about the user workflow, not the implementation. > > I think any > > > > read / write browser interface for Leo must provide the same zero > > install access. Jupyter notebooks can be accessed this way too. > > Yes, some notebooks can be accessed via web pages. > > But they are probably read only. No, Jupyter notebooks are editable across a network. Perhaps a better analogy is a Google Docs. doc. I buy a computer with nothing but a browser installed, go to a web address, and I'm editing a persistent document. That to me is the big prize here, not replacing PyQt with another toolkit given the huge amount of work involved in porting plugins etc. If a browser based UI replaces Qt over time because it's available everywhere, that's fine, but without the "available everywhere" part I don't see anywhere near the value for effort ratio needed to do this. > > Key point is that http://127.0.0.1:8730/ could be > > http://my.server.com/leo/ or maybe http://leohost.com/tbrown/ ;-) > > without any additional work (hosting setup aside). And while I > > would think Electron apps. could work that way, I don't see it in an > > extremely superficial skimming of the interwebs. > > Hmm. That's a worthy goal, but it seems to be a *separate* worthy > goal. I don't think it's separate at all. Almost any js framework / widget stack (including Vue) will give you "available everywhere" for exactly zero extra effort, because that's the only way they work. That hard part's building the GUI, and on the plus side I think a javascript/html GUI will be easier than a curses GUI. Well, no harder at least :) > Ok. It's good to distinguish "browser Leo" and "desktop Leo with > browser-based rendering. I could be wrong, knowing next to nothing about Electron, but it seems to me that it's only with a framework like Electron that the distinction exists at all. That's my concern, that Electron solves a bunch of irrelevant problems (using native desktop menus, dialogs, etc.) but actually hampers the most important use case, read/write Leo on the web. > > If the goal is being able to use cool web/html visualizations in Leo > > on the desktop, they can just be embedded in QWebEngineView, problem > > solved. > > I don't think so. Qt rendering > is feeble and slow. (a) citation required :-) (b) have you tried embedding any web page in QWebEngineView? and (c) ok, if it is, just launch the visualization in the system web-browser. If the goal is just to access additional visualization technologies I think we can do that with a fraction of the effort of building a full HTML GUI. Cheers -Terry -- 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.
