Before we switch to it, we have to be absolutely sure of when it was first supported. I wouldn't want to break our Flash version compatibility range. But otherwise, I have no objections if you want to switch to it.
-Alex On 10/10/13 9:13 AM, "Maurice Amsellem" <maurice.amsel...@systar.com> wrote: >Well , surprisingly enough, it's not in any of the official Adobe docs >:-( . > >I have reviewed the release notes of FlashPlayer 10.1 to 10.3 => not any >mention. > >Not in the asdocs either. > >However, it's in the playerglobal.swc (flash.utils.describeTypeJSON) >and it's already used in some of IOC frameworks that heavily depend on >reflection and other well know libs: > >- Parsley: >http://www.spicefactory.org/parsley/docs/2.4/manual/?page=view§ion=con >fig_explicit >Search for describeTypeJSON >- as3-commons: >http://www.as3commons.org/as3-commons-reflect/introduction.html > >And I am using it every day, I can tell you it's much faster (I will do >some benchmarks on typical UI component reflection and post them to this >list). > >I am confused... > >Maurice > > >-----Message d'origine----- >De : Alex Harui [mailto:aha...@adobe.com] >Envoyé : jeudi 10 octobre 2013 17:55 >À : dev@flex.apache.org >Objet : Re: describeType still used in many places in SDK > > > >On 10/10/13 7:25 AM, "Maurice Amsellem" <maurice.amsel...@systar.com> >wrote: > >>Hi, >> >>While digging into MXML binding code, I discovered it was using >>DescribeTypeCache class, which is still relying on the old >>describeType() XML instead of the new describeTypeJSON() >> >>Hopefully, it's only called in some specific binding situations, such >>as using a Binding expression on non-bindable property, on untyped props. >> >>Morevoer, describeType seems to be called in a number of other places, >>notably: >> >>- Mx:DataGrid.itemEditorItemEditEndHandler >> >>- AbstractMessage getDebugString() [ not used in runtime ] >> >>- Etc... >> >>Shouldn't it be deprecated since FP 10.x in favor on describeTypeJSON, >>which is much faster ? >Interesting. Never heard of this API and it isn't in my copy of the >documentation. Can you point me to it? > >-Alex >
