flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-34138) Divide Flex into several modules so that it can be used more widely
Date Wed, 02 Apr 2014 15:11:15 GMT

    [ https://issues.apache.org/jira/browse/FLEX-34138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957772#comment-13957772

Gary Yang commented on FLEX-34138:

"14 000 lines of codes for UIComponent" is not only hurting the performance, but also scare
developers away from looking into it, the 1st version of Flex was 2004, and the architecture
has not been changed essentially: everything jammed together.

When I looked into Java Spring Framework's growth, especially from Spring2 to Spring3, modularization
gives developer great freedom to choose which feature/function/module to use.

I try to build a pure data model with IList to drive a pure AS UI, I can't exclude all the
UI component from Flex!!, it's like Windows and Explore, except not really.


> 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
> 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

This message was sent by Atlassian JIRA

View raw message