Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 28878B8FA for ; Wed, 4 Jan 2012 21:52:25 +0000 (UTC) Received: (qmail 38910 invoked by uid 500); 4 Jan 2012 21:52:25 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 38825 invoked by uid 500); 4 Jan 2012 21:52:25 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 38817 invoked by uid 99); 4 Jan 2012 21:52:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jan 2012 21:52:25 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of frederic@exuvis.com designates 216.134.213.70 as permitted sender) Received: from [216.134.213.70] (HELO smtp01.myhostedservice.com) (216.134.213.70) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jan 2012 21:52:19 +0000 Received: from EXHUB01.netplexity.local (172.29.211.21) by smtp01.myhostedservice.com (172.29.211.11) with Microsoft SMTP Server (TLS) id 14.0.722.0; Wed, 4 Jan 2012 16:51:46 -0500 Received: from EXMBX06.netplexity.local ([fe80::2853:4ba5:77bd:619e]) by EXHUB01.netplexity.local ([fe80::400:895c:b5fb:2417%11]) with mapi; Wed, 4 Jan 2012 16:51:58 -0500 From: =?iso-8859-1?Q?Fr=E9deric_Cox?= To: Apache Flex Mailing List Subject: Re: Flex performance Thread-Topic: Flex performance Thread-Index: AQHMyyc8hFSkOboeVkiC9FQLt7RGM5X9ExYAgAASgQA= Date: Wed, 4 Jan 2012 21:56:06 +0000 Message-ID: In-Reply-To: <619FF30DF29E46C388807294826A807E@ajobi.net> Accept-Language: nl-NL, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.0.0.100825 Content-Type: text/plain; charset="iso-8859-1" Content-ID: <3c049443-8dc9-4ce4-8da7-6aae50767015> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org And it's not only on mobile, on desktop (mostly Mac's) this is a problem also. I'm talking about big enterprise applications and websites here (like a CMS with graphical skin applied, nothing really in standard Flex skin) On 04/01/12 22:49, "Arthur Lockman" wrote: >+1 on this. Performance definitely needs to be addressed on Flex. I've >noticed that on newer devices, it works fine. But on the slightly older >ones, performance is a huge issue. Hopefully we can get in there and >clean it up so it performs better. > > >-- >Arthur Lockman | Senior Developer @ Vivace >vi.vace.me >Twitter: @arthurlockman >a.rthr.me > > >On Wednesday, January 4, 2012 at 4:28 PM, Fr=E9deric Cox wrote: > >> I've worked on Flex applications for the past 4-5 years and see a lot >>of developers picking it up since it is easy to create rich >>applications. However performance is often an issue. >> =20 >> I mostly see it when using a lot of styles (or one large CSS file) and >>skinned components (It is even worse with Flex 4 then it was with Flex >>3). When a Flex application gets really large the UI is blocked because >>there is too much actionscript code needed to get things running. (with >>this I mean the processing time is acceptable but UI is blocked so the >>perception is that things are slow) >> =20 >> Therefore I'd like to vote on improving the performance of the Flex >>framework where possible so new and existing applications can benefit. >>Flex 4 with spark is great but comes with some performance drawbacks, I >>hope we can improve on this significantly. >> =20 >> I'm speaking on behalf of the experience and perception in the company >>I work for, I'm curious to see if this is also a problem for the rest of >>you. >> =20 >> I'm not the expert here but I'd like to get involved and learn so I can >>eventually help to fix issues but I believe UIComponent had some >>overhead and this together with the StyleManager can cause performance >>drawbacks in large applications >