Difference between revisions of "GUIToolkit"

From The Battle for Wesnoth Wiki
m (Typos)
m (Fix heading markup)
Line 1: Line 1:
= Introduction =
+
== Introduction ==
  
 
This is a new toolkit aiming to make it possible to make the look of Wesnoth fully skinnable.
 
This is a new toolkit aiming to make it possible to make the look of Wesnoth fully skinnable.
Line 10: Line 10:
 
* Window definition, which defines how a certain window looks and it uses the widget definitions.
 
* Window definition, which defines how a certain window looks and it uses the widget definitions.
  
= Todo list =
+
== Todo list ==
 
Here's a(n incomplete) list of items which still need to be done.
 
Here's a(n incomplete) list of items which still need to be done.
 
* The layout engine can still have problems with not finding a solution and stop.
 
* The layout engine can still have problems with not finding a solution and stop.
Line 20: Line 20:
 
* Convert more dialogs
 
* Convert more dialogs
  
= Links =
+
== Links ==
 
* [[GUIVariable]] describes the variable used for the parts of WML.
 
* [[GUIVariable]] describes the variable used for the parts of WML.
 
* [[GUILayout]] describes how to place widgets in a window.
 
* [[GUILayout]] describes how to place widgets in a window.

Revision as of 16:23, 29 August 2017

Introduction

This is a new toolkit aiming to make it possible to make the look of Wesnoth fully skinnable. This will be used in Wesnoth the make it easier to optimize for different screen resolutions. The initial work in progress version has been released with Wesnoth 1.6. Since the development isn't done yet, these pages reflect the state of the trunk.

The engine has two parts:

  • Widget definition, which defines how a widget looks.
  • Window definition, which defines how a certain window looks and it uses the widget definitions.

Todo list

Here's a(n incomplete) list of items which still need to be done.

  • The layout engine can still have problems with not finding a solution and stop.
    • Make sure labels buttons etc can shrink and show ellipses to shrink small enough
    • Optimize the shrink algorithm
  • The code for the events is not entirely to my liking and I want to look at using signals instead, events are there bug not yet used everywhere.
  • EasyCoding#GUI2_related_features
  • Improve the markup for the text
  • Convert more dialogs

Links