On Mon, 23 Oct 2017 14:30:40 -0500 "Edward K. Ream" <[email protected]> wrote:
> On Mon, Oct 23, 2017 at 12:38 PM, Terry Brown <[email protected]> > wrote: > > > On Mon, 23 Oct 2017 09:25:51 -0500 > > Stepping back from implementation and separate vs. combined plug-ins, > > sort of feeling that the velocity (speed and direction :-) of the > > drawer and jupyter/ipython threads are different than they were in > > pre-vacation discussions. Do you share that sense? > > Yes. I've decided to use uA's for drawers. > > > Particularly I > > was thinking of Leo as a new interface to / client of > > jupyter/ipython, rather than any emulation / duplication of > > jupyter/ipython features in Leo, for reasons discussed earlier. > > I plan to improve the jupyter importer in addition to mining ipython > for features. > > > On drawers, again thinking back to earlier recent discussion, I'm > > not sure quite what the goal is. In one sense it seems Leo would > > have different solutions for the need met by drawers in org. mode, > > most simply just sub-nodes. But in another sense drawers seem to > > be an in-line body text feature handled by collapsing / folding, > > which makes sense in a flat text document world but isn't something > > Leo with it's tree often does. > > That's the way drawers work in org mode, but we are free to choose a > smoother way for Leo. > > In particular, org mode delimits code blocks with fairly horrible > syntax. The advantage for org mode is that there is no confusion > about where code starts and stops. In contrast, Leo uses @doc, @c > etc to delimit code vs doc parts. > > > If it did, the most exact duplication of behavior > > would be with something like the wikiview. Note that there's no > > recent activity on > > https://github.com/leo-editor/leo-editor/issues/489, and I feel as > > if I've been using wikiview without issues, so I'm not currently > > sure there's a bug there, but would still like the answers to the > > questions posed by #489 just for clarity. > > #489 is worthwhile on its own, but that is not enough to use it for > drawers. Making drawers plain text will complicate all of Leo's > execute-script code. I don't want to do that, especially when eying > support for executing code in languages other than Python using > Ctrl-B. > > > If there is to be a uA based implementation of drawers (a) I think > > it would be easiest to extend attrib_edit, but (b) am not sure how > > the uA approach addresses the in-line text position of the drawer > > in the body text, it seems only wikiview type approaches do that, > > and it seems necessary for any real drawer mode emulation. > > This is a separate issue. I would be happy even with a popup window > to display the drawer. But there are probably better ways. Imo, > icons denoting uA's and drawers will be an important addition. > > Got to go now. There is no rush about these choices. Ok. Well I don't want to be repetitive, but my thoughts are: Drawers: I don't think this is something Leo needs other than in the context of importing org mode files. And in that context, only an implementation wholly compatible with org mode makes sense to me. IPython / Jupyter - depending on configuration, this system can let you move results between multiple languages (Python, R, javascript, etc.), access cloud storage (AWS etc.) and distributed computation (Spark, Hadoop, etc.) and so on. I don't think we want to emulate those features in Leo, but I think Leo can be a great interface to the IPython / Jupyter system - I think Leo's tree can be a viable alternative to the HTML notebook interface, not to mention the power it brings to Leo users if Leo can use IPython / Jupyter as a computational resource. Too bad Ville's not here to opine, would be interesting to see what he'd say. 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.
