Masterview devel - Jan 2007 - Masterview experiment: packaging directives with a plugin

fyi: I''ve been dabbling with a config service to make it simple to
deliver a
directives dir as part of a plugin so that you can specify in your
masterview config "add all directives directories located in plugins
I''m
loading in this app to the load path".  

I''ve been building several little plugins where I want to support
directive
markup associated with the plugin facilities, and believe this is a nice way
to package and install/distribute the feature. For various reasons some of
the plugins I use in my app aren''t installed in the standard rails
vendor/plugins dir in the app and the loc is diff in my dev setup than in
the deployed version of the site, so configuring my masterview directives
load path is kind of messy if I have to bolt down dir refs; thus the desire
for a config option asking to automatically add plugin directive dirs from
however the rails load path is set up for the current environment.

But I''m not sure I like the implementation yet of how we get hold of
the
rails plugin load path, I kind of extracted and hacked from things done down
in the rails init code, so for the moment I''m patching it in on the
side
from my app init.  Believe I should check out these hooks against rails 1.2
before committing.

Also haven''t convinced myself I understand all the possible
ramifications of
load time dependencies and the timing of when mv directive loading and
startup template processing occurs relative to rails framework, plugin, and
app loading.  Not sure we have quite the right set of hook points in either
masterview or rails itself to completely control some of the timing of
things that you might want.

~ Deb