> Isn't this version 2.0? Or does the component source share almost no code with 1.x versions of Flex?Ah well it's 2 but.. It's 1 in my eyes. This shares the same algorithms in layout. Which is what I am mainly concerned with. As far as I am concerned, it is version 2 Flex, version 1 Flex AS3.
10, 2006
9:21 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] request
for adobe: stop being so private
Flex 2 framework is almost a total revamping, few things were shared from v1.5,
guess they still need time to sharpen it a bit.
and just like you, for so many times I
Flex 2 framework is almost a total revamping, few things were shared from v1.5, guess they still need time to sharpen it a bit.
and just like you, for so many times I have to clone the whole class
just to modify some of the variables marked private, and ends up with
lot of dupe stuff inside, t
Isn't this version 2.0? Or does the component source share almost no code with 1.x versions of Flex? I would have expected a 1.x version to be more raw.BTW, I finally gave up on the extension and just cloned the classes. Unfortunately, now my HDividedBoxExt doesn't display properly in FB. Ev
Hey,I totally agree with you. ;-) Most of what you said I have run into myself. What I have done? I created an extended framework from the Container and use composition(this is mainly for major dnd stuff though).
I know that doesn't solve your problem with say the divided box, you just want to e
Michael,I understand why things are marked as private versus protected. What I'm suggesting is that enough thought isn't going into it and a LOT of stuff is being marked as private that shouldn't be. This is hobbling component extension. I have dealt with a lot of frameworks and they generall
> mark things as protected by default, not private.I disagree, there is good reason why they marked some thing private. I agree that there are things that should be protected like in the TabNavigator etc.
The implications of marking things default protected go far beyond the desire to get at eve
I second thatOn 8/10/06, Pan Troglodytes <[EMAIL PROTECTED]> wrote:
Time and again, I have tried extending components only to find that the important stuff is marked private. I suggest this approach for adobe: mark things as protected by default, not private.
Time and again, I have tried extending components only to find that the important stuff is marked private. I suggest this approach for adobe: mark things as protected by default, not private. Only mark something as private if you're really, really sure it should never be overridden by someone
9 matches
Mail list logo
