Re: Publishing royale to npm

On Tue, Nov 14, 2017 at 11:09 PM, Alex Harui wrote: > Royale will be using artifacts from royale-compiler, not flex-falcon. > > I'm not sure we've decided on how to package our releases. The Ant > scripts are currently set up for two artifacts (compiler and framework),

Re: Publishing royale to npm

Royale will be using artifacts from royale-compiler, not flex-falcon. I'm not sure we've decided on how to package our releases. The Ant scripts are currently set up for two artifacts (compiler and framework), Maven is set up for 1 or 3, depending how you count. I'm pretty sure we'll have to

Re: Publishing royale to npm

I'm in the middle of updating the npm scripts. Are we planning to continue to download flex-falcon from the current release? Or are we planning on pushing out a new release of falcon/royale-compiler? Thanks, Om On Mon, Nov 13, 2017 at 12:57 AM, Alex Harui wrote: >

Re: [royale-asjs] branch develop updated: Add ‘glue’ utility script to allow WASM to be loaded in HTML

+1 for this. As I said it will help me to adjust maven build if it go to separate branch. Thanks, Piotr On Tue, Nov 14, 2017, 23:44 Alex Harui wrote: > It is great to see progress on this front. > > Logistical question: We are hoping to cut a release of Royale

Re: [royale-asjs] branch develop updated: Add ‘glue’ utility script to allow WASM to be loaded in HTML

It is great to see progress on this front. Logistical question: We are hoping to cut a release of Royale "soon". Is this code intended to ship in that release? Are we ready to draw attention to the WebASM effort in the release? Otherwise, can this stuff be in a feature branch so we don't have

Re: About Semantic UI and our UI Set + look-and-feel effort

Hi Carlos, If it turns out you can create a default look for us without any SVG, that's fine with me. SVG-as-skins could always wait for some other day. I don't think potential users have said they must draw their visuals. So I leave it up to you to decide what to work on. If it turns out you

Re: [royale-asjs] branch develop updated: Add ‘glue’ utility script to allow WASM to be loaded in HTML

There are differences in scope, but I think most people like arrow functions mostly because of the syntactic sugar. > On Nov 15, 2017, at 12:02 AM, OmPrakash Muppirala > wrote: > > On Tue, Nov 14, 2017 at 1:49 PM, Harbs wrote: > >> Cool. >> >> I

Re: [royale-asjs] branch develop updated: Add ‘glue’ utility script to allow WASM to be loaded in HTML

On Tue, Nov 14, 2017 at 1:49 PM, Harbs wrote: > Cool. > > I have not been following WASM very closely. > > As an aside: > It would be really cool if we could make the compiler understand arrow > functions for ActionScript. > Hmm, the point of the arrow function in ES6 is

Re: [royale-asjs] branch develop updated: Add ‘glue’ utility script to allow WASM to be loaded in HTML

> > It would be really cool if we could make the compiler understand arrow > functions for ActionScript. > That would need to happen in the actual compiler (royale-compiler/compiler). Which is basically a black box to me. I do all my magic in the transpiler, and I barely even understand what's

Re: [royale-asjs] branch develop updated: Add ‘glue’ utility script to allow WASM to be loaded in HTML

Cool. I have not been following WASM very closely. As an aside: It would be really cool if we could make the compiler understand arrow functions for ActionScript. > On Nov 14, 2017, at 11:44 PM, Erik de Bruin wrote: > > Yes. WebAssembly only a month or so ago made it into

Re: [royale-asjs] branch develop updated: Add ‘glue’ utility script to allow WASM to be loaded in HTML

Yes. WebAssembly only a month or so ago made it into the bleeding edge versions of Safari and Edge, completing it's 'penetration' of the major browsers. ES6 was there "a long time ago", so basically if we're doing WASM, we're good on whatever JS or Web API we want to use ;-) EdB On Tue, Nov

Re: [royale-asjs] branch develop updated: Add ‘glue’ utility script to allow WASM to be loaded in HTML

I’m curious about the context of this script. Will all environments where this is being run understand ES6 arrow functions? > On Nov 14, 2017, at 5:54 PM, erikdebr...@apache.org wrote: > > This is an automated email from the ASF dual-hosted git repository. > > erikdebruin pushed a commit to

