Thanks. That's what I figured.
Unfortunately I will not be able to move completely over to JSON for
everything. (XML document editing capabilities is pretty important for what I
do.)
When I'm forced to start moving over to JS (probably the beginning of 2014),
I'll look into this in more detail
On 9/2/13 11:56 PM, "Harbs" wrote:
>I moved over to dev because I thought it was the right place to go off on
>this tangent...
Ah, sorry, I wasn't tracking which list it was on.
E4x emulation seems really hard, so I'm not planning on taking it on for
early versions of FlexJS. IMO, there are e
I moved over to dev because I thought it was the right place to go off on this
tangent…
On Sep 3, 2013, at 9:43 AM, Alex Harui wrote:
> Are you asking me to not reply until you've copied users@?
>
> On 9/2/13 11:20 PM, "Harbs" wrote:
>
>> I'd like to pick up on this discussion over on the use
Are you asking me to not reply until you've copied users@?
On 9/2/13 11:20 PM, "Harbs" wrote:
>I'd like to pick up on this discussion over on the users list.
>
>Now with Adobe moving over to JS in their CS extensions, I'm going to be
>forced to move over quite a few extensions to js. (I'm hoping
I'd like to pick up on this discussion over on the users list.
Now with Adobe moving over to JS in their CS extensions, I'm going to be forced
to move over quite a few extensions to js. (I'm hoping that will be an
opportunity for me to get more involved in FlexJS…)
One of my (many) concerns is
