Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Your question somewhat smells like <a href="http://en.wikipedia.org/wiki/Not_Invented_Here" rel="noreferrer">Not-Invented-Here-Syndrome</a>. In this case, my advice would be to live with the extra baggage of existing frameworks when you can be sure they are thoroughly tested and supported. <a href="http://sourcemaking.com/antipatterns/reinvent-the-wheel" rel="noreferrer">Don't reinvent the wheel</a>.</p> <p>On the other hand, the above argumentation would prevent new frameworks to be written. And writing one from scratch <em>is</em> a good coding exercise to learn and understand the MVC pattern. </p> <p>So if you are really determined to do it, my suggestion is to learn <a href="http://www.martinfowler.com/eaaDev/uiArchs.html" rel="noreferrer">what each part of MVC is, does and how they interact</a>. You will inevitably come across the <a href="http://en.wikipedia.org/wiki/Front_Controller_pattern" rel="noreferrer">FrontController pattern</a> as well, so you will want to learn about this one too.</p> <p>Note that you are not the only person wanting to do this:</p> <ul> <li><a href="http://www.google.de/search?q=front+controller+php" rel="noreferrer">http://www.google.de/search?q=front+controller+php</a></li> <li><a href="http://www.google.de/search?q=build+your+own+mvc+php" rel="noreferrer">http://www.google.de/search?q=build+your+own+mvc+php</a></li> </ul> <p>And there is also this interesting article by Rasmus Lerdorf</p> <ul> <li><a href="http://toys.lerdorf.com/archives/38-The-no-framework-PHP-MVC-framework.html" rel="noreferrer">http://toys.lerdorf.com/archives/38-The-no-framework-PHP-MVC-framework.html</a></li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload