--- In [email protected], "Gordon Smith" <[EMAIL PROTECTED]> wrote: > > > if you're like me, and you're in the 20% of cases > > > the Flex developers didn't plan for 90% of the time > > > > Amy, do you think that your use cases are simply different from those of > most Flex developers? Or do you think that the Flex framework is failing > to anticipate the use cases of most Flex developers? If it's the latter, > we need to try to do a better job with Gumbo and we need folks to file > enhancement requests to help us.
I think it's a little of both, and I do have some enhancement requests stored up, but I haven't bitten the bullet and dived into the jira system :-). I can at least think of one place where the Framework is lacking, but I suspect Gumbo may already be addressing it. That place is where we have all these great building blocks like the container class, but those classes are too "heavy" for use as itemRenderers without a big performance hit. So nearly all developers who are working with itemRenderers wind up rebuilding a "light" version of the containers starting with UIComponent. I was really pleased to see that Gumbo is addressing the issue of how difficult it can be to come to grips with the component life cycle. One thing that I sometimes miss about Authorware is that in Authorware you can actually watch the screen draw as various logic executes while you're developing. I think if you could see the screen draw as the logic ran in debug mode in Flex that would help in understanding what is happening when. I know that on my husband's mac, the screen isn't totally white when he hits a breakpoint like it is on my PC, but I am not sure how real time what he sees is. Thanks :-) Amy
