I'm very enthusiastic about this work. It will eventually be a real boon to users and developers, I'm sure. I don't know if it will be possible, but I hope that existing GUI plugins that use the nested-splitter/free-layout will be able to continue working without needing to be reworked
On Thursday, May 16, 2024 at 10:39:55 AM UTC-4 Edward K. Ream wrote: > PR #3911 <https://github.com/leo-editor/leo-editor/pull/3911> contains > preliminary work on deprecating Terry's trailblazing free_layout and > nested_splitter plugins. This post is a progress report. > > *Goals* > > Scripts (@button nodes) and plugins should be able to do the following* > easily *and *intuitively:* > > - Detach Leo's screen components, thereby making them floating windows. > > - Move Leo's screen components to other locations. > > *Tools* > > Terry's plugins contain non-trivial low-level helpers that have served as > models for utilities in the PR. A higher-order *gui API* will support the > goals above. > > The gui API will use a *descriptor class* analogous to the caching code > in Terry's plugins. This class will output JSON descriptions of actions > that can persist between different runs of Leo. > > *Summary* > > This post discusses the PR's design. The PR: > > - turns Terry's innovative code inside out, exposing previously private > helpers. > > - creates a descriptive* gui API* that hides implementation details. > > All details are still in flux. All your questions and comments are welcome. > > 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/60b68059-b5ff-40f4-8447-bf2e1e8b38ean%40googlegroups.com.
