Masterview devel - Sep 2006 - Rework of DirectiveDSL as a mixin + internal namespace

>>  go ahead and commit your code when ready.
done, believe I picked up all the ripples into test cases etc, let me know
if I missed anything

I''ve also got a modified copy of parser.rb where I was experimenting
with
similar addition of namespace substructure to wrap the internal impl
classes.  Used MasterView::TemplateProcessing there (similar to introduction
of Master::DirectiveProcessing in the DSL impl).

Not sure if that''s partitioned quite right.  I can commit if you want
me to
put it in and then we can both refine it further, otherwise I''ll just
keep
it for now as my local deviation.
>> mvx sounds like a good default namespace for extensions to keep
distinguished from the built in ones.

Ok, I''ll continue to work with that on the first pass. 
That''ll be an
upgrade issue to document/flag at release time tho - currently addons get
dumped in mv:foo.

RE: namespaces - for the first pass I''m hooking up a mechanism that
will
pick up metadata defaults from a config spec file in a directives directory
if available; that''ll make it fairly easy to package a set of addons
w/out
having to hardwire explicit metadata decl''s for the namespace into
every
class.  Once that''s settled I''d like to add a config-time
override mechanism
to tie into masterview config.directive_paths entries.  [and someday: figure
out what it would mean to allow doc-specific namespace aliasing as defined
by xml]

~ Deb

On 9/20/06, Deb Lewis <djlewis at acm.org> wrote:
> >>  go ahead and commit your code when ready.
>
> done, believe I picked up all the ripples into test cases etc, let me know
> if I missed anything
>
> I''ve also got a modified copy of parser.rb where I was
experimenting with
> similar addition of namespace substructure to wrap the internal impl
> classes.  Used MasterView::TemplateProcessing there (similar to
introduction
> of Master::DirectiveProcessing in the DSL impl).
That is fine with me.
>
> Not sure if that''s partitioned quite right.  I can commit if you
want me to
> put it in and then we can both refine it further, otherwise I''ll
just keep
> it for now as my local deviation.
Which ever seems best to you.
>
> >> mvx sounds like a good default namespace for extensions to keep
> distinguished from the built in ones.
>
> Ok, I''ll continue to work with that on the first pass. 
That''ll be an
> upgrade issue to document/flag at release time tho - currently addons get
> dumped in mv:foo.
Right
>
> RE: namespaces - for the first pass I''m hooking up a mechanism
that will
> pick up metadata defaults from a config spec file in a directives directory
> if available; that''ll make it fairly easy to package a set of
addons w/out
> having to hardwire explicit metadata decl''s for the namespace into
every
> class.  Once that''s settled I''d like to add a config-time
override mechanism
> to tie into masterview config.directive_paths entries.  [and someday:
figure
> out what it would mean to allow doc-specific namespace aliasing as defined
> by xml]
Sounds like a plan!