Re: [DRAFT] [ANNOUNCE] Apache Royale 0.9.0 Released

I have published -> https://github.com/apache/royale-asjs/releases/tag/apache-royale-0.9.0 2018-01-25 7:18 GMT+01:00 Piotr Zarzycki : > Alex, > > We can edit text later, that is not a problem. > > Piotr > > 2018-01-25 0:35 GMT+01:00 OmPrakash Muppirala

Re: [DRAFT] [ANNOUNCE] Apache Royale 0.9.0 Released

Alex, We can edit text later, that is not a problem. Piotr 2018-01-25 0:35 GMT+01:00 OmPrakash Muppirala : > I think it is perfectly fine to announce without npm support. We can add > it in our next release. > > Thanks, > Om > > On Wed, Jan 24, 2018 at 3:31 PM, Alex

Re: Migrating existing FlexJS documentation to Royale

OK, got jekyll working locally. I followed these instructions: https://www.phusionpassenger.com/library/walkthroughs/deploy/ruby/ownserver /standalone/oss/install_language_runtime.html One of the steps was to install bundler. That might be why you got the .bundle error. You will also need to

Re: Updating 2015 FlexJS presentation

Hi, I also have a couple of Royale examples on GitHub that might be useful. [1][2] They are not complex applications but they are a little more that a basic hello world app. You can see them working here. [3][4] For the Quiz (I just put up today) I may of made mistakes and it likely some

Re: [DRAFT] [ANNOUNCE] Apache Royale 0.9.0 Released

I think it is perfectly fine to announce without npm support. We can add it in our next release. Thanks, Om On Wed, Jan 24, 2018 at 3:31 PM, Alex Harui wrote: > If we can edit the text later, then IMO, go ahead and publish. > > If not, we might want to wait to hear

Re: Updating 2015 FlexJS presentation

On Wed, Jan 24, 2018 at 2:15 PM, Andrew Wetmore wrote: > Thank you, Om. > > Quick question: the slides refer to several FlexJS examples. Are they still > running? Will they eventually migrate to Royale versions? > All the examples continue to work with Apache Royale. They

Re: [DRAFT] [ANNOUNCE] Apache Royale 0.9.0 Released

If we can edit the text later, then IMO, go ahead and publish. If not, we might want to wait to hear from more folks. -Alex On 1/24/18, 3:20 PM, "Piotr Zarzycki" wrote: >I have created release on GitHub - It's unpublished [1] - Do we want to >add >something more

Re: Directory and File naming conventions

The .md files get built by Jekyll on our CI server. The results end up here: http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/RoyaleDocs_Stagin g/lastSuccessfulBuild/artifact/_site/ HTH, -Alex On 1/24/18, 2:21 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"

Re: Proposed table of contents for Royale help documentation

MIT is fine, as is BSD. But again, if the theme has many parts, it may result in the PMC spending time researching each of the parts. Just because the theme author claims MIT for his work, he might have used third-party works under other licenses that aren't as compatible with the Apache

Re: Cannot install royale-swf from npm

On Jan 24, 2018 2:10 PM, "Carlos Rovira" wrote: Hi, please as NPM is ready, make a new thread a resume all important info about how many npm packages we have, urls, instructions and all that is needed so I can add it to the website. Thanks Will do. Thanks, Om

Re: [DRAFT] [ANNOUNCE] Apache Royale 0.9.0 Released

I have created release on GitHub - It's unpublished [1] - Do we want to add something more there ? [1] https://github.com/apache/royale-asjs/releases/tag/untagged-3e7dc9305c4ad1eaa804 Thanks, Piotr 2018-01-24 23:06 GMT+01:00 Carlos Rovira : > Hi thanks Alex and Andrew,

Re: Migrating existing FlexJS documentation to Royale

Thanks Alex, I can see it working online :) I'm trying to test it localy but don't know how to do it. In order to make the html/css looks good, I need to work localy, please let me know how yo do it I installed already ruby, jekyll, etc... and tried to run "bundle exec jekyll serve" but we don't

Re: Updating 2015 FlexJS presentation

Thank you, Justin! We should have whenever we ca turn out illustrated talks for the too-busy-to-read crowd. It makes a huge difference in building project credibility. On Wed, Jan 24, 2018 at 6:22 PM, Justin Mclean wrote: > Hi, > > Was it recorded anywhere? I often

Re: Directory and File naming conventions

