Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of banas.iwo@gmail.com designates
 209.85.214.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <6b670eec$5b9b2c5a$529e4a03$@com>
References: <6b670eec$5b9b2c5a$529e4a03$@com>
Date: Mon, 16 Jan 2012 20:45:30 +0000
Message-ID: 
 <CAD0VuCJ358+6216SfRNJ5gSAYQzYZF0cS+i+N4veW5Po++0qSw@mail.gmail.com>
Subject: Re: Flex "code cleanup"?
From: =?UTF-8?Q?Iwo_Bana=C5=9B?= <banas.iwo@gmail.com>
To: flex-dev@incubator.apache.org, flex@rduartes.net
Content-Type: text/plain; charset=ISO-8859-1

On 16 January 2012 12:13, Rui Silva <flex@rduartes.net> wrote:
> But, yes, it would be interesting if people just scanned the framework for
> unused code and post those here so they can be validated by people with
> more knowledge and an eventual elimination of that code could stem from
> that.

I don't think there will be that much unused code. The bigger issue is
that there is a lot of code which is executed unnecessarily. (Doug
pointed this in the other thread)
e.g. if your application is using only minimal CSS you still pay a
price (performance and swf size) of full-blown styling. Unfortunately
this can be addressed only partially without major API changes.

Some of the dirty-looking code is there for backward compatibility.
Loosening the backward compatibility constraints would give us a whole
new area for improvements but compatibility management is an important
topic worth a separate thread.

Cheers,
Iwo