Spring RTS Engine

Recently I have been doing a lot of work on interface stuff. Now there are those who believe all ui should be handled by widgets. However I feel that a game's ui should be handled via gadgets. It was my understanding that widgets were for user UI mods and not the project's core UI. I have heard differing opinions on this matter and frankly want to get an answer posted and written so others can know it as well.

So, I am sure there will be flaming, ad hominems etc I respectfully request any such text be moderated out of the posts as this is a fact finding discussion.

Pretty much it's your choice.

Of course using widgets means there's built-in controls for turning specific ui elements on and off, but you could code your own controls in a gadget.

I remain of the position that the core UI should be forced upon the user and thus gadgeted, and the mod or game development team can decide to permit either third party widgets and/or first party widgets at their own discretion. For 1944 I envisioned all inhouse gadgets and widgets.

Keep in mind that you should be able to disable any gadget UI with the proper /command if you have a widget UI replacement for that specific game.
My thinking is that anything you need to play the game itself should be gadget, most of the rest widgets.

so what is this ModUI thing?

smoth wrote:so what is this ModUI thing?

Archaic leftover.

left over from what?

how is it archaic?

It's deprecated and was never in use.

You should just forget that name.

gadget