On Monday, September 11, 2017 at 11:47:14 AM UTC-4, Terry Brown wrote: > > For multi-node editing, another layer not yet started but perhaps a > good next step, would be a separate widget that manages a vertical > stack (scrolling area) of these edit/view widgets. In the case where > the view half was visible and showing the results of code execution, > this would basically be a Jupyter notebook view. >
I think this is the feature a lot of people are after (at least what I'm after). It would be wrong to call it simply a "Jupyter notebook view". Depending on how you configure the size of the text-edit area and the visibility of borders this would also be used for Org-mode style viewing. In "Continuous view", which would support Org-mode and standard text editing, you could make the text edit areas resize to same number of lines of text that exist in each node and make the borders 1 pix high grey lines that tell you where a nodes starts and stops without adding extra bulk. Question: who many people will look at / test it if it stays in a > separate branch? Alternative is to merge it into master, which would > require this change in core: > > > https://github.com/leo-editor/leo-editor/commit/d9dcffea2655c12c53762053e9ba2a6564266b1f#diff-ed64e2876398e232da95328f1bf78e65 > > > That has a detectable but I think ignorable performance hit, but we > should discuss. > I think if there is any hope of public "beta testing" it has to be in master. -- 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.
