All geek questions in one place

Flex Best Practices - multiple Flex projects or one project, multiple MXML application files

Having seen several different ways to create larger projects in flex, I wonder how you evaluate how to organize projects that require two or more different applications. For example, a public and private site within the project.

The two main ways that I know of will be the first to create one flex project and then add the various mxml application files. Both applications will be able to share the code.

Another way (which I currently like, but cannot be an excuse) would be to create another flexible project for each application, and any code that needs to be shared can be part of a common flex library. I think something about sharing applications that I like best, especially since I'm either working on one or the other at the same time.

What are your opinions, and do you have any reason for this, anyway?

+3
source share
3 answers

. , ( ), " , ". 5 , MXML 4 , .

+4

, . . - .

+2

. . , - . , 2 10 , , , , , , .

, , - , , .

. - ... MP3-.

com.yourdomain.applicationname.mp3controls com.yourdomain.applicationname.albumlistings

each function will contain commands, a model, view packages to run.

you may find that you really like the mp3controls function, and you can use it in some other applications, for example, as a video player application. Then mp3controls could be placed in a shared library, and then perhaps renamed to something like "mediacontrols" or something like that.

0
source

Source: https://habr.com/ru/post/1762308/

More articles:


All Articles