I'm wondering if we should go to MVC modelling for Claroline 2.0. It
seems that a lot of frameworks tend to use MVC, or at least offer
tools to build a MVC app.
So the question is :
Should we build Claroline 2.0 on a MVC pattern or not ?
What are your pro/contra ?
I think that the core of the Claroline 2.0 should be based on a stable
and proven pattern, and well ... the MVC pattern has been used
successfully for years in thousands of web apps. Maybe there are
another ways of doing things (even better), but if you are not going
to develop a general purpose PHP framework, I would reduce the
experiments to the minimum ;-) .
I would not consider as an option starting Claroline 2.0 from scratch,
nowadays you can find some php frameworks that can reduce the time and
effort of developing web apps, and most of them are MVC frameworks. I
really like these ones:
These frameworks usually provide (by themselves or using other
libraries):
-Database abstraction
-Internationalization/localization tools
-Ajax integration
-MVC request processing
-Templating system
-Unit testing
-Form helpers
-Application management tools
-Logging
-Extending mechanisms
The big problem that I find with the MCV part of these frameworks is
that when you start to use one, it's quite difficult to change to
another one. Because of this, the decision of which one to choose,
should be largely meditated.
I use symfony for web application development, and it helps us a lot
to reduce the time and effort of web development. It helps us to
concentrate in the problem that we are solving, and reduces the time
wasted in web development specific problems. I think that the best
advantage of the MVC pattern is that it helps to organize the work and
split the tasks between developers with different skills (designers,
web developers, database designers, etc. )
Redards,
Diego.
On 13 Feb, 16:48, "Seb`pir" <s.pir...@gmail.com> wrote:
> I'm wondering if we should go to MVC modelling for Claroline 2.0. It
> seems that a lot of frameworks tend to use MVC, or at least offer
> tools to build a MVC app.
> So the question is :
> Should we build Claroline 2.0 on a MVC pattern or not ?
> What are your pro/contra ?
Starting Claroline 2.0 from scratch is not an option anymore. Its best practice and les time consuming to be confident with existing frameworks.
My personnal choice was rather Zend Framework as, so far as I know, it doesn't force you to use MVC and doesn't force to use a particular MVC structure. Maybe is it possible in other frameworks you point but I do not know them enough. But as you say, the choice must be largely meditated. I suggest another mailing-list thread for that anyway.
I like MVC concept because of the advantages you point in your message and its why I think we should start using it for 2.0
> I think that the core of the Claroline 2.0 should be based on a stable > and proven pattern, and well ... the MVC pattern has been used > successfully for years in thousands of web apps. Maybe there are > another ways of doing things (even better), but if you are not going > to develop a general purpose PHP framework, I would reduce the > experiments to the minimum ;-) .
> I would not consider as an option starting Claroline 2.0 from scratch, > nowadays you can find some php frameworks that can reduce the time and > effort of developing web apps, and most of them are MVC frameworks. I > really like these ones:
> These frameworks usually provide (by themselves or using other > libraries): > -Database abstraction > -Internationalization/localization tools > -Ajax integration > -MVC request processing > -Templating system > -Unit testing > -Form helpers > -Application management tools > -Logging > -Extending mechanisms
> The big problem that I find with the MCV part of these frameworks is > that when you start to use one, it's quite difficult to change to > another one. Because of this, the decision of which one to choose, > should be largely meditated.
> I use symfony for web application development, and it helps us a lot > to reduce the time and effort of web development. It helps us to > concentrate in the problem that we are solving, and reduces the time > wasted in web development specific problems. I think that the best > advantage of the MVC pattern is that it helps to organize the work and > split the tasks between developers with different skills (designers, > web developers, database designers, etc. )
> Redards,
> Diego.
> On 13 Feb, 16:48, "Seb`pir" <s.pir...@gmail.com> wrote:
>> Hi all,
>> I'm wondering if we should go to MVC modelling for Claroline 2.0. It >> seems that a lot of frameworks tend to use MVC, or at least offer >> tools to build a MVC app.
>> So the question is :
>> Should we build Claroline 2.0 on a MVC pattern or not ? >> What are your pro/contra ?
Se?bastien Piraux wrote: > I like MVC concept because of the advantages you point in your message > and its why I think we should start using it for 2.0
Hello,
I think using MVC in Claroline 2.0 is really a good idea. It will bring a lot of flexibility to the application.
On the other hand, MVC often reduce the performance of an application when combined to database mapping. I think this must be remembered when developing the application kernel.
Pour info je vous fait suivre un message posté par un utilisateur sur la liste AFUP et qui résume assez bien ma vision des templates PHP :
"Certes, un système de template est fortement utile pour implémenter MVC. Mais PHP étant un moteur de template on peut implémenter MVC facilement, sans pour autant rajouter de librairie de templates. Dans les faits, c'est ma réalité d'aujourd'hui, utiliser un php très simple qui se contente d'afficher au sein du HTML. Tout le travail est réalisé dans des itérateurs, tant pour le formatage que les traitements. Et honnêtement, entre un template PHP et un template Smarty, je vois la même complexité, et les mêmes difficultés pour un non développeur. Donc autant rester simple, non?"
