>Mike, did you take any measurements? Was the reflection data static or
>per-instance? I would expect that the traits information for properties would
>be as efficient or more efficient than metadata. And the >memory overhead of
>describetype would outweigh the memory of data structure.
Yes,
On 3/8/12 10:38 AM, "Michael A. Labriola"
wrote:
>> Sounds like a plan! :) Can't wait to see what you've been up to :)
>
> IMO, this is just the place to handle these things. It does mean we build more
> data structures and that does mean more memory use. However, I think we could
> let peopl
>Sounds like a plan! :) Can't wait to see what you've been up to :)
IMO, this is just the place to handle these things. It does mean we build more
data structures and that does mean more memory use. However, I think we could
let people opt out of that tradeoff.
I have a really simple Guice styl
>
> >Having the compiler add this kind of reflection info would be awesome.
>
> As soon as we have compiler bits in SVN I can share what I have done. It
> is no way production worthy, however, this was the basis of the work I did
> to make injection more performant in the SDK itself.
>
> I identify
>Having the compiler add this kind of reflection info would be awesome.
As soon as we have compiler bits in SVN I can share what I have done. It is no
way production worthy, however, this was the basis of the work I did to make
injection more performant in the SDK itself.
I identify kept metada
>
> > to be precise, reflection is present in flash player (via
> > describetype) but the queries about structure of some class are not
> > cached, and accessible as xml not as a collection or something
> > similar.
> And performance of describetype is poor and probably the lowest priority
> featur
On 3/8/12 8:12 AM, "Jarosław Szczepankiewicz"
wrote:
> to be precise, reflection is present in flash player (via
> describetype) but the queries about structure of some class are not
> cached, and accessible as xml not as a collection or something
> similar.
And performance of describetype is
to be precise, reflection is present in flash player (via
describetype) but the queries about structure of some class are not
cached, and accessible as xml not as a collection or something
similar.
2012/3/7 Alex Harui :
>
>
>
> On 3/7/12 9:08 AM, "Stefan Horochovec" wrote:
>
>> Well
>>
>> In my p
On 3/7/12 9:08 AM, "Stefan Horochovec" wrote:
> Well
>
> In my previous email I suggested was a reflection API built into the
> Flex SDK, and also cited an example a third API that does this, but at
> no time I said that we should copy, request that was donated, so I
> suggested that was deve
Well
In my previous email I suggested was a reflection API built into the
Flex SDK, and also cited an example a third API that does this, but at
no time I said that we should copy, request that was donated, so I
suggested that was developed this feature natively, as there is in
Java eg
http://doc
On Wed, Mar 7, 2012 at 8:59 AM, Brent Arnold wrote:
> I believe the purpose of this mailing list and project is to allow for
> lazy consensus on additions/updates to the Apache Flex SDK.
>
I agree here.
>
> I don't think there's anything wrong with people suggesting
> changes/updates/additions
I believe the purpose of this mailing list and project is to allow for
lazy consensus on additions/updates to the Apache Flex SDK.
I don't think there's anything wrong with people suggesting
changes/updates/additions, they just need to back it up with code so the
community can act on it. So if
On Wed, Mar 7, 2012 at 8:53 AM, Pierangelo Mancusi <
pierangelo.manc...@gmail.com> wrote:
> i think Stefan said to implement in Sdk, not to import that project :-)
>
> good idea for me
>
Implement in what? Can you be more specific? What exactly do you want the
reflection APIs implemented on? Just
i think Stefan said to implement in Sdk, not to import that project :-)
good idea for me
Il giorno 07/mar/2012 17:47, "Stefan Horochovec" <
stefan.horocho...@gmail.com> ha scritto:
> Understand..
>
> In my mind went the idea of creating a more robust SDK, including
> some API that are required fo
>
> The main focus is to supplement the missing components in the spark?
>
> Att
>
> --
> Stefan Horochovec
> Software Engineer
> Blog: http://www.horochovec.com.br/
> Twitter: http://twitter.com/horochovec
>
>
The main focus is to continue to move the Flex SDK forward, Spark, MX and
future version
Understand..
In my mind went the idea of creating a more robust SDK, including
some API that are required for various projects, but anyway, it was
just an idea launched.
The main focus is to supplement the missing components in the spark?
Att
--
Stefan Horochovec
Software Engineer
Blog: http
I agree with Mike, people can use it without flex framework.
Gilmar.
On Mar 7, 2012 1:23 PM, "Michael A. Labriola"
wrote:
> >Today, the as3-commons-reflect [1] is widely used, but I believe the best
> option would be to add this feature natively.
>
> I disagree. That project has many uses and a
Agree with Mike here. I think primarily Flex is an application component
set. If we start trying to put everything and the kitchen sink into it it's
going to turn into Zend Framework, and that's kind of a mess.
-omar
>Today, the as3-commons-reflect [1] is widely used, but I believe the best
>option would be to add this feature natively.
I disagree. That project has many uses and a lifetime far outside of the Flex
framework. That would mean everyone interested in those APIs would need to use
the Flex SDK (if
19 matches
Mail list logo
