Thank you, Alex. But as I said, that's what I'm trying to avoid doing; it means that I can't supply runtime-created asset data via any other means than rewriting/extending every single Flex component that I need to do it for.
That seems completely backwards, and seems an ill-thought-out strategy in the creation of the Flex framework. Ian On 10/22/07, Alex Harui <[EMAIL PROTECTED]> wrote: > > You would write a custom itemRenderer to show bitmaps instead of class > instances. > > > ------------------------------ > > *From:* [email protected] [mailto:[EMAIL PROTECTED] *On > Behalf Of *Ian Thomas > *Sent:* Monday, October 22, 2007 8:47 AM > *To:* [email protected] > *Subject:* Re: [flexcoders] Take two: dynamic asset creation > > > > Thanks Arul, > The more I delve in to this and experiment with it the more I'm > beginning to think it's not possible. > > Ben Stucki has an interesting post on a similar solution: > http://blog.benstucki.net/?p=42 > > But it relies on you needing to know exactly which component container the > resulting object is destined for, and that won't work in TileLists (because > ItemRenderers get reused). > > Josh Tynjala has a slightly different solution: > http://www.zeuslabs.us/2007/09/28/actionscript-3-bitmap-image-classes-with-functions-and-loaders > > > But it hits the same issue that I did, which is that in AS3 > Function!=Class any more. > > It feels like it _ought_ to be easy. > > If it's really true that we can't use runtime-created assets with the Flex > framework without handrolling a load of different ItemRenderers or creating > our own subclasses of the Flex components, then that's very depressing and > seems ill-thought-out. :-( > > Cheers, > Ian >
