royale-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Harbs <>
Subject Re: Struggling with resource files
Date Mon, 02 Oct 2017 06:34:00 GMT
I should probably spend some time to learn how resource bundles worked in Flex… ;-)

Metadata seems like a good solution, but it seems to me like there needs to be two sets of
metadata tags. Some comments and questions I have:

1. We’d need metadata tags which would just inline the resource into the compiled code for
cases where a full-blown ResourceManager is overkill.
2. We’d need the [ResourceBundle] tag for compiling downloadable resource bundles. What
would that look like in Javascript? A JS file which evaluates to the resources? A JSON file?
Would default resources get auto-included in the main JS?

BTW, if there’s something I can do to help you with the packaging branch, please let me


> On Oct 2, 2017, at 2:28 AM, Alex Harui <> wrote:
> On 10/1/17, 7:31 AM, "Harbs" <> wrote:
>> I’d really like for the compiler to include resources as strings, but I’m
>> not sure what the best way to declare it is.
>> How can we declare a reference to the resource and have the compiler
>> include it?
> Well, that depends...
> The [ResourceBundle] metadata and the compiler's -locale option seemed to
> make people happy.  I don't remember any complaints about it, my only
> issue was that it didn't seem to be efficient for String-only resources.
> [ResourceBundle] allows the strings to be managed in separate .properties
> files that are packaged with a SWC.  That's probably important because you
> probably don't want to have to list out every component's resources as
> beads in your app.  It probably needs to be driven automatically by
> metadata.
> So, if we decide to stick with it, the challenge will be to teach the
> compiler to do something different with the resource properties.
> Thoughts?
> -Alex

View raw message