Quite a diversity of opinions on this one! To me, the ideal MVC model allows both conceptual design and practical development of the three separate layers. All one layer should need to know about another is their common interface.
IMO one of the practical benefits of a good MVC development system is that the tools allow this to be as simple as possible. e.g. having to edit a minimum number of files to enable this. I use WO for developing webapps and so far I've found it pretty good at allowing MVC along these lines. While the idea of configuration files and multiple java classes per "page" are entirely within the scope of MVC, ideally I would not be forced to do so if a simpler solution is available. For my own purposes, I have been able to use .wod + .html as the "View" up to now, and that's largely because I've been happy to ignore the complexities of .css. Using the likes of WOConditionals, WORepetitions and WOComponents within WOBuilder make it easy to do almost all of what I need. I can see that the designers of WOBuilder tried to include just about everything the typical .html View would need a few years ago, without resorting to code. Hence a WOComponent set (java, wod, html) covers most of what is typically needed. These days, in the world of .css, I feel the View needs a bit more complexity. For my purposes, something like a <WOSwitch>....<WOOption>..., equivalent to a Java "switch" would suffice. That way I could still use one WOComponent per "page" or page section, consiting of .wod + .html as the View part, and one .java as the Controller part. Sure, there will be many other business logic java classes in the app, but they're not concerned with the View. As we don't have this, there are a number of solutions and workarounds as described in this thread, but I can dream! Maybe in the next WO version, Apple? :-) Of course, that's what would suit me for the way I want to build an app, but no two developers work the same way... John _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
