Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Received-SPF: pass (athena.apache.org: domain of aharui@adobe.com designates
 64.18.1.27 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "dev@flex.apache.org" <dev@flex.apache.org>
Date: Mon, 11 Mar 2013 08:37:48 -0700
Subject: Re: [FlexJS] data structure specs
Thread-Topic: [FlexJS] data structure specs
Thread-Index: Ac4ebQhXs+5OkipgQT67ulaXgLyOUwAAVmsk
Message-ID: <CD63485C.4EDA8%aharui@adobe.com>
In-Reply-To: 
 <CAJs+wW3Xm60qWX41K3BT8dWpjS49OZ8dOm6Wk1_iYHFkLA_VvQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-Entourage/13.15.0.121009
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


On 3/11/13 8:27 AM, "Erik de Bruin" <erik@ixsoftware.nl> wrote:

> The last entry for each descriptor is a 'null' and is supposed to be
> for "children", but as all child nodes in FlexJS seem to be
> implemented as 'beads', isn't the children entry obsolete?
No, there are certainly children or will be when we have containers.
>=20
> There is some inconsistency with regard to the final 3 (or 4, counting
> 'children') entries. The description on the is that they are for
> styles, effects and events (and children), but the implementation in
> FalconJS outputs only 2... I assume these two are 'styles' and
> 'events' (in that order) and that 'effects' is obsolete?
It should be properties and events, but I think I'm sticking in 0's for
styles and effects.
>=20
> That's the ones that caught my eye. As I'm "almost" ready to do a full
> one on one comparison between the output of FalconJS and FalconJx,
> maybe more will pop up.
>=20
> EdB
>=20
>=20
>=20
> On Mon, Mar 11, 2013 at 4:16 PM, Alex Harui <aharui@adobe.com> wrote:
>>=20
>>=20
>>=20
>> On 3/11/13 4:18 AM, "Erik de Bruin" <erik@ixsoftware.nl> wrote:
>>=20
>>> Alex,
>>>=20
>>> Could you please take a look at:
>>>=20
>>> https://cwiki.apache.org/confluence/display/FLEX/MXML+Data+Spec
>>>=20
>>> and check if that spec is still up to date? I see some differences
>>> between the spec and the current FlexJS output and I'm wondering which
>>> one is leading...
>>>=20
>> What difference are you seeing?  BTW, the only thing that probably shoul=
dn't
>> change is the fact that it is an array of stuff.  The format of the stuf=
f
>> can change if it needs to.  Also note that you can look at what
>> Falcon/FalconJS is currently doing since it actually works (at least, we=
ll
>> enough for the prototype).
>>=20
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>=20
>=20
>=20
>=20
> --
> Ix Multimedia Software
>=20
> Jan Luykenstraat 27
> 3521 VB Utrecht
>=20
> T. 06-51952295
> I. www.ixsoftware.nl

--=20
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui