On Sat, Jun 16, 2007 at 03:51:05PM -0000, John W. Long wrote: > Again, what exactly is the point of organizing files by type? Our
So you know, absolutely, where a particular file will be. "I'm looking for the Foo model, so that'll be in app/modules/foo.rb". It becomes a little fuzzier as to where your files are when your models might be tied to one of a number of different "chunks" of the app. > applications have logical structure, why not reflect that in directory > layout? In that case, I'd say that you would want to allow a free-form directory structure under app/, which is not very opinionated, will cause endless holy wars, and doesn't fit with the rest of the Rails Way (as I see it). > Perhaps the example laid out in my article is a bit extreme. I'd see > it as a win if we just moved to a directory per related controller, > model, and views: Remove 'model' from that list, and you'd be awfully close to having my vote. The views, helpers, and controller do all tend to relate quite closely together. Models, though, often permeate between various controllers. > Please, set the issues of backwards compatibility aside or personal > preference and argue with merit alone. How much of this discussion *doesn't* ultimately come down to personal preference? Do you have any hard, objective facts in favour of your proposed layout? I don't know of anything that objectively supports Rails' current way of doing things. - Matt --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
