I'm currently writing a couple of DisplayObject based components whose optimal implementation would allow their use both via MXML, AS3, or within the Flash IDE, without forcing the end-user to have either of the two component libraries. Since this means I can't use either of the UIComponent classes, UIObject or the IUIComponent interface (Since each is distributed with the associated IDE and I can't make the assumption that my end-user has both), I've written my own sprite extension class that handles some basic delayed instantiation and updating- easy enough. The catch now is that when you're trying to add anythign to an UIContainer (via MXML or addChild), it demands it implement IUIComponent, else it throws a runtime error. I have two questions: 1- Is there some elegant way of circumventing this (I'm aware of creating a second UIComponent 'wrapper' class only for use in flex- not elegant, but servicable), and: 2- If not, am I allowed to include and distribute the source for IUIComponent (with no modifications) with my own source release (BSD License, not a source of income) so that the component will compile properly? My gut instinct answers to these questions are: 1- No, unless you can implement IUIComponent, and 2- No, the license agreement prevents me from doing this. Can someone prove me wrong? Michael Krotscheck
Senior Developer
RESOURCE INTERACTIVE
<http://www.resource.com/> www.resource.com <http://www.resource.com/>
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
We support privacy and confidentiality. Please delete this email if it
was received in error.
What's new ::
Capitalize on the social web | The Open Brand, a new book by Kelly
Mooney and Dr. Nita Rollins, available March 2008 | www.theopenbrand.com
<<1c85cff_688c521c__img_1.gif>>
