Re: Nightly Builds Available

OK, I merged packaging to develop. I think I see some consensus around the rename, so I will start on that tomorrow in feature branches. -Alex On 10/2/17, 12:29 AM, "Piotr Zarzycki" wrote: >Alex, > >I think we should have separate branch for renaming. Packaging

Re: [DISCUSS] project vs. product name vs artifact names

Hi, I like Alex's idea and I don't see any problem if we will have clear information on our website what is for what is not for. I actually was waiting for some package which is small and free from Flash Player - and here we go! I have to admit since I did start using FlexJS I haven't touch SWF

Re: [Discussion] About validation

I have very few work days until the 15th. I doubt I’m going to work more on validation until then. If someone else wants to do work on it before that, it’s fine with me… > On Oct 2, 2017, at 8:46 PM, Alex Harui wrote: > > I didn't look at the Validation commit too

Re: [DISCUSS] project vs. product name vs artifact names

> > So our mantra should be "keep it simple" to be able to make people outside > our world have the opportunity to be attracted by our tech. > Agreed on the "simple." But it may be better to have a few products that do what they advertise to do instead of one monolithic product that I then need

Re: Github wikis

Hi, I don't see to much reason for having royale-website wiki - as long as we decide where actually documentation goes. Another repo for examples, does examples which we already have ? I believe that is good that we are shipping examples along with our framework repo - How we will ship that ?

Re: Github wikis

I think I learned that Github Pages is not per-repo, it is one per Apache Project. It is a bit easier to have one repo per release product. Combining repos for a release is a bit of extra work. There should be examples in the IDE-friendly artifact. IMO, TourJS would have its own release

Re: Possible license issue with new web site

My $0.02: Let’s see what you have and then we can discuss what is and isn’t a problem. It’s clearly not an issue for Apache to use commercial software (i.e. JIRA etc.) Are you using a commercial theme for your design? If yes, who paid for it and who is it licensed to? Will we need to commit it

Re: [DISCUSS] project vs. product name vs artifact names

We must think in users as people doesn't know anythings about us. As well people writing articles about us, will want to check quickly what we do, and we need to be simple and fast. So for me, if I use for example NPM, the last proposal is the correct one: npm install royale -g If people that

Re: Struggling with resource files

The Flash runtime doesn't know anything about resources. In regular Flex, and Resource Module is a SWF full of compiled Resource Bundles which are classes that wrap the resource data. IMO, that's too heavy for strings and I believe there are many apps where the only things that change per locale

Re: License issue for back port of AMF code

Hi Justin, It seems to me like Surrey agreed to the request which was explicit that it included relicensing to the Apache License. If you feel that another more explicit response is required then please go ahead and make that effort. Regards, Dave > On Oct 1, 2017, at 9:29 PM, Justin Mclean

Re: [DISCUSS] project vs. product name vs artifact names

I changed the subject so sorry if this appears like a new thread. Let's be a bit more explicit and see if that helps. After getting the packaging to start to work, I've changed my thoughts a bit. I actually think I agree with Carlos and Erik. I am proposing that we post two different

Re: Possible license issue with new web site

Hi Justin, good questions. I think take a comercial product to build a site for marketing purposes is different to take some code to be incorporated to our project codebase, or make it work with that code. In this case, is only a "face" of our real project and we are not planning to change it, or

Re: Nightly Builds Available

Hah! Harbs greate idea for creating issue. If you could do that. Thanks, Piotr 2017-10-02 9:32 GMT+02:00 Harbs : > I was in middle of writing the same thing. :) > > I think we should create an issue with what needs to be done for the > rename. The obvious is a

Re: Struggling with resource files

We’ve had some discussion about having the compiler inline string constants at compile time (to make code minimization more efficient). I wonder if that might be usable to inline the values into ResourceBundle names (and maybe other metadata) as well. Harbs > On Oct 2, 2017, at 9:35 AM,

Re: Struggling with resource files

See the Adobe docs: [1][2] I think the functionality you are looking forward is supported by the compiler. The compiler already has a set of options that dictate what bundles are "inline" in the app and I think they can be re-used to output different things. [ResourceBundle] metadata tells the

RE: Struggling with resource files

>From our point of view (app development), the Flex way Alex describes is >simple and easy to grab. The only "complaint" is that you cannot alias the resource file to a var/const inside the metatag which would be more convenient than declaring a separate constant. I believe that most people