Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of lekant@gmail.com designates
 209.85.210.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <96F927F3-4265-4DC8-AEF8-EB4003B23C1F@gmail.com>
References: <96F927F3-4265-4DC8-AEF8-EB4003B23C1F@gmail.com>
From: =?UTF-8?Q?Quentin_Le_H=C3=A9naff?= <lekant@gmail.com>
Date: Wed, 11 Jan 2012 16:41:08 +0100
Message-ID: 
 <CA+tHAFS=vc+A7yZz1piWcwtCidyW+g8w3ZJ1dMZL3V7VFRjiZQ@mail.gmail.com>
Subject: Re: Goal for Flex: Strengthening large-scale Flex applications
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=e89a8ff24d9f1c4f2f04b6427778

--e89a8ff24d9f1c4f2f04b6427778
Content-Type: text/plain; charset=UTF-8

>
> As part of my research, for now I think "Building large-scale
> Flex applications is simple" is a false-proof statement. If you
> don't believe that, please have a look to all those Flex application
> which have to deal with more then 150 MXML files and all their
> worries and issues they ran into during the last couple of years:


I may be wrong, but 150 mxml files is not that huge :) depending if the
size of each mxml you have, personnaly I make them as much minimal as
possible.
This is much about optimizing updateDisplayList, validation and all these
stuffs
But you are right about Flex performance. IMO, designing a more modular
component that allow to do less validation in a sense that it should be
more smart, is a good direction.

I propose to list all bad design we know about the Flex 3 and 4 frameworks
and propose technical/designs solutions ; should the JIRA do the stuff?

On Wed, Jan 11, 2012 at 10:59 AM, Sebastian Mohr <masuland@gmail.com> wrote:

> I would like define a goal for future versions of Flex:
>
> Goal: "Strengthening large-scale Flex applications"
>
>
> http://code.google.com/p/masuland/wiki/WhatsWrongWithFlex#3.1._Strengthening_large-scale_Flex_applications
>
> As part of my research, for now I think "Building large-scale
> Flex applications is simple" is a false-proof statement. If you
> don't believe that, please have a look to all those Flex application
> which have to deal with more then 150 MXML files and all their
> worries and issues they ran into during the last couple of years:
>
>  * Heavy code rewrites and refactoring
>  * Migration from Flex 3 to Flex 4 issues
>  * Upgrading or switching the Microarchitecture (Cairngorm, Mate, PureMVC,
> Robotlegs, Parsley, Spring AS, Swiz)
>  * etc ...
>
> A more complete list of things that effect large-
> scale Flex applications can be found here:
>
>
> http://code.google.com/p/masuland/wiki/WhatsWrongWithFlex#2.2._What's_negative
> ?
>
> Please read and disagree,
>
>
> -- Sebastian
>
>
>

--e89a8ff24d9f1c4f2f04b6427778--