Re: About Semantic UI and our UI Set + look-and-feel effort

Hi Alex, 2017-11-14 18:26 GMT+01:00 Alex Harui : > Hi Carlos, > > You and others are definitely welcome to integrate SemanticUI like you did > for Material Design Lite. > Ok, but as I stated before, if I invest in integrate SemanticUI the proposal would be as I

Re: Ant Build Problem

The FlexUnit compile is trying to use the Ant tasks instead of directly calling the compiler, which is probably worth testing. You can see that it picks up the Ant tasks from If ROYALE_COMPILER_HOME is pointing somewhere unexpected, then you might be loading a really old

RE: Ant Build Problem

The failure is on the compilation of FlexUnitRoyaleApplication.mxml. The rest of royale-asjs seems to compile ok. One thing I noticed is that the compiler is invoked differently.

Re: [royale-asjs] branch develop updated: Add license

Just to avoid any misunderstanding: I was already working on a feature branch (feature/wast) for the compiler stuff, and the stuff I put in develop@royale-asjs doesn't touch any executable or build code. Also, I run all tests before committing anything to any branch of any project, just to make

Re: [royale-asjs] branch develop updated: Add license

Erik, Agree with Alex that you wouldn't worry about all build stuff if you will be on separate branch. I'm just asking, we didn't have any agreement to have separate branch for each feature, but note thing that not only Harbs has currently application which is using code from develop. We are

RE: Ant Build Problem

I updated compiler and typedefs as well. Will have a look tomorrow. From: Alex Harui Sent: Tuesday, November 14, 2017 6:25:55 PM To: dev@royale.apache.org Subject: Re: Ant Build Problem I haven't seen that. You are working with

Re: [royale-asjs] branch develop updated: Add license

I don't know about you, but when I'm trying something really new, I just want to commit it some place so I don't lose it if my computer blows up. Later, I might get to a point where I want to share it with others and have them help me. IMO, I wouldn't worry about Ant/Maven/CI until you have

Re: About Semantic UI and our UI Set + look-and-feel effort

Hi Carlos, You and others are definitely welcome to integrate SemanticUI like you did for Material Design Lite. Regarding a more sophisticated option, I first want to see if SVG for visuals is possible before we build a whole tool chain around it. So, IMO, you could just use your favorite

Re: [royale-asjs] branch develop updated: Add license

> > sooner or later. The functionality which you are doing is something big, > that's why I'm asking to have your work on branch. > I was already working on a branch. I made two commits to develop@royale-asjs, which were in a subdirectory and completely separate from the rest of the framework, so

Re: About Semantic UI and our UI Set + look-and-feel effort

Hi Alex, what you propose would be the more sophisticated option we can do. I could invest in that, but I need to work with you, Peter closely to complete something. I see more probable that I can design each component, at least for a first round, but I can't do the infrastructure we need to get

Re: About Semantic UI and our UI Set + look-and-feel effort

Maybe we need to pause for a minute to agree on the implementation goals related to our default theme. I was under the impression that an implementation goal was to create a component set where you could "draw" just about any visuals for the components. These other 3rd party themes (Material

Re: About Semantic UI and our UI Set + look-and-feel effort

Hi Peter, IMHO, dataProviders+itemRenderes in Royale List and Tablets is without doubt the way to go. Is some of the features that made Flex so successful, like RemoteObject or other "Flex" things, is what will make migration from flex more easy and what a flex developer expect to see in Royale.

Re: About Semantic UI and our UI Set + look-and-feel effort

Hi Peter, I mention it in my email at the end. We can talk with legal first, but in theory MIT license allows us to do whatever we want as is the most permissive open source license I know. But you're right, before pushing project barebones for this, we'll be talking with legal. Thanks! :)

Re: About Semantic UI and our UI Set + look-and-feel effort

haha, sometimes planets align Piotr! :) 2017-11-14 16:53 GMT+01:00 Piotr Zarzycki : > Carlos, > > Just quick from me. Today I have found exactly the same :D :) > > Piotr > > 2017-11-14 16:25 GMT+01:00 Yishay Weiss : > > > One thing that I found

Re: About Semantic UI and our UI Set + look-and-feel effort

