Not sure I understood all that was written below, presumably due to English not being your first language.
The advantage of using good design patterns is to ensure future-scalability and the modularity of your code. I often come across code that is half-object orientated; where one class does two things instead of one, or the code is not properly encapsulated. Design patterns, or a micro-architecture such as pureMVC help us to ensure that our code follows proper separation or encapsulation. Naturally an MVC architecture is not required on a simple site, nor is a micro-architecture on a simple MVC implementation; but applied to the right scale/type of project, it can make all the [long term] difference. And a common micro-architecture makes it easy to understand new projects when old ones follow identical patterns. I'm curious as to why you have such strong negative feelings... have you struggled with projects that are over-structured? Kind, Sebastian. iteratif wrote: > The whole question is: is what you spent pureMVC because you perfectly > mastered the MVC model or rather lack of knowledge on the subject. > > Because the use of abusive patterns in the frameworks have no meaning, > it proves the lack of knowledge about the subject. Otherwise the GoF > would have done it a long time ago. > > These frameworks do live that those who create and be a shame not good > enough for you anlgais in the show technically. > > Indeed this is not the patterns or even less frameworks that guide a > project, these are the needs. So if a project does not recquire model > MVC not need to implement ... when it was well understood and we > understand the full meaning of object-oriented programming ... > > bonne continuation > Iteratif > > > _______________________________________________ > osflash mailing list > [email protected] > http://osflash.org/mailman/listinfo/osflash_osflash.org > _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
