On May 19, 2006, at 3:48 PM, Ben Bleything wrote:
Another is to namespace your models with modules+subdirs and cherry-
pick dirs for svn:externals as you please. This requires a bit of
work changing Foo to SomeModule::Foo but tickles the "it feels right"
spot by keeping a large models dir comprehensible and by sharing
'chunks' only as needed.
That seemed like more trouble than it was worth when I could just
create
an engine to do it, but it's a good tip for the future.
Yeah, def avoid unless modules are warranted of their own right
(I think too much `ls` overflows my brain's L1 cache.)
(I haven't tried Engines for this task so I can't say how they
compare.)
In the simplest case, all the Engine does is add its subdirs to the
load
paths. So if you have models defined in your Engine and then load
that
engine, Rails will load those models too. That's how I was using it.
You can of course get more complex with it, I just didn't bother.
This sounds equivalent to a plugin in the models-only case. I'll have to
give it a shot to see how controllers + routing work out..
jeremy
_______________________________________________
PDXRuby mailing list
[email protected]
IRC: #pdx.rb on irc.freenode.net
http://lists.pdxruby.org/mailman/listinfo/pdxruby
