Re: Implementing Model-View-Controller

[derby]

You don't say if you're doing web based apps or console based apps?

If web based, I'm a big fan of CGI::Application - where it's the controller, your model is a package that defines your user object and the view is whatever template system you choose.

You really don't want to wrap the three parts of MVC into a single OO hierarchy but you could wrap the three individually into seperate OO hierarchies.

In practice, my controllers have always been simple derived classes of CGI::Application (I prefer to have logging embedded into the controller). The model is where I tend to get a bit crazy but it all depends on what your modelling. If you have only one user type than your model can be simply one class. The view has always been pretty simple too but then again I eschew most of the power of my template system (HTML::Embperl) and prefer a USES relationship for my template parts (headers, footers, sidebars, etc) to an ISA one.