You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flex.apache.org by "Justin Mclean (JIRA)" <ji...@apache.org> on 2014/03/13 02:26:49 UTC
[jira] [Commented] (FLEX-34138) Divide Flex into several modules so
that it can be used more widely
[ https://issues.apache.org/jira/browse/FLEX-34138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13932751#comment-13932751 ]
Justin Mclean commented on FLEX-34138:
--------------------------------------
It's already broken up along these lines.
- binding and collections are in the framework.swc
- ui components are split among spark.swc, mx.swc, experimental.swc, mobile.swc, advancedgrids.swc and charts.swc
- the client/server code is in rpc.swc
- skins are in spark skins.swc
- text engine in textLayout.swc
> Divide Flex into several modules so that it can be used more widely
> -------------------------------------------------------------------
>
> Key: FLEX-34138
> URL: https://issues.apache.org/jira/browse/FLEX-34138
> Project: Apache Flex
> Issue Type: Wish
> Reporter: Gary Yang
>
> 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;
--
This message was sent by Atlassian JIRA
(v6.2#6252)