37 lines
1.3 KiB
Markdown
37 lines
1.3 KiB
Markdown
-----
|
|
# Built-in
|
|
filters_pre:
|
|
- erb
|
|
- "bluecloth"
|
|
|
|
# Custom
|
|
# l'article n'est pas encore prêt
|
|
isHidden: true
|
|
kind: article
|
|
created_at: 2009-07-06T16:15:23+02:00
|
|
title: MVC explained
|
|
multiTitle:
|
|
fr: Les raisons du MVC
|
|
en: Why MVC?
|
|
multiDescription:
|
|
fr: Une explication en anglais des raisons pour lesquelles l'architecture MVC a naturellement émergée. Avec la création d'un projet, du début à la fin.
|
|
en: Why MVC naturally emerged? To show that we will create a project from the beginning to the end and we'll show how natural it becomes to use an MVC architecture and all benefits. If you don't want to re-invent the wheel, you should read this post.
|
|
menupriority: 2
|
|
|
|
-----
|
|
|
|
# Why This article and for whom? #
|
|
|
|
Many website explaining how MVC works. But I can't found one who explain why.
|
|
|
|
I have difficulties to obey some principle don't know *why* I should use it. And something better than the:
|
|
|
|
> "Smarter people than you decided you have to do so"
|
|
|
|
This article is for people who like me want to understand the real motivation of using an MVC architecture and which advantage it gives you.
|
|
|
|
Let's start making a project from scratch pretending we don't know anything about the MVC architecture. Then let see how we'll naturally derive to an MVC architecture.
|
|
|
|
<center>
|
|
<p> <%= lnkto('→ Next','/blog/mvc/mvc1') %> </p>
|
|
</center>
|