> > didn''t see your aaasample-config (did it get committed?)
oops, nope. it''s out there now (with LF''s)
Another possible tweak: not sure if I like the file name
config/masterview/init.rb - kind of implies more than what''s intended.
This
file really shouldn''t be doing much more than setting values in the
config
instance it''s given, it''s not really intended as a general
"write
initialization logic" - if you want to do additional app initialization to
leverage MV once it''s installed, that probably does properly belong in
your
environment.rb (where it''s run when your own app has been initialized
and
installed, which isn''t the case at the point when the plugin init is
being
run)
So maybe config/masterview/settings.rb or config/masterview/app_settings.rb
(?config/masterview/config.rb?!) would be a better name to express the
intended scope of what goes in this file.
philosophy rant: this might seem like nit-picking, but names *REALLY* do
matter. Getting the names right early on makes a huge, huge difference in
the comprehensibility of the software, both for the developers and the
users. Affects how you talk about and think about what''s going on. I
find
up-front investment in fussing to get names and concepts right always has
huge payoff over the long-term lifetime of the system.
If you''re lazy or get it wrong, it''ll hurt your brain every
single time
forever after when you have to stop and think "lessee, X... oh yeah, that
means Y"
</rant>
~ Deb
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/masterview-devel/attachments/20060602/ed0dfa32/attachment.htm