Interactive tools for rapidly building GUIs are all the rage, and wxWindows does not at this point support this. Loading Windows 3.1 dialog boxes from resource files may be possible in future in wxWindows, so that dialogs may be constructed interactively. However, this will not carry through to other platforms, so a more general solution is required. One possibility is to translate Windows 3.1 resource scripts or DevGuide descriptions into wxWindows code, or into a form that wxWindows could load. Using YACC and LEX such a project could be quite straightforward, although there will not always be a mapping between the dialog builder and wxWindows constructs. (A wxWindows user is currently working on this project.)
Another consideration is that it is not always possible to build GUI components interactively: the 'what you see is all you get' syndrome. When complex repositioning of items depending on window size is required, then GUI builders such as the Microsoft dialog editor are useless.
However, using a toolkit with geometry management may be no panacea; for example, the Motif constraint algorithm is difficult to understand and much experimentation is necessary. The approach taken by wxWindows is in keeping with the main goal of simplicity: wxWindows has the ability to create panel items from left to right, top to bottom with appropriate horizontal and vertical spacing; or the programmer may position the panel items explicitly. The first method gives resolution and font independence, and is less fiddly, and the second method may be used for tidying up a display for a specific platform.
Is likely that in the near future, a constraint algorithm will be added to wxWindows to allow specification of relative position, alignment etc. Hopefully, it will be easier to use than Motif constraints, if not as flexible.