Hi, I see you work in develop thought GitHub with .md files. I can see as well .css with website fonts. But I don't know how to see the generated site. Can someone explain me how to see the final html content resulting from apply the css to the markdown files? Thanks 2018-01-24 22:13 GMT+01:00

Re: Updating 2015 FlexJS presentation

Hi, Was it recorded anywhere? I often use autosub [1] and Aegisub [2] to generate captions from talks. The talks at the FlexJS summit were recorded and might be useful [3][4] Justin 1. https://github.com/agermanidis/autosub 2. http://www.aegisub.org 3. https://us.apacheflexjs.org 4.

Re: Updating 2015 FlexJS presentation

Thank you, Om. Quick question: the slides refer to several FlexJS examples. Are they still running? Will they eventually migrate to Royale versions? I am tempted to make a first migration of this slide deck with the substance but without the links to the examples. Then, when we have examples

Re: Cannot install royale-swf from npm

Hi, please as NPM is ready, make a new thread a resume all important info about how many npm packages we have, urls, instructions and all that is needed so I can add it to the website. Thanks 2018-01-24 22:51 GMT+01:00 OmPrakash Muppirala : > On Wed, Jan 24, 2018 at 1:15

Re: [DRAFT] [ANNOUNCE] Apache Royale 0.9.0 Released

Hi thanks Alex and Andrew, right now we are having such moderate impact on internet. For example in twitter we have 135 followers, in facebook 40. We have the accounts open about 15 days like the website. So we can make huge noise right now. Just letting people know we release our first release

Re: Updating 2015 FlexJS presentation

Andrew, Please feel free to take this presentation and modify it. I have made the original ppt file available here: https://www.amazon.com/clouddrive/share/FPveqBSWJ5PiXXYkbSslIC36LLVgMYsHg8UUNHEV2c I don't have a presentation script (I just winged it :-D) But I would guess that by the time

Re: Proposed table of contents for Royale help documentation

Hi Alex, right, I'm looking for something that is ALv2. Unfortunately almost all docs themes are MIT license. Is MIT right for us? 2018-01-24 18:14 GMT+01:00 Alex Harui : > Hi Carlos, > > Right now, the master branch is set up to use the Cayman theme. When I > took a

Re: Cannot install royale-swf from npm

On Wed, Jan 24, 2018 at 1:15 PM, Alex Harui wrote: > OK, but I believe the royale-swf package still won't run. Or are you > going to fix that before publishing? > Hmm, fixing it will require a new release, right? If that is the case, I would rather push what we have

Re: Different results for compilation Error in JS and SWF compilation

Ok now I understand! I will look into that :) 2018-01-24 21:40 GMT+01:00 Alex Harui : > I'm saying that if you want JSRoyale to have the same output as the SWF > target, I would look at the compiler source in those files and see if they > are doing something different.

Re: Cannot install royale-swf from npm

OK, but I believe the royale-swf package still won't run. Or are you going to fix that before publishing? Please use NPM 5.6.0 so we can use whatever steps you end up using in the RM script. Thanks, -Alex On 1/24/18, 1:08 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"

Re: Directory and File naming conventions

OK, I'm done playing in the Welcome folder. The third-tier TOC seems to be working. I am moving on to the CreateAnApplication folder. -Alex On 1/24/18, 12:10 PM, "Andrew Wetmore" wrote: >I should have added that I will go edit out the hyphens in the front >matter. > >On

Re: Cannot install royale-swf from npm

I'm going to republish both under the apache royale organization. Please hold off on making any changes till then. Thanks, Om On Jan 24, 2018 12:31 PM, "Alex Harui" wrote: > Interesting. There might be different rules for Apache Royale since our > repos are under

Re: Different results for compilation Error in JS and SWF compilation

I'm saying that if you want JSRoyale to have the same output as the SWF target, I would look at the compiler source in those files and see if they are doing something different. I could go fix it myself, but I am trying to encourage other committers to get more familiar with the compiler source.

Re: Different results for compilation Error in JS and SWF compilation

Not sure what do you mean ? That's how we use it I think so. 2018-01-24 21:28 GMT+01:00 Alex Harui : > Interesting. Hadn't noticed that. I guess you could compare the output > logic in the compilers. MXMLC.java should be used for SWF compiles and > MXMLJSC.java for

Re: Cannot install royale-swf from npm

