Re: text namespace

On Thursday, April 10, 2003, at 06:57  PM, Adam Megacz wrote:
> I dunno, I kinda side with Charles on this one... text and label
> should be the same template; the only difference being that you flip
> the editable attribute on or off.

That works.

So now we have:

xwt.widget.edit
	- preapply xwt.widget.text
	- editable = true

xwt.widget.text:
	- preapply xwt.theme.scrollpane
	- redirect to only child of scrollpane, which preapplis xwt.theme.text
	- preapply focusable.
	- pull out the keybinding traps from the child for the focusable 
preapply
	- editable = false

xwt.theme.text (actually done in a theme somewhere):
	- preapply xwt.lib.text
	- implement theme-sepcific keybindings, placed in traps ready for 
focusable

xwt.lib.text (all the code and stuff)

This sound right?

> I can see how richtext belongs in a seperate template.

It needs a separate template for usage, and probably it's own namespace 
under xwt.lib for implementing its selection code on top of xwt.html 
(at this point).

I'm trying to plan it so xwt.html is nothing more than an 
implementation of the standard. The challenge at the moment is: which 
standard, and how to handle the others (many plans, may post them soon).

> IMHO the "engine" (ie bulk of the code) belongs in xwt.lib, right?

Yes. What I said was a little misleading. See above.

d


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