Ok, all should be fine now. I've committed an example that should show
the proper functioning of the code with some of the most common use
cases: LanguageTests.

EdB



On Mon, Nov 4, 2013 at 8:23 AM, Erik de Bruin <e...@ixsoftware.nl> wrote:
> Note: when trying to build a project using the new "Language" class
> yesterday, I noticed that the implementation is not complete. Please
> hold off on implementing it in any components until I check in some
> changes to FalconJx and the framework.
>
> EdB
>
>
>
> On Fri, Nov 1, 2013 at 3:57 PM, Alex Harui <aha...@adobe.com> wrote:
>>
>>
>> On 11/1/13 7:48 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
>>
>>>> Will we end up doing metadata and describetype following this pattern?
>>>
>>>It certainly provides an extra tool towards that goal, but depending
>>>on the requirements for both features - can you elaborate your ideas a
>>>bit - there might be other things that we can do, e.g. Closure
>>>provides some introspection tools as well.
>> The next "big experiment" is trying to cross-compile an app that uses one
>> of the app frameworks like Swiz, Parsely, etc.  Someone pointed out that
>> they use metadata and and I assume they must use describetype to fetch
>> said metadata.
>>
>> My hope is to avoid use of describetype in the FlexJS classes we write or
>> consider a lighter weight implementation for the few things we might need
>> (I recently checked in a lightweight getQualifiedClassName for CSS
>> TypeSelector support in JS), but I think we need to see if we can support
>> the existing app frameworks.
>>
>> I'm not sure we'd need full describetype support, probably just enough to
>> get the metadata.
>>
>> -Alex
>>
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Reply via email to