Add template.ui

[johanmalm]

Set environment variable LABWC_TWEAKS_SHOW_TEMPLATE to show it.

It contains:

1. Scroll Area (frame hidden)
2. Group Boxes
3. Grid Layouts

[johanmalm]

recording.webm

[johanmalm]

@stefonarch I welcome your views on this. Thought it could help us drive some commonality in UI design.

[stefonarch]

Good idea, I'm still a newbie with those .ui files. At a first glance I have this layout in the behavior page I'm working on.

IMO a good place to discuss also which pages will be coming in future.

• keyboard
  IMO the "Language page" should be renamed to "Keyboard" as it is so in afaik all other xkb setting GUIs . Adding:
  • numlock
  • repeat rate
  • repeat delay
• Window switcher?
• Desktops
• Touch ?
• Tablet/Tools ?
• Menu → Behavior ?
• Magnifier → Behavior ?

For "core" items I'm not sure if adding it to "Behavior".
I've added only "Gap" under "Margins" atm. Maybe this could better go under "Advanced"?

Maybe I missed something here, could well be.

[johanmalm]

Good idea, I'm still a newbie with those .ui files. At a first glance I have this layout in the behavior page I'm working on.

Okay, I'll go for the merge now so that we've got it as a reference for future stacks we want to add. We can always develop it with "best practice" ideas as we gain more understanding.

I'm also new to .ui files.

IMO a good place to discuss also which pages will be coming in future.

Yes agree. I personally find it quite hard to do, but agree it's worth putting in the effort up front to avoid re-doing things.

* keyboard
  IMO the "Language page" should be renamed to "Keyboard" as it is so in afaik all other xkb setting GUIs .

I'm fine with this. Can't think of anything non-keyboard related that would belong in a 'language' section.

We might want a separate "Keyboard Shortcut" section. Or we could include that under "Keyboard"

* Window switcher?

Yes. Makes sense.

* Desktops

Agree.

* Touch ?
* Tablet/Tools ?

Suggest s/Touch/Touchscreen/

But, in principle I agree that these probably deserve their own sections.

They will have some of the backend code in common with 'Mouse & Touchpad' but I think that's fine.

* Menu → Behavior ?

I think it depends on how far we go with it. If we just want to include a few rc.xml settings, then a GroupBox in behaviour could be enough, but if we want to allow users to edit the menu with the gui then I'd say we need a dedicated menu stack.

* Magnifier → Behavior ?

For magnifier, we could consider a "Universal Access" stack. It would feel nice to have one of those. That would normally also include things like high-contrast, large text and cursor size.

For "core" items I'm not sure if adding it to "Behavior". I've added only "Gap" under "Margins" atm. Maybe this could better go under "Advanced"?

I'm thinking the same. There are some "unusual" settings which we ought to add to something like Advanced.

Maybe I missed something here, could well be.

We could consider adding some WLR_ environment variables under advanced or similar. https://gitlab.freedesktop.org/wlroots/wlroots/-/blob/master/docs/env_vars.md?ref_type=heads

We could also consider some optional stacks, for example:

• A front end for kanshi

I feel we ought support some theming. This could involved themes in $HOME or just themerc-override.

We could consider a Titlebar stack with a drag-and-drop interface for titlebar buttons and some of the common size variables.