On Fri, Mar 24, 2017 at 8:10 AM, 'Terry Brown' via leo-editor < [email protected]> wrote:
> I'm not sure if I understood Lewis's post or not. Neither do I. > Different solutions, but no reason to think there's one best solution. > The questions I am interested in. First, what's best for Leo. Second, how best to connect, literally and figuratively, with other programs. > > Leo will soon have commands that make it easy to show/hide the body > > pane or everything except the VR pane. These commands will give Leo > > the essence of Quiver's Preview, Presentation and Full Screen modes. > > Ditto for Jupyter notebook views. > > I have a problem with your use of the word "the" :-) Heh. > I think Leo should be (is?) > > flexible enough to support multiple editing components. Do what seems best to you. That will work, providing we don't reimagine what body panes, possibly plural, do. The odd > example using > [pub/sub] without an instance points towards the possibility of > storing listeners on `c`, in appropriate cases, without modifying other > Leo code. Or at least keeping the modifications more localized / > possibly even in a plugin. > There might be some g.app objects that might like to subscribe. Other than that, keeping pub/sub data in the Commander or subcommander seems natural. 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.
