I think this discussion is slightly off-center. It seems that most people are criticizing John Long's solution rather than discussing the problem he's trying to solve. The advantage to breaking out an application by function rather than type is that you can then package up an entire area of one project and use it in another. Just to clarify, I'm not saying that all applications should be built with this in mind and that all applications can be separated out by functional area, but rather that if there were functional areas of a site you'd like to reuse in another rails application, it becomes difficult.
Plugins are the beginning of code sharing, but they simply aren't powerful enough (no direct support for views, routing, database migrations, public assets, etc). This is a problem that many people have tried solving in one way or another (Plugin-a-week's appable_plugins, Rails Engines, RHG's Plugems, Radiant's extension system, etc) but really should be discussed and solved at the core level. -Warren On Jun 15, 5:55 pm, "John W. Long" <[EMAIL PROTECTED]> wrote: > I've written an article suggesting some radical changes to the Rails > directory structure for Rails 2.0 and am curious to know the core > team's thoughts about it: > > http://wiseheartdesign.com/2007/6/15/better-modularization-for-rails-... > > -- > John Longhttp://wiseheartdesign.comhttp://radiantcms.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
