[FLEX-34138] Divide Flex into several modules so that it can be used more widely

• Type: Wish
• Status: Reopened
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Gary Yang
• Created: 12/Mar/14 15:49
• Updated: 02/Apr/14 15:10

Description

Just some thoughts, might be worth discussing more:

Flex divided into multiple modules:

Flex tools: 1) Mxml to AS;2)Meta process;3)Other code generation and automation; 4) Maven integration;

Flex Data: 1) Binding and List Synchronizing; 2) 0 UI component; 3) Pure model reacting repeatable model;

Flex UI: 1) UI components and skinning; 2) States;

Serverside ---- bridge between server domain and presentation domain 1) DTO; 2) Model synchronizing;

Issue Links

• incorporates: FLEX-34137 Flex App swf initialization failure when working as an Android worker!!!!
• relates to: FLEX-34143 Give <fx:Binding /> an event handle.
• relates to: FLEX-34146 Add a Map structure( key->value ) which will dispatch MapPropertyChangedEvent( a PropertyChangedEvent with a key property ) when value is changed.
• relates to: FLEX-34202 Add PropertyChangingEvent and CollectionChangingEvent so that developers can handle before change happens.