Interesting. There might be different rules for Apache Royale since our repos are under the Apache organization, but if you can get it to work, I think that would be helpful. -Alex On 1/24/18, 12:21 PM, "Piotr Zarzycki" wrote: >Ahh Yes! > >You can do nice release on

Re: Cannot install royale-swf from npm

Ahh Yes! You can do nice release on the GH. We are doing such based on TAG. I'm putting in the description links to the release [1] [1] https://github.com/prominic/Moonshine-IDE/releases 2018-01-24 20:58 GMT+01:00 Alex Harui : > The NPM install name is defined in

Updating 2015 FlexJS presentation

Hi: Om presented this slide deck at ApacheCon in 2015 [1]. The FlexJS help docs refer to it, and I wondered if it would be worth updating for current use with Royale. I would be happy to do the grunt work of updating the slides if someone can provide the PowerPoint. Do we have a place to host

Re: Directory and File naming conventions

On 1/24/18, 9:59 AM, "Alex Harui" wrote: >Hi Andrew, > >Thanks for doing the research. I didn't even think about "-". That seems >like a good idea to me. Speaking of '-', I saw in your recent commit that the Front Matter title had '-' in it. That title becomes the

Re: Cannot install royale-swf from npm

The NPM install name is defined in package.json. The -bin-js package is JS only, no SWF support. It's package name is 'royale'. Turns out there is already a 'royale' out there, so I've already changed it to 'apache-royale' in the nightly builds and for the next release. Technically, we

Re: Different results for compilation Error in JS and SWF compilation

Links are still broken. Paste.a.o might be having problems. Try just cut and paste of a section of the main differences. -Alex On 1/24/18, 10:19 AM, "Piotr Zarzycki" wrote: >Something happened with Apache paste. Posting once again. > >JSRoyale compilation error [1]

Re: Different results for compilation Error in JS and SWF compilation

Something happened with Apache paste. Posting once again. JSRoyale compilation error [1] SWF compilation error [2] [1] https://paste.apache.org/JdNf [2] https://paste.apache.org/QgUo 2018-01-24 18:22 GMT+01:00 Alex Harui : > The links do not work for me. > > -Alex >

Re: Directory and File naming conventions

On 1/24/18, 10:07 AM, "Andrew Wetmore" wrote: >My argument for sentence case over title case is that, in general, fewer >capital letters makes for easier scanning and comprehension, especially >for >folks for whom English is not the first or a comfortable language. OK, If

Re: Cannot install royale-swf from npm

Alex, Can we republish once again everything ? If not can we upload binaries to Apache mirrors[1] as we had this with Flex ? [1] http://www.apache.org/dyn/closer.lua/flex/4.16.1/binaries/apache-flex-sdk-4.16.1-bin.zip Thanks, Piotr 2018-01-24 19:11 GMT+01:00 Alex Harui

Re: Cannot install royale-swf from npm

Bummer. Maybe nobody actually tested the royale-swf package. I only tested the royale package which we did not publish due to collision with another royale package out there. In the next release we will name the packages apache-royale and apache-royale-swf. Do you have time to try to fix it?

Re: Directory and File naming conventions

My argument for sentence case over title case is that, in general, fewer capital letters makes for easier scanning and comprehension, especially for folks for whom English is not the first or a comfortable language. I do not have time today to scrub existing files and the table of contents, and I

Re: [DRAFT] [ANNOUNCE] Apache Royale 0.9.0 Released

Tweakage: I would change this passage This release should be considered ‘beta' quality. The purpose of this release is to gather feedback about the features and implementation strategies, and recruit new contributors as we grow the code base into an SDK and tool chain that delivers the highest

Re: Directory and File naming conventions

Hi Andrew, Thanks for doing the research. I didn't even think about "-". That seems like a good idea to me. I think of page titles and TOC entries as chapter titles in books so my first instinct is to use title case, but if you really want to use sentence case, that's fine with me. I feel the

[DRAFT] [ANNOUNCE] Apache Royale 0.9.0 Released

Please comment on the draft below. Quite frankly, I'm not clear how much noise we want to make about 0.9.0. Looks like NPM is not working at all. Thoughts? -Alex --- The Apache Royale community is pleased to announce the release of Apache Royale 0.9.0. Apache Royale is a new project

Re: Directory and File naming conventions

