It's easy to be horrified by under and over-use of patterns / frameworks. Especially in a world where Cairngorm is pushed as a good idea.
I took to PureMVC precisely because there's pretty much nothing to it, very limited time spent doing anything framework-y, definitely not a heavy-handed, this-framework-should-do-everything-approach. Just lovely decoupled classes communicating via the tried and tested observer pattern using notifications, instead of the not-so-good Adobe event system (which you thankfully restrict to just the view classes). Application logic wrapped up in commands that map to notifications, business logic wrapped in your models, and complete separation of view and model classes allowing easy unit testing (no need to worry about the framework being pulled in). I can only speak from experience in the London agency world, but very quickly Flash teams have started picking it up as the primary framework for most app development. Thankfully I'm now seeing lots of contractors coming through with PureMVC experience, which is making hiring less painful. I suppose it being an open-source framework keeps the discussion a litle relevant ;) Jaakko Manninen wrote: > Most of you seem to be against using the pattern on this list. So what > would you suggest doing instead of using MVC to achieve the same > goals? MVC certainly has its applications and will inherently help you > organize things well in those scenarios, given a proper implementation > and use :) I'm sure everyone understands that it doesn't apply > universally to every software project. > > Why is this relevant to this list? > > Jak > > On Tue, Oct 21, 2008 at 12:14 AM, Scott Langeberg <[EMAIL PROTECTED]> wrote: > >> I've shuddered to find classes typed: Model, View, Controller in projects >> I've been assigned to work on. ;) >> >> -Scott >> >> On Mon, Oct 20, 2008 at 3:28 PM, Robin Debreuil <[EMAIL PROTECTED]> wrote: >> >>> For a horrifying look at over-pattern-itis, have a look at the eclipse >>> source code. Not to say patterns aren't useful, but they aren't useful to >>> the point that they should be treated as some high level language >>> construct >>> (at least the ones that haven't migrated to become that already : ). Often >>> something being an 'approved pattern' is treated as sufficient >>> justification >>> to use it, which of course is crazy. It is something like saying, 'my code >>> has no bugs because it has unit tests'. >>> >>> Computer Science at any time is 60% fashion -- you have to constantly be >>> on >>> guard for these things. >>> >>> Cheers, >>> Robin >>> >>> -----Original Message----- >>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On >>> Behalf Of sebastian >>> Sent: Monday, October 20, 2008 2:20 PM >>> To: Open Source Flash Mailing List >>> Subject: Re: [osflash] Q:Basic AS3 MVC question >>> >>> 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 >>> >>> >>> _______________________________________________ >>> osflash mailing list >>> [email protected] >>> http://osflash.org/mailman/listinfo/osflash_osflash.org >>> >> >> -- >> : : ) Scott >> >> Helping your grandma on the interweb >> at: http://blog.criticalpile.com >> >> _______________________________________________ >> 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 > _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
