Thanks Mark ,
I prefer your definition.
Data has a nice depth to it when describing the Model. Container wasn't right at all, was it ?I've come across other definitions like business logic , core functionality.
But that's very difficult to design programmatically.
Borrowing from that other thread on MVC running in parallel, I think I'll stick with FlightModel,
- covers a few angles.
Can this and the DataAccessFacade be one and the same ? Hmmm. One Model is beginning to sound like a good idea.
In fact, Max's suggestion of 3 Views and 1 model , 1 Controller is very feasible .
Search, Select and Book/ Reserve are potentially re-usable functions for
many Models.
Having the same Look and Feel for a given Model for each of these functions across applications can only be a good thing and this can be achieved by having a re-usable view for each.
Actually , I am going to back-track on the last one, unless someone tells me other-wise.
Same Look and Feel and the MVC paradigm don't fit together very well. It will be the designer's choice to re-use a View for a given Model in another application . (we could make it easier for them, though,if needed)
1 Model, 1 Controller , 1 View as far as the assignment goes, rules the day.
Max,
thanks for the cautionary though not directive note. (You're right I could split the Views to logically separate them. Makes it easier to follow the code but I'm not going to try the re-use argument again).
Hope I am not confusing anyone else ?
[ January 28, 2003: Message edited by: HS Thomas ]
[ January 28, 2003: Message edited by: HS Thomas ]
[ January 28, 2003: Message edited by: HS Thomas ]
[ January 30, 2003: Message edited by: HS Thomas ]