Futurescale, Inc. PureMVC Home

The PureMVC Framework Code at the Speed of Thought


Over 10 years of community discussion and knowledge are maintained here as a read-only archive.

New discussions should be taken up in issues on the appropriate projects at https://github.com/PureMVC

Pages: [1]
Print
Author Topic: Multiple Application from the same Flex Project  (Read 7622 times)
janberc
Newbie
*
Posts: 4


View Profile Email
« on: April 16, 2009, 09:02:51 »

I am developing a Flex application using PureMVC standard. Its a large application and have multiple functionality modules (not flex or puremvc modules). Everything went well until the customer came back with a new implementation of the project with slight modification of the functionality modules. Basically, in this new application only 2 of the original functionality modules has to be used.

How can we have the same project used to create both the implementations without having to create a new project for the new application?

Can multicore with an additional Application MXML and Facade help to get a solution?

Looking forward for suggestions..

Thanks
-JB
Logged
puremvc
Global Moderator
Hero Member
*****
Posts: 2871



View Profile WWW Email
« Reply #1 on: April 16, 2009, 11:45:45 »

I'm afraid from the description of your problem that you're unlikely to get both implementations produced from the same Flex project.


Though not very pallatable, if you're pressed for time and must maintain both implementations, then tag your codebase in the repository at the current version first. Then create a branch on which this old version will be maintained. Now, on the trunk commence with refactoring your existing app into the new implementation. 

This way, in order to build the old version, you simply check out the branch and compile. In order to build the new version, you check out the trunk and compile. This assumes you're using a repository. If not you need to, so get one and check in what you have before proceeding.

Later, if you have time to make things right, then refactor the trunk to MultiCore.

-=Cliff>
Logged
Pages: [1]
Print