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], 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 Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
