Re: FINAL CALL

Charles Goodwin <[email protected]> writes:
> Where do common key bindings go with this model.  eg edit, the key bindings
> for edit / a text box are common to many platforms but not all
> ...
> It can't go in .lib, can it.

If it's generally useful but doesn't apply to all themes, then it goes
in .lib.  A hypothetical org.xwt.theme.monopoly.edit would preapply
xwt.lib.keybindings and then override the keybindings that don't
apply to that particular theme.


> I don't like the widget_layout/widget_functions separation because that's
> ^exactly^ what namespaces (aka directories) are used for.  Why add _layout
> to all your files when you can have layout.widget (or theme.widget as I'd
> have called it) and simply lib.widget over lib.widget_functions.

You can break up xwt.lib into xwt.lib.layout and xwt.lib.functions if
you like.  We're gonna play it fast-and-loose with xwt.lib and go back
later once we have some hindsight to work with.  If you think this is
the best way to go, by all means do it.


> old layout and the more it doesn't address the problems that we've
> recognised in the duraction of the widget audit.

Charlie, you need to post specific examples of these mysterious
"problems" instead of just alluding to them.

  - a

_______________________________________________
http://lists.xwt.org/listinfo/dev