FlashTeam and questionable content
Well TGIF ....
There is thread running over on the FlashTeam blog, it has become a sort of IDE wishlist cool...
Anyway I thought i would add my 2cents worth
... but I got rejected ...
apparently my posting contained ***questionable content***
Well here it is in its completley uncensored form and if you are under the age of 45 or of a sensitive nature please view with a parent thank you....
If I could only have two features in the next version of Flash they would be
1) UNINSPECTABLELIST MetaTag. This has caused me so much grief in adding new props only to forget some inherited class had an inspectablelist to exclude some completley unrelated prop and as such it wouldnt reflect my new prop till I found the class and amended its inspectablelist.
2) Store text/xml docs in the library. Would be great to store config/menu xml docs in the Library as a resource that could be retrieved at runtime. Sure you can load from an external url but there are many instances where it would be better to store this in the library... as a twist on this... components could acces info in an xml file say with basic config info that they included in the swc.
3)Not a realistic wish as I am sure this is never going to happen but... I would like to be able to change style info(className) at design time and see the changes reflected immediatley, this would work if only the component could access some central repository of user defined style data in the IDE.