After sending, I realized I omitted a statement I meant to include: ``` This being the largest regression I've seen Leo go through in 12 years is a *testament* to how fantastic this app is. Which also, somehow, heightens it absence. It's just a little less 'perfect' now, even as it's more structurally sound 'under the hood'. ```
As a script writer, I'm sure I'll much appreciate the new splitter setup -- some of my 'LeoApps' had done *atrocious* things to get a consistent layout 😅. I just haven't gotten into the new splitter API and I really don't think usual users should ever *have* to go that far. I think a possible starting point for a series of commands could be (assuming a potential layout of thirds, either vertical or horizontal): move-XXX-to-top (alias move-XXX-to-left) move-XXX-to-bottom (alias move-XXX-to-right) move-XXX-to-center where XXX is a 'named' pane (log, body, vr, vr3, etc) And where the commands interpret the appropriate movement instructions from whether the layout is currently horizontal or vertical via the Split Direction (thus the aliases -- same command under the hood, just with user-friendly names for cognitive ease). Perhaps there could even be an API to 'register' new named panes (which would auto-generate and auto-populate the appropriate commands). And a matching `list-all-named-panes` command (and function somewhere under c) that would get you the list of registered named panes. With such a thing, plugins that add new panes could just say to Leo's core "hey, I'm providing a widget called foobar, you do the layout work". Just spitballing. Thanks for coming to my TED talk :) Jake On Wed, Jul 17, 2024 at 9:01 PM Thomas Passin <[email protected]> wrote: > > On Wednesday, July 17, 2024 at 8:44:35 PM UTC-4 [email protected] wrote: > > 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). > > > I was unhappy too or at least concerned when Edward brought up changing > the splitter interface. But unlike you, I always had trouble using it, or > even knowing what the various context menu items would do. And when I got > a configuration I liked, it was hard for me to reproduce. I was constantly > irritated and tried to avoid using the splitter menu. It also made > programming various things in plugins tricky at best. The new interface is > much better, I think, at least for programmers. > > I certainly agree with you about having built-in commands that are easy to > use to replace some of the splitter menu commands. Ordinary users > shouldn't have to write scripts to do basic configuration. OTOH, just what > are those configuration things that people want to do? It's a little hard > to know until they speak up. I don't know about Edward, but I hope we can > learn what people want the most and start to build them in. > > And, as always, it's hard to figure out how to let people find out how to > do things they want. Suggestions greatly welcomed! > > -- > 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/add5bed1-e9dc-49fb-a2f5-e522450cbe2bn%40googlegroups.com > <https://groups.google.com/d/msgid/leo-editor/add5bed1-e9dc-49fb-a2f5-e522450cbe2bn%40googlegroups.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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAJ1i%2BSYsPbGH_oYiOQWvwonM7h_8HGvTer2SFahbSu5SoP9ufQ%40mail.gmail.com.
