Re: Problem with webobject attributes in WOBuilder
Re: Problem with webobject attributes in WOBuilder
- Subject: Re: Problem with webobject attributes in WOBuilder
- From: "John Stewart" <email@hidden>
- Date: Thu, 15 Jun 2006 13:08:16 +0100
A slight afterthought...
My idea of MVC is that the only the View deals with appearance, although may need a certain amount of logic to handle this. The Controller carries the business logic and shouldn't be concerned with appearance, though has to handle I/O of data to the View.
For example, the Controller can tell the View that it wants to display something as "On" or "Off", but doesn't care how this is done.
The View could display this as verbal "On" or "Off", or could use icons for red & green traffic lights.
The View should contain all "ViewLogic" necessary to create this appearance. A useful encapsulation which allows that to be changed later without affecting the Controller.
I was hoping to handle the View entirely in .html + .wod, so if the .css changes I just change the references in there. However, the .wod logic won't cope with that, so I have to extend the View to include a chunk of Java code. Still MVC as long as I separate it from the Controller code. However, I'm stuck with the WOComponent being part of the View, and also the Controller due to pageWithName. _javascript_ isn't an option as our client has it turned off for security policies.
I suppose it's just the nature of webapps that the "Page" is both View and Controller, though it's good to separate these code-wise. WO makes a good attempt at this, as long as the View logic doesn't go beyond boolean.
John
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden