Sounds good. I will take a look at the changes, but they seemed to be working fine for my tests and app.<br><br>I think the namespace class impl is fine for now, we can always get more complicated if we need to later.<br><br>
<div><span class="gmail_quote">On 7/5/06, <b class="gmail_sendername">Deb Lewis</b> <<a href="mailto:djlewis@acm.org">djlewis@acm.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Jeff - I committed some internal rework tonight that moves around some of<br>the existing code related to directive loading and managing the set of known<br>directives to support the parser.<br><br>Ran the unit tests and my app and don't think I broke anything, but lemme
<br>know asap if you find any problems.<br><br>There's a new MasterView.DirectivesRegistry which manages loaded-directives<br>registrations and acessing services for the parser. Got into that while<br>working through the issues of enabling support for alternate namespaces on
<br>custom directives. Turns out we probably don't need to do much - mainly<br>just describe the mechanism by which a developer would do so, I think the<br>existing parser code is fine if alt directive namespaces suddenly appear.
<br><br>Option 1 is a protocol in the directive implementation class - e.g. if you<br>implement class method #namespace you override the default use of the mv:<br>namespace. But may want alt mechanism via config settings, in addition to
<br>or instead of a code-based mechanism, so that there's a workaround available<br>in the event of namespace collisions.<br><br>~ Deb<br><br><br>_______________________________________________<br>Masterview-devel mailing list
<br><a href="mailto:Masterview-devel@rubyforge.org">Masterview-devel@rubyforge.org</a><br><a href="http://rubyforge.org/mailman/listinfo/masterview-devel">http://rubyforge.org/mailman/listinfo/masterview-devel</a><br></blockquote>
</div><br>