RE: Source path in framework SWCs

Let’s hope FDT provides Royale support. We need a presence in Eclipse. New versions of Eclipse support generic editors that support language servers so maybe Josh’s work can be reused… From: Alex Harui Sent: Tuesday, November 7, 2017

Re: [Royale-ASJS] flexTasks

Sync all 3 repos, start with royale-compiler, then royale-typedefs, then royale-asjs. I'd recommend running "ant wipe-all" in royale-compiler before running just "ant" (which now builds everything in royale-compiler). And in royale-asjs, run "ant super-clean" before running "ant". HTH, -Alex

Re: [Royale-ASJS] flexTasks

I'm not seeing this in the latest builds, now that things are synced up. We are keeping "flexTasks" to make it easier for folks migrating. Not sure if new users who aren't migrating are going to be using Ant anyway. -Alex On 11/7/17, 4:42 PM, "Alex Harui" wrote:

Re: [Royale-ASJS] flexTasks

I've noticed that too, but the build seems to work for me. I will look into it. -Alex On 11/7/17, 3:58 PM, "Peter Ent" wrote: >I sent this earlier but I haven’t seen it in my feed. Apologies if this >is a duplicate. > >I sync'd the repo (develop branch) and rebuilt

Re: RE: Source path in framework SWCs

The VSCode extension attempts to use the source path from the SWC, if possible. Basically, it checks the path for "/frameworks/projects/", and then, it tries to swap in the local path to the SDK on your computer. - Josh On 2017-11-07 13:12, "Idylog - Nicolas Granon" wrote:

RE: Resources (I18N, globalization, localization)

I forgot to say (it was probably obvious, but...) that we rely *heavily* on locale for dates and number formatting. For dates, it means not only the typical MM, DD, order, but also the separator between them, and the "text form" (short or long) for days of week, and/or months. For

RE: Source path in framework SWCs

I am not an expert there, but I see in the SWCs that ship from Adobe that the source path (to the /projects/ folder) is in fact coded "inside" the SWCs. When I open the SWCs from the Royale binaries, the source path points to some absolute Jenkins source folder that is not part of the

Re: [royale-compiler] branch wast created (now e336021)

I know Erik, that's why I'm trying to keep my hands on that. Thanks for moving it! :) Piotr 2017-11-07 19:43 GMT+01:00 Erik de Bruin : > I moved it. > > I know nothing about Maven, and I won't be investing time in writing code > to support it: that'll have to be another

Re: Apache Royale website legal approval

Yay! So excited about being able to move on with this! :-D Harbs > On Nov 7, 2017, at 8:45 PM, Carlos Rovira wrote: > > Hi, > > as Chris marked the ticket solved (although it will remain open until > Friday), I just buyed the license now to avoid a price increase in

Re: Apache Royale website legal approval

btw, to share the envato credentials to the "apacheroyale" account, I think it's ok to share it in private list 2017-11-07 19:45 GMT+01:00 Carlos Rovira : > Hi, > > as Chris marked the ticket solved (although it will remain open until > Friday), I just buyed the license

Re: [royale-compiler] branch wast created (now e336021)

I moved it. I know nothing about Maven, and I won't be investing time in writing code to support it: that'll have to be another volunteer's challenge ;-) EdB On Tue, Nov 7, 2017 at 5:24 PM, Piotr Zarzycki wrote: > Hi Erik, > > Could you please create that branch

Re: source-map compiler argument : path to source

The .js.map extension is the correct behavior. The name of a source map file is based on extension of the output file rather then the input file. Both .as and .mxml files will produce .js output, so the source map's extension should be .js.map for both. Every tool that I've seen produce source

Re: Apache Royale website legal approval

Right Harbs, I think what Shane demands is ok, I expect they could give us that concrete wording for us to add to the footer. Thanks 2017-11-07 18:26 GMT+01:00 Harbs : > It looks that way, but I’d wait a bit longer to give some more folks a > chance to weigh in. > >

Re: Test Beads (was Re: Unit Tests et. al.)

> I guess we are not understanding each other. Probably not. The best way to discuss this is likely a POC. > If the testing language is > AS or JS, test authors have to know how to deal with the runtime > differences. It depends on the tests. If the code is platform agnostic, the tests should

