Masterview devel - Jul 2006 - New DirectivesRegistry and support for multiple directive namespaces

Jeff - I committed some internal rework tonight that moves around some of
the existing code related to directive loading and managing the set of known
directives to support the parser.

Ran the unit tests and my app and don''t think I broke anything, but
lemme
know asap if you find any problems.

There''s a new MasterView.DirectivesRegistry which manages
loaded-directives
registrations and acessing services for the parser.   Got into that while
working through the issues of enabling support for alternate namespaces on
custom directives.  Turns out we probably don''t need to do much -
mainly
just describe the mechanism by which a developer would do so, I think the
existing parser code is fine if alt directive namespaces suddenly appear.

Option 1 is a protocol in the directive implementation class - e.g. if you
implement class method #namespace you override the default use of the mv:
namespace.  But may want alt mechanism via config settings, in addition to
or instead of a code-based mechanism, so that there''s a workaround
available
in the event of namespace collisions.

~ Deb

Sounds good. I will take a look at the changes, but they seemed to be
working fine for my tests and app.

I think the namespace class impl is fine for now, we can always get more
complicated if we need to later.

On 7/5/06, Deb Lewis <djlewis at acm.org> wrote:
>
> Jeff - I committed some internal rework tonight that moves around some of
> the existing code related to directive loading and managing the set of
> known
> directives to support the parser.
>
> Ran the unit tests and my app and don''t think I broke anything,
but lemme
> know asap if you find any problems.
>
> There''s a new MasterView.DirectivesRegistry which manages
> loaded-directives
> registrations and acessing services for the parser.   Got into that while
> working through the issues of enabling support for alternate namespaces on
> custom directives.  Turns out we probably don''t need to do much -
mainly
> just describe the mechanism by which a developer would do so, I think the
> existing parser code is fine if alt directive namespaces suddenly appear.
>
> Option 1 is a protocol in the directive implementation class - e.g. if you
> implement class method #namespace you override the default use of the mv:
> namespace.  But may want alt mechanism via config settings, in addition to
> or instead of a code-based mechanism, so that there''s a workaround
> available
> in the event of namespace collisions.
>
> ~ Deb
>
>
> _______________________________________________
> Masterview-devel mailing list
> Masterview-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/masterview-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/masterview-devel/attachments/20060705/567938e7/attachment.html