RE: [flexcoders] Re: CairngormEvent Antipattern

[Steven Webster]

Are you using source-code control systems like CVS or Subversion ?  These tools solved the problem a long time ago, of having multiple developers editing the same source file at the same time ... let the tools handle the problems of merging the controller when someone checks in their code.   If developers are checking-in/committing code that breaks a build, that's a development process problem, not a technology or architecture problem.   Developers should not be "fighting for control" of a class ?!?  Nor should they be emailing around changes to code.   Apologies if this is teaching you how to suck eggs; if not, then google for subversion or cvs and get that in place as soon as possible!   Best,   Steven   Steven Webster Practice Leader (Rich Internet Applications and LiveCycle) Adobe Consulting Westpoint, 4 Redheughs Rigg, South Gyle, Edinburgh, EH12 9DQ, UK p: +44 (0) 131 338 6108 m: +44 (0) 7917 428 947  [EMAIL PROTECTED]   From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of e_baggg Sent: 31 August 2006 03:39 To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: CairngormEvent Antipattern Andi- Tom was referring to having a hierarchy of FrontControllers. He happens to have a class called "CoreController" which all of his Flex apps would use. Then, each Flex app will have it's own FrontController that extends CoreController...this way each developer has their own controller. This assumes of course there's 1 developer working on a project. The CoreController would house the common Commands such as Login, Logout, and similar things. If you're in the situation where you have 1 large Flex app that has 1 large controller that all the developers are fighting for...I would suggest that users update the Contoller and check in their empty Command classes right away. Then begin development. That way if it takes them 2 days to implement the logic for an event, they won't have a lot of contacts. Another option is to make one developer the 'owner' of the front controller and have other developers e-mail them the line of code for the command. --- In [EMAIL PROTECTED]ups.com, Andrea Varga <[EMAIL PROTECTED]> wrote: > > Tom Chiverton wrote: > > >On Wednesday 30 August 2006 13:14, Andrea Varga wrote: > > > > > >>(For example, on a large project, when there are many developers > >>working, all of them has to edit the FrontController to add an event.) > >> > >> > > > >This isn't a problem with a decent RCS. > > > >As it is, we've got a CoreController and then indivdual projects extend that > >to make their application specific events. > > > > > > > Could you please tell me where can I found more about this? I cannot > find anything. Thanks. > > Andi > __._,_.___ -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com SPONSORED LINKS Software development tool Software development Software development services Home design software Software development company YAHOO! GROUPS LINKS  Visit your group "flexcoders" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. __,_._,___