On Mon, 10 Jun 2002, Perrin Harkins wrote:
> Those are both interesting and may be the most appropriate solution for > the problems you're working on, but I wouldn't call either of them MVC. > You are going straight to a view (template) and letting it drive all > the decisions. In an MVC application, you would go to a controller that > would do some work and then decide which view to show. You are right, I know this problem, but think at components as second level controllers, where i can work with Model and View. The ugly thing is having html, which belongs to View, in two places with Controller in the middle. The main focus here is to be friendly with ui people, shifting reusability towards them. Thank you for your comment! Ciao, Valerio Valerio Paolini, <http://130.136.3.200/~paolini> -------------------------------------------------- what is open-source about? Learn, and then give back
