Thank you, Thomas and Edward, for your inputs and examples.
As a Leo user (and occasional dev/contributor) over the last 12 years and change, removing the ‘Easter egg’ menus feels like the largest regression I’ve seen Leo go through. Needing to write custom commands and scripts to do now what used to take about three clicks before is just unfortunate.
I don’t know how to satisfy both the needs of devs and the needs of users in this instance. It just feels a bit sad that the UI lost in this particular fight. And I don’t think that a bevy of new commands is the right way to go about it moving forward, either — many users never ever interact with the minibuffer. I certainly don’t use it if I can help it. And Leo is my Everything Program for over a decade now.
I will script up the things I need to get the work done that I need to do, but in all honesty this is a huge loss for those who aren’t programmers and used to be among the users Leo welcomed more thoroughly. It feels a little bit like every passing version removes more and more user-facing features, and alienates non-programming folks even further.
Sorry to complain, just airing my $0.02 (worth even less now with inflation).
Jake Here's a similar script that will toggle viewrendered in a new pane next to the body:
import leo.plugins.viewrendered as v
h = c.hash()
vr = v.controllers.get(h)
if not vr:
v.controllers[h] = vr = v.ViewRenderedController(c)
if vr.isVisible():
c.doCommandByName('vr-hide')
else:
ms = g.app.gui.find_widget_by_name(c, 'main_splitter')
ms.addWidget(vr)
ms.setSizes([100_000] * len(ms.sizes()))
c.doCommandByName('vr-show')
On Wednesday, July 17, 2024 at 5:14:53 PM UTC-4 Thomas Passin wrote:
If you want to use viewrendered3 instead of viewrendered, I have scripts that will open it in the same pane as the body editor, and you can toggle between VR3 and the body editor. I have another one that can open VR3 in the log pane instead of on a small panel under it. I'm pretty sure a small change would make them work for VR but I haven't tried it.
Otherwise, I have a script that moves the log frame from its default position under the tree to a new panel to the right of the body editor. This does the same thing as one of the old splitter menu items. I've put these scripts into buttons so they are easy to use.
Actually it's easier to write dedicated little scripts now than it used to be with the old nested splitters. Mainly you have to know the names of the frames and splitters you are interested in. Edward posted a command that will list all the widgets and their names in a hierarchical view. I forget whether it's a built-in Leo command or not.
My guess is that eventually a default Leo installation will have several of these little commands, once we get enough experience to know what they should be. Here's my script to swap the log frame to a position beside the body editor. It finds the splitter of interest, then finds the widget for the log frame, and inserts it into the same splitter as the body editor - that automatically puts it beside or below the body editor depending on the orientation you are using:
"""Move Nav frame between main and secondary splitters."""
gui = g.app.gui
ms = gui.find_widget_by_name(c, 'main_splitter')
ss = gui.find_widget_by_name(c, 'secondary_splitter')
lf = gui.find_widget_by_name(c, 'logFrame')
nav_in_secondary = ss.findChild(type(lf), "logFrame")
target = ms if nav_in_secondary else ss
target.addWidget(lf)
# Equalize sizes - "100000" must be larger than any of the widgets...
# and well less than MAX_INT
target.setSizes([100_000] * len(target.sizes()))
If you are using vertical orientation instead or horizonal (or maybe the other way around, I forget the terminology) this may not be what you want but you can change the orientation with the Window menu item Toggle-Split-Direction .
Until we have more of these commands, post what functionality you would like to have and perhaps Edward or I will be able to write one. Alt-0 to open my VR pane now opens in a really tiny box underneath my log, and it's kinda unusable there. I'm not seeing in the docs or leoSettings file how to move things around any longer. This feels like a downgrade, unless I'm just missing some commands or something (and even if there are commands, the right-click context menus were supremely useful for this. so I didn't have to memorize new things).
Sorry if this sounds frustrated or critical, that's not my intention. I'm honestly just trying to figure this brave new world out. The 'old way' may have had its implementation woes, but the user facing experience was at least easier to grok to me. Please point me in the right direction, so I can educate myself. Thanks, Jake
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/aed731a4-6add-493c-a087-0e725608c377n%40googlegroups.com.
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/F0D58AD0-4795-4479-8791-A6C1815EAA37%40gmail.com.
|
