Flex and RSL Modules

I'm a little confused when it is better to use Flex Modules or RSL libriaries (in Flex 3.5).

My goal is to split my project into several projects, so I can test and work separately. Suppose I have a Customer application and a Vendor application. I also have an interface panel with two buttons. Each button launches the Customer application or the Vendor application.

These applications do different things. They also have some .as features and common components.

I understand that if I create a main project (for logging in and for displaying the first panel) and two modules (client, provider), I must have all these components in the Eclipse project, right?

Instead of making modules, should I create SWCs for Vendor and others for the Customer application and make calls from the main application using RSL?

So which option is more suitable? What will you advice me? What are the tradeoffs for each option?

On the other hand, this flexible application is integrated with Java through Blaze and ibatis for persistence management and is supported by the apache web server. I also considered creating independent military files to preserve this difference, but I thought that this does not optimize flexible code. I'm right?

Thank.

Zero

+3
source share
2 answers

Modules and RSL serve for different purposes.

RSL swf, .

RSL - , , - . RSL Flex Flash/ActionScript. , RSL, .

- , , SWF, , , Flex, , Flex . , SWF, . Flex , , . (, , SWF , ).

. - , . , , .

SWF, , , Flex .

RSL , . , , , RSL, .

+3

- , , - .

, RSL, .

, , .

, .

Customer and Vendor . .

, , RSL, .

+2

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


All Articles