views:

90

answers:

1

Over the past few years I have built several MVC Frameworks and scraped them several MVC Frameworks.

Usually I build my frameworks with a startup file which loads the main components (controller/library/input/output/error/configLoader/database model loader) etc.

I'm just wondering how you build yours in an attempt for me to discover new ways to implement these features, for example when it comes to storage and models I tend to build my model system so the extends keyword loads a particular modelBase

class Model_NewsItems extends ModelStorage_CSVText{}

or

class Model_Users extends ModelStorage_DatabaseMySql{}

Which all inherit their own methods.

But in regards to the libraries controller, etc., are there any "sleek" ways to go about them in regards to larger functionality ?

Just so when I do develop my framework again it can be more reliable when it comes to extending?

Thanks in advance.

A: 

Here are two resources that use a approach to create the MVC framework:

The No-Framework PHP MVC framework (by Rasmus Lerdorf, php creator)
Model View Controller MVC (by phpro.org)

Sarfraz
Unfortunately, Both them styles are tiny, there not really hard to do or advanced, im looking for ways to develope MVC's to another level, another example, The template system i usually create consists of 2 major classes, 1 witch is available via the controller, the other witch is wrapped in all template files, so as your passing data via the controller to the view, when you tell the view to output it sends all information to the VIEWLAODER, witch compiles and has a range of functions that you can use within your views. im looking for ideas such as these that can squeeze more functionality out
RobertPitt