incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Omar Gonzalez <omarg.develo...@gmail.com>
Subject Re: Flex 5 UIComponent - Behavior Pattern
Date Mon, 23 Jan 2012 18:24:33 GMT
On Mon, Jan 23, 2012 at 10:19 AM, Bogdan DINU <flex.programming@gmail.com>wrote:

> Hey,
>
> you haven't answered my reply question : "what should we favor ?
> Inheritance ?Composition ?". I would really love an answer :)
>

There is no black or white answer. Each decision on whether to inherit or
compose features will have to come down to performance testing to be able
to measure the pros and cons of such decisions. We can sit here and
pontificate on the ideal architecture until we are blue in the face but
without performance tests to back it up then its just hot air. The answer
will likely be both, with careful consideration as to how many new objects
we introduce into such a huge component like UIComponent while continuing
to increase the speed and not weight it down.


>
> Now, those Spark "things" are dependent on whom has the "teacher" and why
> they did it like that. I have nothing to confess, but the fact that in my
> company everything is OK.  Why ?  Because certain concepts where introduced
> when they were mature enough... In other words, no matter how much complex
> is that component, I really don't believe that they could complicate it
> beyond speed of Flex 4.0...
>
> Last but not least, performance consideration were always in our heads (me,
> you, the world). I'm also really sure that you do this as the last thing
> before handing over the product, not to impress, not to show yourself
> something, but passing through iteration 2 to apply the real optimization
> that you have foreseen when you've started the "poison" (sorry, misspell :
> it's "project").
>
> Looking forward for your reply, please have my best regards!
>
> Bogdan
>

I'm not really sure what you're trying to get at with the rest of your
reply, sorry.

-omar

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