Hi --

I would like to design the UI of an input process, so that the user is 
presented with two screens (instead of just one), each which would ask for 
some of the necessary parameters.

What I would really like to be able to write the code is such a way that 
only the view has to be modified, should a skin with three (or four..) 
input screens be implemented.  It appears that there is a implicit coupling 
which couples the pages to the controller more tightly than I would like.

I was thinking of what might work:  perhaps a special feature in the 
controller, which will support multiple pages.  Hidden fields would be 
embedded in the forms of each page, and the perform() method would figure 
out which page has been submitted.  Then, I suppose, the controller would 
have be told to persist until the next last call to perform() or hidden 
fields in the html form could hold already entered fields.  I'm not quite 
sure how I would implement this, but perhaps if this were put in the base 
Controller class, all forms would be able to take advantage of this 
functionality for free.

Any thoughts to help me out?
Dan


_______________________________________________
Mav-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mav-user

Reply via email to