On Wed, Jul 17, 2024 at 8:51 PM Jacob Peck <[email protected]> wrote:
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'. > Thanks for your comments. Over the years I've deleted several overly-complex features. I've never regretted any of those choices and I don't regret removing the free_layout plugin. Being less complex under the hood is worth any temporary pain. 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 😅. > Exactly. And you weren't the only user that had trouble. 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. > Leo now has a new *widget* API, consisting of just a few new methods. I think a possible starting point for a series of commands could be ... > I agree that some help would be welcome. Thomas's scripts are an excellent starting point. Those scripts are a good *ending* point if you are good with changing the layout using `@button` nodes. I don't recommend enabling scripts on startup. It's too big a security concern. Instead, I recommend creating new *layout plugins*. Outlines could enable the most appropriate plugin. *Summary* - There is no need for yet another API or yet more commands. - `@button` scripts are best when one wants to allow multiple layouts in an outline. - Bespoke *layout plugins* are another way to package non-standard layouts. HTH. 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS07OAywRg957TkUVCYAjd5H7fEgsJZzTGmn86y7rh3_Tw%40mail.gmail.com.
