[ANNOUNCE] Apache Royale 0.9.0 Released

The Apache Royale community is pleased to announce the release of Apache Royale 0.9.0. The Apache Royale project is a continuation of the previous effort called FlexJS to produce a next-generation of the Apache Flex SDK that enables developers to use MXML and ActionScript to generated HTML/JS/CSS

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

On Sun, Jan 28, 2018 at 11:42 PM, Alex Harui wrote: > I was (and still am) confused by Om's effort to publish the NPM artifacts. > I was waiting to hear back from Om as to whether it was going to happen > so we know whether to recommend to folks to use the URL on

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

I was (and still am) confused by Om's effort to publish the NPM artifacts. I was waiting to hear back from Om as to whether it was going to happen so we know whether to recommend to folks to use the URL on GitHub or not. I will send the announcement shortly with the GH URL, and we can send a

Re: Royale Doc Table-of-Contents UX (was Re: Royale Documentation Page Layout Proposal)

This does not use the Jekyll workflow. This uses the .md files directly. Thanks, Om On Jan 28, 2018 10:57 PM, "Alex Harui" wrote: I don’t get it. There is a Jekyll template in our repo. The link I just clicked on did not appear to use it. -Alex On 1/28/18, 4:41

Re: About Royale MDL Examples

Yes, filing a JIRA is probably the next step. When do we want to spend more time on this? -Alex On 1/28/18, 3:37 AM, "Piotr Zarzycki" wrote: >It's been more than a week since Alex asked on legal [1] for advice in >case >of that Examples. No response. What's the next

Re: Royale Doc Table-of-Contents UX (was Re: Royale Documentation Page Layout Proposal)

I don’t get it. There is a Jekyll template in our repo. The link I just clicked on did not appear to use it. -Alex On 1/28/18, 4:41 AM, "Andrew Wetmore" wrote: >Yeah...the one thing it does not have is an expanding-collapsing ToC. The >scrolling is not bad, but the

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

On Jan 28, 2018 3:34 AM, "Piotr Zarzycki" wrote: Om, But Alex figure out that we can use links from GitHub which I published [1]. Only JSOnly working. sudo npm install -g https://github.com/apache/royale-asjs/releases/download/apache-royale-0.9.0

Re: Royale Doc Table-of-Contents UX (was Re: Royale Documentation Page Layout Proposal)

Yeah...the one thing it does not have is an expanding-collapsing ToC. The scrolling is not bad, but the intimidation effect of endless topic titles can be large. For me that is a usability negative...but not a deal-killer. On Sun, Jan 28, 2018 at 7:35 AM, Gabe Harbs wrote:

Re: About Royale MDL Examples

It's been more than a week since Alex asked on legal [1] for advice in case of that Examples. No response. What's the next step ? Maybe jira with his question ? [1] https://goo.gl/s5Zp1y Thanks, Piotr 2018-01-18 12:59 GMT+01:00 Carlos Rovira : > Hi Piotr, > > for me

Re: Royale Doc Table-of-Contents UX (was Re: Royale Documentation Page Layout Proposal)

BTW: That site has 3 levels in the table of contents: https://redux.js.org/docs/recipes/reducers/PrerequisiteConcepts.html > On Jan 28, 2018, at 1:20 PM, OmPrakash Muppirala wrote: > > Here is a very

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

Om, But Alex figure out that we can use links from GitHub which I published [1]. Only JSOnly working. sudo npm install -g https://github.com/apache/royale-asjs/releases/download/apache-royale-0.9.0 /apache-royale-0.9.0-bin-js.tar.gz Can we for that release ? Thanks, Piotr 2018-01-28 12:31

Re: Royale Doc Table-of-Contents UX (was Re: Royale Documentation Page Layout Proposal)

I’d say “go for it”! > On Jan 28, 2018, at 1:20 PM, OmPrakash Muppirala wrote: > > Here is a very good example of what the end product would look like: > https://redux.js.org/ > > Thanks, > Om > > On Sun, Jan 28, 2018 at 3:14 AM, OmPrakash Muppirala

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

On Sun, Jan 28, 2018 at 3:29 AM, Piotr Zarzycki wrote: > Yeah. I was going to ask for the Announce as well. Let's mention link to > working version of NPM, which you Alex figure out. We could put them to the > website. > As mentioned earlier, the npm package is broken

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

Yeah. I was going to ask for the Announce as well. Let's mention link to working version of NPM, which you Alex figure out. We could put them to the website. Thanks, Piotr 2018-01-28 11:24 GMT+01:00 Carlos Rovira : > Hi, > > I'm a bit confused here. What happen with the

Re: Royale Doc Table-of-Contents UX (was Re: Royale Documentation Page Layout Proposal)

Here is a very good example of what the end product would look like: https://redux.js.org/ Thanks, Om On Sun, Jan 28, 2018 at 3:14 AM, OmPrakash Muppirala wrote: > > > On Sun, Jan 28, 2018 at 3:13 AM, Gabe Harbs wrote: > >> Is this an additional

Re: Royale Doc Table-of-Contents UX (was Re: Royale Documentation Page Layout Proposal)

On Sun, Jan 28, 2018 at 3:13 AM, Gabe Harbs wrote: > Is this an additional way of viewing the content or a replacement for the > Jenkyll-produced site? > > If it’s the former, I can’t see any reason why not. > It's an additional way. It uses the .md files from the github

Re: Royale Doc Table-of-Contents UX (was Re: Royale Documentation Page Layout Proposal)

Is this an additional way of viewing the content or a replacement for the Jenkyll-produced site? If it’s the former, I can’t see any reason why not. Harbs > On Jan 28, 2018, at 1:09 PM, OmPrakash Muppirala wrote: > > I've been playing around with the tool: GitBook

Re: Royale Doc Table-of-Contents UX (was Re: Royale Documentation Page Layout Proposal)

I've been playing around with the tool: GitBook [www.gitbooks.io] I was able to connect my personal fork of the royale-docs to my gitbooks.io account. This way, all my .md files are automatically available for Docs creation. Here is an example I created in a few minutes:

Re: Royale Doc Table-of-Contents UX (was Re: Royale Documentation Page Layout Proposal)

If the ToC accordions properly and we need three levels, I do not see why three levels would cause more confusion than two levels. If this is a resource providing information people are going to need to use Royale, and if that information is not readily available elsewhere, then we should make the

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

Hi, I'm a bit confused here. What happen with the release and announcement? If we have a release we should announce it. We published in twitter and facebook that we was very close to our first release but starts to be a big delay since that. Thanks 2018-01-25 20:29 GMT+01:00 Jason Guild

Re: Royale Documentation Page Layout Proposal

Right, we should make this ourselves, but in the right way, using the right path designed for this. The wheel is already created so we should find how to make the wheel and not trying to reinvent it. In [1] seems to be the right steps to create a Jekyll theme from scratch. I think we should

Re: Royale Doc Table-of-Contents UX (was Re: Royale Documentation Page Layout Proposal)

Hi Alex, for TOC. One think that's very important to me: Please only *two levels* in TOC. For simplicity and clarity. Like the demo page I did. It's the standard right now and a three level only created confusion. Again see Angular and React sites to match what they did and take it as a