Why would a floating window solve any problems here? How are you envisioning that a floating VR3 window, *which can already be done* *today without any additional coding*, would help the situation?
As a counterpoint, I only have a single display available to me. I generally do my work (in Leo) on a single desktop monitor, or a tiny laptop screen. In *both cases* I would much prefer a switchable pane, rather than a floating window. The current solution of VR eating up a third of the screen by default, or of faffing about with a floating window (even more irksome on a laptop with a touchpad), is such a poor UX that I avoid it. Enough so that I've effectively stopped using Leo for anything that needs to be rendered. Adding a first-class 'floating window' feature to VR/3 wouldn't fix any issues. It would strictly exacerbate the issue. But a context-aware switchable tab, which is eminently doable, would solve *every single one* of my personal problems. And I know it's a workable solution *because I've done it*. Leo is, to me, an editor, an IDE, and a platform. But it is increasingly *not* an authoring tool for me, because of the current implementation of VR. And that's frustrating, because authoring any sort of complex documentation *should be* where Leo shines, given the first-class outlining and clones. Just my $0.02. I wish we wouldn't just discard things out of hand because of perceived 'dubiousness'. Experimentation is fruitful, and painless, given git branching. Jake On Fri, Apr 26, 2024 at 1:31 PM Edward K. Ream <edream...@gmail.com> wrote: > On Fri, Apr 26, 2024 at 11:49 AM Thomas Passin <tbp100...@gmail.com> > wrote: > > >> Trilium undervalues the power of text: > > > I think that Edward does not appreciate how often users want to use Leo > as a Notebook... > > I agree. Leonistas *should *be able to use lots of graphics :-) That's > why improving the VR plugins and (maybe) the rst3 plugin seems like a good > idea. > > > Trillium...shows you a rendered view of its nodes and makes it harder to > edit and work with the content. > > > Leo makes it easy to edit and work with text, but harder to insert and > look at rendered graphics, etc. > > That's a reasonable summary. A floating VR pane would be a step forward. > > > VR3 can display [jupyter] files using an @jupyter node type. Any text > display would only show the raw html... > > Yes, sometimes the rendered view is preferable. But that's no reason to > complicate Leo's interface. > > *Summary* > > The Easter Egg is the only way to expand the VR pane. An optional floating > VR window would solve that problem. > > 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 leo-editor+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/CAMF8tS1WZmuDxfRg8vU-oWsXKRZOoKSqn2ZP0cGX0Duw_5ys4A%40mail.gmail.com > <https://groups.google.com/d/msgid/leo-editor/CAMF8tS1WZmuDxfRg8vU-oWsXKRZOoKSqn2ZP0cGX0Duw_5ys4A%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAJ1i%2BSYr2DEPMRRaA9Xr%2BXdUx-a1r%2B%2Bj7Z0zxJ8LxTwTvG998Q%40mail.gmail.com.
