Re: problem with internal ui: namespace

Yeah, that's one of those dirty little xwt secrets I was trying to
ignore. ;)

Actually, it's valid, compliant XML, but it's not compliant with the
XML-Names spec.

  - a

Tupshin Harper <[email protected]> writes:
> Any namespace that is used in an XML file *has* to be declared in that
> XML. Currently, core defines the ui: namespace internally, which means
> that it is functional to do:
> <ibex>
> <ui:box/>
> </ibex>
>
> But this is illegal XML, since ui: wasn't specified with a namespace
> declaration.
> If you attempt to declare a namespace declaration for ui, then it
> tries to override the internal ui mapping, and therefore doesn't work.
>
> I would suggest that instead of doing an internal namespace mapping,
> that we just have a virtual pathtowidget mapping (ui.box, for
> example), that *can* be defined with a namespace declaration in
> template files, but doesn't have to be.
>
> -Tupshin
>
> _______________________________________________
> core mailing list
> [email protected]
> http://lists.xwt.org/listinfo/core
>

-- 
"It's lucky," he added, after a pause, "that there are such a lot of
islands in the world.  I almost envy you, Mr. Watson."

                                                   -- Mustapha Mond