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.187 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "dev@flex.apache.org" <dev@flex.apache.org>,
        "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Date: Mon, 21 Jan 2013 06:52:34 -0800
Subject: Re: [FalconJx] Compiling i18n properties / ResourceBundles
Thread-Topic: [FalconJx] Compiling i18n properties / ResourceBundles
Thread-Index: Ac33rlElwaZY48wLQgKHeaXh4tD0TAAOKD37
Message-ID: <CD229632.4BF96%aharui@adobe.com>
In-Reply-To: 
 <CAD8jDGL6VTysN_zYV-5L-oottxFJUOLBrkhRs6-ymJrOtOAGUw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-Entourage/13.13.0.120411
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


On 1/21/13 12:01 AM, "Frank Wienberg" <frank@jangaroo.net> wrote:

> Besides ActionScript and MXML, there is a third source file format for
> which mxmlc can produce code: properties files.
> Thus, for FalconJx, like for MXML, we have to decide which way to go: eit=
her
>=20
>    1. let Falcon generate the temporary ActionScript class and compile th=
at
>    to JavaScript, or
>    2. produce JavaScript code or maybe even data (JSON?) directly from th=
e
>    properties file.
Sorry, I didn't read the whole email, but I believe there is a 3rd option
(and more)
3. Don't reduce string-only properties files to the current class structure=
,
just take them in as a string and parse them in the framework.  How often d=
o
folks actually use binary resources?

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