On Thursday, July 18, 2024 at 8:41:47 AM UTC-4 Edward K. Ream wrote: On Thu, Jul 18, 2024 at 7:24 AM Jacob Peck <[email protected]> wrote:
@buttons are an objectively bad solution to this for a casual user. That's why a set of layout plugins would be a valuable addition to Leo. I feel that 'layout plugins' would assist with this, but they'd still be supremely inflexible. For the non-programming user, we went from 'you can have any layout you want' to 'here are your choices, get over it'. You are overstating your case. Let's focus on creating a set of useful layout plugins. Plugins for layouts would be helpful but don't completely solve the question of a simple intuitive user interface. A layout plugin can provide a new menu item, @button, or minibuffer command that will create the new layout. A better user interface would, as Jacob writes, let a user see and click on the layout wanted, or even better to manipulate panes on a simplified view to create a new layout. I would say that the latter would be awfully hard to to create relative to its benefits, but the former would be much easier. Leo's menu construction system uses a declarative approach. The desired menu arrangement is specified in a @settings file in a declarative way. It's fairly easy and very useful. I expect that a similar declarative approach to layouts would be fruitful. -- 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/9ee534c5-5d92-4123-b360-61a527e54867n%40googlegroups.com.
