Ideas • Re: [interface] sidebar: make unit status / unit_weapons scrollable

I'd like to inform you about something. Wesnoth actually has two UI toolkits. The first is the legacy UI toolkit (GUI1), which is used in:

• the top bar including the menu bar
• the sidebar (which you're working with)
• the help browser
• the command window inside a scenario

All other windows use the new GUI toolkit called GUI2. More details are on the wiki and past forum post, for example here. (It separates the UI and control logic and simplifies many things.)

The development team has plans to replace the GUI1 toolkit completely (for a long time now), so it is likely possible that all of the parts mentioned above will get completely redone using GUI2, hopefully within the current development cycle. Also, this might automatically fix many of the bugs involved the previous parts. So what that mean it that any change or bugfixes to those parts will get replaced, so there's a risk that your efforts might be wasted (really sorry for that). The UI Maintainer and the Project Manager can give you more details.

4) If I should go forward with this, is this the place to discuss implementation details? I think I have a decent idea of what needs to be done, but I'd really like to avoid going down the wrong path if I'm wrong.

Joining the development channels on Discord/IRC might make the discussion faster. Another option is creating an Issue on github.

Are there any ongoing discussions or documented plans I could look at? Your response got me curious, so I did a little poking around and managed to come up with a very crude GUI2 version of the top panel, and I think I now have a rough understanding of how GUI2 works with C++. What I don't get is how the player would be able interact all at once with the top panel, the sidebar, and especially the gamemap (is this what you mean by "the command window inside a scenario") -- unless the gamemap itself was made into a widget, or some sort of "pass through widget" was created, or ...??? My understanding of a dialog, mostly from the lua API, is that it takes exclusive ownership of the keyboard/mouse as long as it's open, so I'm missing something there.

I looked at discord (for the first time), but it looks to me like pretty much just an IRC clone, fine for a quick chat but not something I'd expect would be used for more long-term planning kind of stuff.

thanks

Statistics: Posted by white_haired_uncle — Today, 2:49 am

---