On Fri, May 19, 2006, Jeremy Kemper wrote: > The simplest is to share them all-- surprisingly not-so-bad, though I > had some knee-jerk dislike.
I considered doing that, but there was a semi-good argument against it at the time which I have since forgotten. > 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. > Since replying, I did come up with a couple of externals annoyances: > 1. svk doesn't deal with them at all > 2. they're dumb urls, so your branch from trunk to branches/some- > dev-feature leaves your externals pointing to the other app's trunk. I had forgotten about #1. I do use svk so that was an annoyance. > (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. Ben _______________________________________________ PDXRuby mailing list [email protected] IRC: #pdx.rb on irc.freenode.net http://lists.pdxruby.org/mailman/listinfo/pdxruby
