Re: gui builder issues?

On Fri, 2004-01-23 at 09:39, Emiliano Heyns wrote:
> The first problem would be to define what constitutes a widget in the
> first place. In any XWT (ibex?) app, there's going to be many templates
> that the user won't think of as a widget (since it'll have a single
> purpose, like a specific pane grouping widgets to form the app gui) but
> that could technically be used as such.
> 
> Maybe we should explicitly mark widgets? An attribute on the toplevel
> that has no purpose but to identify it as an entity meant to be
> presented as a widget in a gui builder?

-1

It's up to somebody developing apps to make an effort to understand
widgets.  They'll have a 'list' (a toolbar?) to choose from and they
should understand the process that goes into setting up a GUI.

ie to create a menu:
1) add a toolbar
2) add a menu entry
3) add a menu item, submenu, or separator

It'd be wiser to simply describe widgets properly in documentation to
that 'mark' them in some hackish way.

Besides, it's quite clear (once the concept has been introduced) that
anything in xwt.widget is a widget.

> Maybe here too it'd be worthwhile to not rely upon reflection but
> explicitly document what the UI builder can use, and how.

Perhaps we have a use for some XML elements in the <doc> node to point
out exactly what properties a widget has.
-- 
- Charlie

The future of the net - www.xwt.org

Charles Goodwin <[email protected]>
  Member of the XWT Foundation