Masterview devel - Sep 2006 - What is/was purpose of namespace override option in Renderer?

Jeff - there''s an old hook in the template parsing Renderer to take
options
from the client which can include :namespace option to override the default
mv namespace.

I need to understand why that was there and if it''s something
significant
that we need to support.  Whatever the original purpose was probably
doesn''t
work with the new metadata and namespaces mechanisms that I just put in.

I''d like to either get rid of that old :namespace option hook in
Renderer or
if it''s important figure out what needs to be done to provide the
desired
functionality given the new metadata facilities.

Discussion/details follow.

~ Deb

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

Background: the original implementation of parsing filled in default value
for namespace if not specifically implemented by the directive dynamically,
every time a document template was processed.  There was code which
on-the-fly computed default attr name from directive class name and if no ns
specified filled in the default mv namespace.

The options arg in Renderer would allow mv: namespace to be overridden on a
per-invocation basis (though I don''t know if that was ever exploited)

The new stuff I''ve put in pins down its point of view on directive
markup
naming at the time that a directive is loaded.  That effectively fixes our
opinion on the directive''s attribute name and namespace for the
duration of
the application''s execution.

I would at some point in the Glorious Future also like to handle namespace
aliasing w/in a document, per xml markup that lets you declare the namespace
prefix you want to use w/in that particular document, but that''s not
something I want to tackle yet.  And when we do it''s likely solvable at
the
point when we extract the directive set from an alement: if there''s
namespace prefix aliases defined in the document we''re processing,
we''d map
that to the registered namespace at that point so we can identify the
handler.

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

On 9/22/06, Deb Lewis <djlewis at acm.org> wrote:
> Jeff - there''s an old hook in the template parsing Renderer to
take options
> from the client which can include :namespace option to override the default
> mv namespace.
>
> I need to understand why that was there and if it''s something
significant
> that we need to support.  Whatever the original purpose was probably
doesn''t
> work with the new metadata and namespaces mechanisms that I just put in.
>
> I''d like to either get rid of that old :namespace option hook in
Renderer or
> if it''s important figure out what needs to be done to provide the
desired
> functionality given the new metadata facilities.
>
I think the original idea was that if you wanted to change the
namespace so that there wasn''t one or to something different so it
didn''t conflict with other things that you could do it. However I
don''t really see this being necessary for any scenarios I can
currently envision. I am fine with removing it in light of the new
custom namespacing that you have created.