Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

The release artifacts are a combination of all 3 repos. When you uncompress an artifact, there is a README there that is different from the README.md files we put in the root of each repo. The artifact README comes from the royale-asjs repo in the releasemgr/README file. -Alex On 2/8/18, 11:27

Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

Is it that section ? https://github.com/apache/royale-asjs#additional-prerequisites-for-swf-output 2018-02-09 8:21 GMT+01:00 Alex Harui : > > > On 2/8/18, 10:55 PM, "Piotr Zarzycki" wrote: > > >Hi Alex, > > > >One question to this release.

Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

On 2/8/18, 10:55 PM, "Piotr Zarzycki" wrote: >Hi Alex, > >One question to this release. Did you document anywhere that if someone >download Royale SWF, JS have to on his own download the rest of >dependencies ? It is in the top-level README. -Alex > >Thanks, >Piotr

Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

Hi Alex, One question to this release. Did you document anywhere that if someone download Royale SWF, JS have to on his own download the rest of dependencies ? Thanks, Piotr 2018-02-08 20:58 GMT+01:00 Alex Harui : > This is the discussion thread. > > Thanks, > Alex

Re: Royale Examples Blog proposal to all the team

Great idea, Carlos. Here is one I volunteer to write about: Getting started with Royale on npm I will write this over the weekend and share it here. We can post after Andrew (and others) makes a sweep over it :-) Thanks, Om On Thu, Feb 8, 2018 at 3:25 AM, Andrew Wetmore

Re: JSON Objects renaming (was Re: ASDoc, Routing, Releases)

Sent from my iPhone > On Feb 8, 2018, at 2:10 PM, Alex Harui wrote: > > We can "leave it as it was" by making SIMPLE_OPTIMIZATIONS the default. > The difference between Flex and Royale is that Royale currently crunches > your code through the Google Closure Compiler

Re: JSON Objects renaming (was Re: ASDoc, Routing, Releases)

We can "leave it as it was" by making SIMPLE_OPTIMIZATIONS the default. The difference between Flex and Royale is that Royale currently crunches your code through the Google Closure Compiler with ADVANCED_OPTIMIZATIONS and that messes up how you use plain objects. IMO, there is enough to gain

Re: JSON Objects renaming (was Re: ASDoc, Routing, Releases)

but why to complicate this so much? I think we always had in Flex/Flash the opportunity to make this without any additional config. Why not left it as it always was? thanks 2018-02-08 19:48 GMT+01:00 Alex Harui : > I'm not disagreeing. I think the question is whether

Re: [VOTE] Release Apache Royale 0.9.1 RC1

+1 Package https://dist.apache.org/repos/dist/dev/royale/0.9.1/rc1/apache-royale-0.9.1 -src.tar.gz Java 1.8 OS: Mac OS X x86_64 10.12.5 Source kit signatures match: y Source kit builds: y README is ok: y RELEASE_NOTES is ok: y NOTICE is ok: y LICENSE is ok: y No unapproved licenses or archives: y

[VOTE] Release Apache Royale 0.9.1 RC1

Hi, This is vote for the 0.9.1 release of Apache Royale. The release candidate can be found here; https://dist.apache.org/repos/dist/dev/royale/0.9.1/rc1/ Before voting please review the section,'What are the ASF requirements on approving a release?', at:

Re: What is x and y? What is width and height?

In most cases we do output the most basic code. But let's look at one scenario I expect to run into more than once, which is placing a popup somewhere. Like I said, in most of our code, we rarely read back x and y. I don't even think we read x and y in an absolute positioning container. But I

Re: JSON Objects renaming (was Re: ASDoc, Routing, Releases)

I'm not disagreeing. I think the question is whether we need yet another compiler option to generate bracket notation for objects or just ask folks to use SIMPLE_OPTIMIZATIONS. And whether we switch to SIMPLE_OPTIMIZATIONS by default. I can think of lots of other things to work on besides this

Re: What is x and y? What is width and height?

Hi Alex, in this case it's hard to prove this will be a problem. Maybe the apps will suffer it very slightly for most people to perceive it, but that's not the problem. The problem is our solution will have additional calculations *always* that other frameworks doesn't have. And that's goes

Re: Canvas

IMO, the Express set should have a Canvas component that bundles those beads. I challenge someone besides Peter and me to create it! Thanks, -Alex On 2/8/18, 3:13 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: >So

Re: What is x and y? What is width and height?

I would much rather we decide on an implementation. It makes documentation much easier. I'm all for options, but making fundamental things like geometry have options seems like it would make Royale seem more complex. I would not worry about performance until it actually proves to be a problem.

Re: JSON Objects renaming (was Re: ASDoc, Routing, Releases)

Nothing frustrated me more about Royale/FlexJS than the fact that I couldn't use untyped objects without bracket notation. It's a very bad user experience when trying to consume JSON, or even when choosing to create my own object literals. While it's a good best practice to create value

Re: What is x and y? What is width and height?

Seems more reasonable, since its optional and people wanting it can include... 2018-02-08 14:04 GMT+01:00 Piotr Zarzycki : > I personally prefer having Bead for such things. > > 2018-02-08 14:01 GMT+01:00 Yishay Weiss : > > > I agree, that’s why

Re: What is x and y? What is width and height?

I personally prefer having Bead for such things. 2018-02-08 14:01 GMT+01:00 Yishay Weiss : > I agree, that’s why I’m proposing to have a bead do the calculation. If > you care about integrity with actual position on the screen and are willing > to sacrifice some

RE: What is x and y? What is width and height?

I agree, that’s why I’m proposing to have a bead do the calculation. If you care about integrity with actual position on the screen and are willing to sacrifice some performance use ScreenPositionCalculatorBead, otherwise use the default which is more performance oriented. Another option is to

Re: Canvas

Absolutely. I am also going to include this in the help docs list of features that you do one way in Flex and slightly differently in Royale. On Thu, Feb 8, 2018 at 6:57 AM, Carlos Rovira wrote: > (moving to dev list) > > Hi I think this is a good tip that we can add to

Re: Canvas

(moving to dev list) Hi I think this is a good tip that we can add to our Royale Blog in the "Examples" category. And respect the user (ni this case Peter) as the poster. What do you think? 2018-02-06 15:06 GMT+01:00 Peter Ent : > Hi, > > Thanks for looking into Apache Royale!

Re: What is x and y? What is width and height?

I don't have right now a proposal for this, but it seems to me that introduce calculations that affects performance will be a bad idea. That will make us not elegible for some escenarios/people. On e of the things I like from Royale is that in the end we are outputting the most easy code while we