incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Om <bigosma...@gmail.com>
Subject Re: Flex 5 UIComponent - Behavior Pattern
Date Tue, 24 Jan 2012 22:08:05 GMT
+1 to creating a sample application or at least templates of applications
that we build with different SDKs(built with different approaches).  It
would give us a concrete target to work towards.  I can help with this
effort.

Om

On Tue, Jan 24, 2012 at 12:40 PM, Rick Winscot <rick.winscot@gmail.com>wrote:

> If anyone is interested in squeezing out n-th degree performance out of
> Flash... they've probably bumped into apparat.
>
> https://github.com/joa/apparat
>
> Adding constructs upon constructs in code amounts to entropy in ABC.
> De-composition, composition, inheritance, etc... all have costs and
> benefits which shift dramatically depending upon the application. IMO, the
> best way to settle the discussion is to take a given test to measure
> performance and start creating samples for evaluation ( e.g. whiteboards ).
>
> --
> Rick Winscot
>
>
> On Tuesday, January 24, 2012 at 3:06 PM, Michael A. Labriola wrote:
>
> > That is actually my preference and the reason I was mentioning things
> like AOP at the summit. We could keep the classes nicely designed but not
> pay the priced at runtime.
> >
> > -----Original Message-----
> > From: Alex Harui [mailto:aharui@adobe.com]
> > Sent: Tuesday, January 24, 2012 12:32 PM
> > To: flex-dev@incubator.apache.org (mailto:flex-dev@incubator.apache.org)
> > Subject: Re: Flex 5 UIComponent - Behavior Pattern
> >
> >
> >
> >
> > On 1/24/12 10:20 AM, "Haykel BEN JEMIA" <haykelbj@gmail.com (mailto:
> haykelbj@gmail.com)> wrote:
> >
> > > I'm curious to see your work Alex. Were you able to do some
> > > performance and memory tests with your prototype?
> > >
> > > Haykel
> > Further back in this thread I stated that the prototype was not faster
> because of 'interstitial' costs: the cost of adding an additional function
> call to get to the subobject that actually does the work.
> >
> > I think you have to give up on something: backward-compatibility,
> keeping certain high-bandwidth 'behaviors' baked in', memory footprint, in
> order to get gains.
> >
> > Or do something more clever like figuring out how to do post-process
> optimization of the SWF that can set up tail-call optimizations and reduce
> the interstitial cost.
> >
> > --
> > Alex Harui
> > Flex SDK Team
> > Adobe Systems, Inc.
> > http://blogs.adobe.com/aharui
> >
> > Notice: This transmission is intended only for the use of the individual
> or entity to which it is addressed and may contain information that is
> privileged or confidential. Any dissemination, distribution or copying of
> this transmission by anyone other than the intended recipient is strictly
> prohibited. If you have received this transmission in error, please notify
> the sender immediately by e-mail or telephone and delete the original
> transmission. Thank you.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message