Hi Yishay, that's the main problem I see in MDL too. And that it was not our own foundation. I said that MDL was only something quick for people coming that see Royale can do good looking UIs quickly. But the problem was that we can't plan anything "cross" to all Royale since Material has its own

Re: [royale-asjs] branch develop updated: Add license

And as you can see something went wrong and I know about that from the very beginning. :) [1] https://builds.apache.org/job/Royale%20Pipeline/job/feature%252Fwast/2/console Thanks, Piotr 2017-11-14 17:27 GMT+01:00 Piotr Zarzycki : > Sweet! Now whenever you push

Re: About Semantic UI and our UI Set + look-and-feel effort

For things like lists and tables, we have our dataProviders and itemRenderer factories. Could probably be more streamlined to produce list and table elements for the itemRenderers. Being able to make a quick in-line list with some text and buttons ought to be easy and not require a dataProvider

Re: Ant Build Problem

I haven't seen that. You are working with relatively new test code, IIRC. Could be you are using very old compiler? HTH, -Alex On 11/14/17, 3:26 AM, "Yishay Weiss" wrote: >[mxmlc] >C:\dev\flexjs\royale-asjs\frameworks\projects\Core\src\test\royale\flexUni

Re: About Semantic UI and our UI Set + look-and-feel effort

I did a quick look. Seems pretty cool and definitely useful. Plus it gives us direction. But please, please, please, figure out licensing before going a step further. This is what I found: https://semantic-ui.mit-license.org ‹peter On 11/14/17, 10:10 AM, "carlos.rov...@gmail.com on behalf of

Re: [royale-asjs] branch develop updated: Add license

And I have created and published the branches you requested :-) Thanks, EdB On Tue, Nov 14, 2017 at 5:16 PM, Erik de Bruin wrote: > Piotr, > > Can you explain what Maven has to do with anything? I'm pretty sure this > will not work with Maven... > > Thanks, > > EdB > > >

Re: [royale-asjs] branch develop updated: Add license

Piotr, Can you explain what Maven has to do with anything? I'm pretty sure this will not work with Maven... Thanks, EdB On Tue, Nov 14, 2017 at 5:11 PM, Piotr Zarzycki wrote: > Erik, > > Could you create branch in repository typedefs and asjs called feature/wast

Re: [royale-asjs] branch develop updated: Add license

Erik, Could you create branch in repository typedefs and asjs called feature/wast - Once we have those three branches Maven will pickup it automatically. It will be easier to me follow your changes there. Thanks, Piotr 2017-11-14 16:57 GMT+01:00 : > This is an

Re: About Semantic UI and our UI Set + look-and-feel effort

Carlos, Just quick from me. Today I have found exactly the same :D :) Piotr 2017-11-14 16:25 GMT+01:00 Yishay Weiss : > One thing that I found problematic with the mdl implementation was that > there was a feeling of thin wrappers on a blackbox. Whatever default theme >

RE: About Semantic UI and our UI Set + look-and-feel effort

One thing that I found problematic with the mdl implementation was that there was a feeling of thin wrappers on a blackbox. Whatever default theme we choose, I think we should implement it so the core functionality is easily understandable to an AS3 programmer with some CSS knowledge. That

About Semantic UI and our UI Set + look-and-feel effort

Hi, I was looking at Semantic UI and it has most of the things we want to get with our UI set + Look and feel effort. I need to investigate it more, but maybe we don't need to reinvent the wheel here. Supposing licenses are ok, we could base the new UI Set to be based on Semantic UI or make our

Ant Build Problem

[mxmlc] C:\dev\flexjs\royale-asjs\frameworks\projects\Core\src\test\royale\flexUnitTests\KeyboardEventConverterTest. as(23): col: 5 Error: Can not resolve config constant: 'SWF' [mxmlc] [mxmlc] COMPILE::SWF [mxmlc] ^ [mxmlc] Is anyone else getting it?

Re: [royale-asjs] branch develop updated: Fixes #87 box-sizing was only being set for the view and not the application

I changed the box model for “Application” in addition to “royale”. This makes sure that popups such as Alert which might be attached to the application outside the view, use border-box instead of content-box. I think this is correct, but I wanted to make sure that others agree and I did not