Re: Test Beads (was Re: Unit Tests et. al.)

I guess we are not understanding each other. If the testing language is AS or JS, test authors have to know how to deal with the runtime differences. That's why Mustella uses MXML. Automated test code generation could also abstract those differences from the test authors. If you want to build

Re: Resources (I18N, globalization, localization)

Thanks Nicolas. So some questions for you (and other users) 1) does your Flex app currently use the "fall-through" where not every locale has every key? 2) does your Flex app use @resource directive in MXML? Thanks, -Alex On 11/7/17, 9:29 AM, "Idylog - Nicolas Granon"

Re: Currency formatter instanciation issue (was RE: ApplicationComplete event not firing)

Unfortunately, FB does not call our code in a useful fashion during a "clean". That's something that may also be a limitation of FB. We'll see if I find time to dig into FB more and find a workaround. The workaround may be to always clean the bin folder when running in FB. -Alex On 11/7/17,

Re: Source path in framework SWCs

AFAIK, there is no way to link the source-path "out-of-the-box". It is a limitation of Flash Builder. We might provide a script that injects the links into a project's files. That's about the best we can do, short of monkey-patching FB. Long-term, the newer IDEs (VSCode, Moonshine) and older

Re: Test Beads (was Re: Unit Tests et. al.)

Right. I’m proposing a totally different architecture. In the architecture I’m proposing, the runner is a passive observer. The tests would be run by *the beads themselves* and *push* the results out to the runner. The runner would have a count of the number of tests that are supposed to be

RE: Resources (I18N, globalization, localization)

Great ! That is one the features we cannot afford to miss... Nicolas Granon > -Message d'origine- > De : Alex Harui [mailto:aha...@adobe.com.INVALID] > Envoyé : mardi 7 novembre 2017 18:24 > À : dev@royale.apache.org > Objet : Resources (I18N, globalization, localization) > > Hi, >

Re: Apache Royale website legal approval

It looks that way, but I’d wait a bit longer to give some more folks a chance to weigh in. Shane wants very clear wording and a page that explains the licensing. Makes sense to me. Harbs > On Nov 7, 2017, at 7:00 PM, Carlos Rovira wrote: > > Hi, > > just let you

Resources (I18N, globalization, localization)

Hi, I just pushed a simple way of handling different locales in a Royale app. I purposefully did not call it ResourceManager for now since I don't think it will be 100% compatible. I just wanted to get something out there to get a discussion going. It looks like there is PAYG features for what

Re: Working on UI Controls styling

Hi Harbs, That looks like good starting point, but this last approach where we for example generate UIDs for every component. This UID at the end will have to end up as an id in HTML or compiler will have to bind together css with that uid. The first approach where you have created couple of css

Re: [royale-compiler] branch wast created (now e336021)

Hi Erik, Could you please create that branch under "feature/" folder - "feature/wast" - Thanks to that Maven build automatically pickup all your changes if we create branches for other repository as well. Thanks, Piotr 2017-11-07 15:13 GMT+01:00 : > This is an

RE: Working on UI Controls styling

Are we talking about styling, theming or skinning ? As application developers, we are mainly interested in "styling", based on an available theme. Usually, it is a minor task. Most of the apps follow the chosen theme and styles affect mostly font size/weight, borders width/color, alphas ... We

Re: Working on UI Controls styling

Some food for thought: I created a custom component for “buttons” which allow simple skinning using image files. It works like this: https://paste.apache.org/tc8f Specifying different states can be done using the following css: .bug { background-image:

Re: Renaming Next Steps

+1 2017-11-07 9:57 GMT+01:00 Erik de Bruin : > Go for it. > > EdB > > > > On Tue, Nov 7, 2017 at 8:12 AM, Harbs wrote: > > > +1 > > > > > On Nov 7, 2017, at 7:25 AM, Alex Harui > wrote: > > > > > > Hi, > > > > > > It looks

Re: Test Beads (was Re: Unit Tests et. al.)

Comments inline. > Each Mixin brings in one class, but that class can drag in tons of stuff. > The key question for our users is how they want to determine what gets > tested. From prior Adobe Flex users, they didn't want to add testing > overhead to every MXML component, only certain ones, and