Extended Views

Paul,

Thanks for the feedback.

Making use of a single view that contains all the html seems very reasonable. All the data could be gathered in the controller and then sent to the main view. HTML changes made to the main view wouldn't break other views.

My thought was to use individual views to generate portions of html code (somewhat like a widget). The widgets could then be assembled in the main view. The main reason I decided to use the controller for the heavy lifting is because views can't make use of library code. By doing most of the processing in the controller, I can build code segments in libraries that produce the widgets.

How about other folks? Please comment! Thanks.

Andy