From a quick and non-comprehensive review: - Practis [1] recommends using all lower case, with no spaces, for file names, with _ or - to join words and no other punctuation. - Huridocs [2] concurs and suggests some tools for doing bulk file renaming. - Winthrop University[4]

Re: Different results for compilation Error in JS and SWF compilation

The links do not work for me. -Alex On 1/24/18, 4:19 AM, "Piotr Zarzycki" wrote: >Carlos, > >I know what causes the error :) I just wanted to know why the message >provided by compiler is different :) > >Piotr > >2018-01-24 13:18 GMT+01:00 Carlos Rovira

Cannot install royale-swf from npm

I get the following console output when I run `npm install -g royale-swf` https://paste.apache.org/xA7e It appears that royale-asjs is missing from the path when running the `npm/dependencies/download_dependencies.js` script. - Josh

Re: Proposed table of contents for Royale help documentation

Hi Carlos, Right now, the master branch is set up to use the Cayman theme. When I took a quick look at Cayman, it appeared to be under Creative Commons, which makes it very difficult for us to use. Unfortunately, just because it is "Open Source" and on GitHub doesn't mean it is compatible with

Re: Directory and File naming conventions

HI Andrew, Good question. I'm pretty sure I don't care as long as it meets usability goals. Maybe you already know what usability goals a "help docs" site should have, but maybe we should first agree on usability goals and work backwards to how the directory and file names affect that if at

Re: Proposed table of contents for Royale help documentation

I am even rewriting the legacy Apache Flex stuff I think we can reuse. Apart from issues of licenses, I don't want to trample on other writers by stealing, as opposing to learning from, their material. On Wed, Jan 24, 2018 at 12:07 PM, Alex Harui wrote: > Again, please

Re: Proposed table of contents for Royale help documentation

Again, please be careful when copying anything you find on the internet. I still think we want to make our doc licensed under the Apache License and lots of web stuff is Creative Commons. The "best" stuff may be under copyrights and other licenses and require attributions that make more work for

Directory and File naming conventions

This is for the help documentation, but maybe there are already some conventions in place for the code base that we should follow. 1. Are we using all lower case, sentence case (Getting started), or initial caps (Getting Started) for directory and file names? 2. Are we using sentence

Re: Different results for compilation Error in JS and SWF compilation

Carlos, I know what causes the error :) I just wanted to know why the message provided by compiler is different :) Piotr 2018-01-24 13:18 GMT+01:00 Carlos Rovira : > there's a need for a final "h" here percentWidt > > so it seems something is wrong in the generation

Re: Different results for compilation Error in JS and SWF compilation

there's a need for a final "h" here percentWidt so it seems something is wrong in the generation right? 2018-01-24 13:08 GMT+01:00 Piotr Zarzycki : > Hi, > > I have found that during SWF only compilation and JS only although I'm > getting the same errors they are

Different results for compilation Error in JS and SWF compilation

Hi, I have found that during SWF only compilation and JS only although I'm getting the same errors they are reported a bit differently. In build: compiler.targets=JSRoyale I got [1] In build: compiler.targets=SWF I got [2] There is no word "Error" in case of JSRoyale - Is this a bug ? [1]

Re: Proposed table of contents for Royale help documentation

Right, when I planned the website, I was learning as well from that websites and apache websites, and copying, mixing from here and there was how I did the current one. I think we should take the test of those for our docs to get the best we can. thanks! :) 2018-01-24 12:35 GMT+01:00 Andrew

Re: Proposed table of contents for Royale help documentation

Thanks for the pointer about the React and Angular sites, Carlos. Lots to learn from! -- Andrew Wetmore http://cottage14.blogspot.com/

Re: Proposed table of contents for Royale help documentation

Great Andrew! :))) 2018-01-24 12:33 GMT+01:00 Andrew Wetmore : > Hi! > > Yes, I feel like a real committer now. > > I am going to migrate some material from the FlexJS documentation to see > what that experience is like. I am going to draw from "Overview" [1] >

Re: Proposed table of contents for Royale help documentation

Hi! Yes, I feel like a real committer now. I am going to migrate some material from the FlexJS documentation to see what that experience is like. I am going to draw from "Overview" [1] to populate both "High level view"

Re: Proposed table of contents for Royale help documentation

Hi Alex, for this reason is better to go with a OS GitHub theme that only needs to use the colors, fonts and logos from our website. Those where selected by me and are not provided by the WP theme. The other main reason is that we need to use something done for that task with the maximum quality.