[ANNOUNCE] Apache Royale 0.9.0 Released

[Alex Harui]

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 so
applications can run natively in browsers.  The cross-compiled code can
also be used in Apache Cordova (Adobe PhoneGap) mobile applications.

(Apache Flex is a highly productive, open source application framework for
building and maintaining expressive applications that deploy on Adobe
Flash and Adobe AIR to provide a consistent experience on all major
browsers, desktops and devices.)

This release should be considered ‘beta' quality. The purpose of this
release is to gather feedback about the features and implementation
strategies, and to recruit new contributors. We hope to grow the code base
into an SDK and tool chain that delivers the highest productivity when
developing applications that can run on many platforms. Beta releases may
not handle production needs.

Please file bugs at:

  https://github.com/apache/royale-asjs/issues

If you happen to know it is a compiler issue, please use:

  https://github.com/apache/royale-compiler/issues

For questions about how to use Royale, send email to
us...@royale.apache.org.  For questions and feedback on the development of
the source code in the release, send email to dev@royale.apache.org.

Apache Royale is available in source and binary form from the Apache
mirrors:

Source:
http://www.apache.org/dyn/closer.lua/royale/0.9.0/apache-royale-0.9.0-src.t
ar.gz
http://www.apache.org/dyn/closer.lua/royale/0.9.0/apache-royale-0.9.0-src.z
ip

Binary:
http://www.apache.org/dyn/closer.lua/royale/0.9.0/binaries/apache-royale-0.
9.0-bin-js.tar.gz
http://www.apache.org/dyn/closer.lua/royale/0.9.0/binaries/apache-royale-0.
9.0-bin-js.zip

Binary with SWF support:
http://www.apache.org/dyn/closer.lua/royale/0.9.0/binaries/apache-royale-0.
9.0-bin-js-swf.tar.gz
http://www.apache.org/dyn/closer.lua/royale/0.9.0/binaries/apache-royale-0.
9.0-bin-js-swf.zip

When downloading from a mirror site, please remember to verify the
downloads using signatures or MD5 hashes.

The -bin-js-swf package is not working when installed via NPM.  The bin-js
package can be installed via NPM by running:

Mac:

  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

Windows:

  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

We expect the packages to be available in the NPM registry in future
releases.

See the README for more information. Visit http://royale.apache.org/ for
links to other resources.

Please try Royale and become involved in shaping the future of application
development.

The Apache Royale Community

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

[OmPrakash Muppirala]

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 GitHub or not.
>
> I will send the announcement shortly with the GH URL, and we can send a
> correction later if Om figures out how to get the packages published in
> NPM.
>

I'm working on the scripts right now.  As I mentioned earlier, that wont
work until the next release of Royale.
It would be best to recommend users to install via the github url for now.

Thanks,
Om


>
> Thanks,
> -Alex
>
> On 1/28/18, 3:31 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
>  wrote:
>
> >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 for this release.  We will
> >fix it in the next release of royale.
> >I'm working on publishing those anyway so that we have a process setup for
> >the next release.
> >
> >Thanks,
> >Om
> >
> >
> >>
> >> Thanks,
> >> Piotr
> >>
> >> 2018-01-28 11:24 GMT+01:00 Carlos Rovira :
> >>
> >> > 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 :
> >> >
> >> > > Alex:
> >> > >
> >> > > A suggestion for improving the opening sentence:
> >> > > The Apache Royale project is a continuation of the previous effort
> >> called
> >> > > FlexJS to produce a next-generation of the Apache Flex SDK that...
> >> > >
> >> > >
> >> > > On 1/25/2018 12:51 AM, Alex Harui wrote:
> >> > >
> >> > >> Apache Royale is a new project that took over the work on what was
> >> being
> >> > >> called FlexJS, a next-generation of the Apache Flex SDK that
> >>enables
> >> > >> developers to use MXML and ActionScript to generated HTML/JS/CSS so
> >> > >> applications can run natively in browsers.  The cross-compiled code
> >> can
> >> > >> also be used in Apache Cordova (Adobe PhoneGap) mobile
> >>applications.
> >> > >>
> >> > >
> >> > > --
> >> > > Jason Guild
> >> > > Analyst/Programmer V
> >> > > State of Alaska - Department of Transportation & Public Facilities
> >> > > Information Systems and Services Division
> >> > > 820 E. 15th Ave.
> >> > > Anchorage, Alaska 99501
> >> > >
> >> > >
> >> >
> >> >
> >> > --
> >> > Carlos Rovira
> >> >
> >>https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fabout.me%
> >>2Fcarlosrovira=02%7C01%7Caharui%40adobe.com%
> 7Ccb239e35d72348b9c4b608
> >>d56642d3a9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C63652735958959059
> >>3=TSXP862xzR7UwLRN29XYaUNax18DCxNboYgzUCiF71c%3D=0
> >> >
> >>
> >>
> >>
> >> --
> >>
> >> Piotr Zarzycki
> >>
> >> Patreon:
> >>*https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fwww.pat
> >>reon.com%2Fpiotrzarzycki=02%7C01%7Caharui%40adobe.com
> %7Ccb239e35d723
> >>48b9c4b608d56642d3a9%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6365273
> >>59589590593=cVHyuJ6atF9bUjtXpACaWgvNHGBCzS
> 6NE4AU5TFNTf4%3D
> >>=0
> >>
> >> https%3A%2F%2Fwww.pat
> >>reon.com%2Fpiotrzarzycki=02%7C01%7Caharui%40adobe.com
> %7Ccb239e35d723
> >>48b9c4b608d56642d3a9%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6365273
> >>59589590593=cVHyuJ6atF9bUjtXpACaWgvNHGBCzS
> 6NE4AU5TFNTf4%3D
> >>=0>*
> >>
>
>

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

[Alex Harui]

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
correction later if Om figures out how to get the packages published in
NPM.

Thanks,
-Alex

On 1/28/18, 3:31 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
 wrote:

>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 for this release.  We will
>fix it in the next release of royale.
>I'm working on publishing those anyway so that we have a process setup for
>the next release.
>
>Thanks,
>Om
>
>
>>
>> Thanks,
>> Piotr
>>
>> 2018-01-28 11:24 GMT+01:00 Carlos Rovira :
>>
>> > 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 :
>> >
>> > > Alex:
>> > >
>> > > A suggestion for improving the opening sentence:
>> > > The Apache Royale project is a continuation of the previous effort
>> called
>> > > FlexJS to produce a next-generation of the Apache Flex SDK that...
>> > >
>> > >
>> > > On 1/25/2018 12:51 AM, Alex Harui wrote:
>> > >
>> > >> Apache Royale is a new project that took over the work on what was
>> being
>> > >> called FlexJS, a next-generation of the Apache Flex SDK that
>>enables
>> > >> developers to use MXML and ActionScript to generated HTML/JS/CSS so
>> > >> applications can run natively in browsers.  The cross-compiled code
>> can
>> > >> also be used in Apache Cordova (Adobe PhoneGap) mobile
>>applications.
>> > >>
>> > >
>> > > --
>> > > Jason Guild
>> > > Analyst/Programmer V
>> > > State of Alaska - Department of Transportation & Public Facilities
>> > > Information Systems and Services Division
>> > > 820 E. 15th Ave.
>> > > Anchorage, Alaska 99501
>> > >
>> > >
>> >
>> >
>> > --
>> > Carlos Rovira
>> > 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%
>>2Fcarlosrovira=02%7C01%7Caharui%40adobe.com%7Ccb239e35d72348b9c4b608
>>d56642d3a9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63652735958959059
>>3=TSXP862xzR7UwLRN29XYaUNax18DCxNboYgzUCiF71c%3D=0
>> >
>>
>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: 
>>*https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.pat
>>reon.com%2Fpiotrzarzycki=02%7C01%7Caharui%40adobe.com%7Ccb239e35d723
>>48b9c4b608d56642d3a9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365273
>>59589590593=cVHyuJ6atF9bUjtXpACaWgvNHGBCzS6NE4AU5TFNTf4%3D
>>=0
>> 
>>>reon.com%2Fpiotrzarzycki=02%7C01%7Caharui%40adobe.com%7Ccb239e35d723
>>48b9c4b608d56642d3a9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365273
>>59589590593=cVHyuJ6atF9bUjtXpACaWgvNHGBCzS6NE4AU5TFNTf4%3D
>>=0>*
>>

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

[OmPrakash Muppirala]

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 AM, "Andrew Wetmore"  wrote:

>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:
>
>> BTW:
>>
>> That site has 3 levels in the table of contents:
>>
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fredux.js
>>.org%2Fdocs%2Frecipes%2Freducers%2FPrerequisiteConcepts.html=02%7C01
>>%7Caharui%40adobe.com%7Ce35c7c4743804324141308d5664c8547%7Cfa7b1b5a7b3443
>>8794aed2c178decee1%7C0%7C0%7C636527401200834465=4Bdy4FThikLGQukS0SS
>>d6DXKBbnoe0oMuSrJ%2BpxpHYw%3D=0 <
>>
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fredux.js
>>.org%2Fdocs%2Frecipes%2Freducers%2FPrerequisiteConcepts.html=02%7C01
>>%7Caharui%40adobe.com%7Ce35c7c4743804324141308d5664c8547%7Cfa7b1b5a7b3443
>>8794aed2c178decee1%7C0%7C0%7C636527401200834465=4Bdy4FThikLGQukS0SS
>>d6DXKBbnoe0oMuSrJ%2BpxpHYw%3D=0>
>>
>> > 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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fredux.js
>>.org%2F=02%7C01%7Caharui%40adobe.com%7Ce35c7c4743804324141308d5664c8
>>547%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636527401200834465
>>=GrTlTr5PCqHK6qS9pg9dKcKyRtO6BJU1xpxLGzWYOsY%3D=0
>> >
>> > Thanks,
>> > Om
>> >
>> > On Sun, Jan 28, 2018 at 3:14 AM, OmPrakash Muppirala <
>> bigosma...@gmail.com>
>> > wrote:
>> >
>> >>
>> >>
>> >> 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 repo
>>and
>> >> builds its own site.
>> >>
>> >> Thanks,
>> >> Om
>> >>
>> >>
>> >>>
>> >>> Harbs
>> >>>
>>  On Jan 28, 2018, at 1:09 PM, OmPrakash Muppirala <
>> bigosma...@gmail.com>
>> >>> wrote:
>> 
>>  I've been playing around with the tool: GitBook
>>[https://na01.safelinks.protection.outlook.com/?url=www.gitbooks.io=
>>02%7C01%7Caharui%40adobe.com%7Ce35c7c4743804324141308d5664c8547%7Cfa7b1b5
>>a7b34438794aed2c178decee1%7C0%7C0%7C636527401200834465=VI3BEHW9v7GP
>>nAlTOg2gEp%2FgLrF61UFUShsrxY1wG7I%3D=0]
>>  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:
>> 
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbigosmal
>>lm.gitbooks.io%2Froyale-docs-test2%2Fcontent%2Fv%2F=02%7C01%7Caharui
>>%40adobe.com%7Ce35c7c4743804324141308d5664c8547%7Cfa7b1b5a7b34438794aed2c
>>178decee1%7C0%7C0%7C636527401200834465=wYN9q4TD9UFz8rwXmzoh8QDc16En
>>Q64NDLMa4XKvMdg%3D=0
>> >>> develop/Create%20An%20Application.html
>> 
>>  The advantages I see using this tool are:
>> 
>>  * Seems to be a widely used tool for documentation these days.
>> >>> NPMjs.org,
>>  React, Redux, etc. use Gitbook
>>  * Two way sync between github and gitbook app.  That is, you can
>> create
>> >>> an
>>  .md file on github and see it on gitbook.  You can also create more
>> >>> content
>>  using the WYSIWYG editor on Gitbook, which will be synced to the
>> github
>>  repo.
>>  * Seems pretty straightforward to create a TOC.  It includes
>>support
>> for
>>  tree structure by default
>>  * We can choose to use the web app on gitbook.com or use the open
>>  source(Apache V2 licensed |
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.c
>>om%2FGitbookIO%2Fgitbook=02%7C01%7Caharui%40adobe.com%7Ce35c7c474380
>>4324141308d5664c8547%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365274
>>01200834465=9yrCy9F6C7auYCI%2FEjfdLi8gTkkma%2FN4rURUrFDU%2FZI%3D
>>served=0)
>> >>> command
>>  line tool.  The CLI will help us integrate with our Jenkins build
>>for
>>  example.
>>  * Allows users to provide feedback on the site itself
>>  * Allows us to point the docs site to our custom domain address
>> 
>> 
>>  If there is more interest in trying this out, I can set up an
>> >>> Organization
>>  account (free) and add users as needed.
>> 
>>  Thanks,
>>  Om
>> 
>>  On Sun, Jan 28, 2018 at 2:53 AM, Andrew Wetmore

Re: About Royale MDL Examples

[Alex Harui]

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 step ? Maybe jira with his
>question ?
>
>[1] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgoo.gl%2F
>s5Zp1y=02%7C01%7Caharui%40adobe.com%7C4d3f223be1764199838708d56643928
>c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636527362778153010=Ms
>5LmB%2F%2FyotheduBEC2yNYACGTZ%2Bhwenw2CwZj6sUU8%3D=0
>
>Thanks, Piotr
>
>2018-01-18 12:59 GMT+01:00 Carlos Rovira :
>
>> Hi Piotr,
>>
>> for me it's ok. My opinion is that example should be accesible but
>>outside
>> this project for two reasons:
>>
>> 1.- Could be important for people currently using MDL library.
>>
>> 2.- As I stated, I want to concentrate our energies in new Royale UI Set
>> that eventually has an MDL theme. So maybe this change will encourage
>>us to
>> think that is more important to invest in our own set that continue
>>working
>> in a library that is based on an external set that we don't control (and
>> that's deprecated too in favor of material components by google)
>>
>> So if you want to host it is ok for me, if you do, I'll do nothing since
>> it's better to have only one repo for both samples, so people doesn't
>>get
>> confused
>>
>> I think we need to wait for legal decisions about this
>>
>> thanks!
>>
>> Carlos
>>
>>
>>
>> 2018-01-18 12:49 GMT+01:00 Piotr Zarzycki :
>>
>> > Hi Carlos,
>> >
>> > I don't mind if you do this.
>> > I will personally for sure add those examples to my own repo as I
>>stated
>> in
>> > the RC thread - IF Legal won't allow as to use it. By won't allow I
>>mean
>> > the situation where we will have to do some magic to have that
>>example.
>> >
>> > Legal discussion is in progress, so I would wait once it will be
>> finished.
>> >
>> > Thanks, Piotr
>> >
>> >
>> > 2018-01-18 12:39 GMT+01:00 Carlos Rovira :
>> >
>> > > Hi,
>> > >
>> > > separating MDL examples problem from release so we can get that done
>> soon
>> > > with less noise.
>> > >
>> > > I want to ask here if it would be ok to upload both conflictive
>> examples
>> > to
>> > > my own github account so people interested can access it.
>> > >
>> > > Let me know in order to proceed.
>> > >
>> > > --
>> > > Carlos Rovira
>> > > 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%
>>2Fcarlosrovira=02%7C01%7Caharui%40adobe.com%7C4d3f223be1764199838708
>>d56643928c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63652736277815301
>>0=YoEA9I6ecNlmY5bL4FW0h2G8d75IOHyR%2BJht2pf%2BSX8%3D=0
>> > >
>> >
>> >
>> >
>> > --
>> >
>> > Piotr Zarzycki
>> >
>> > Patreon: 
>>*https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.pat
>>reon.com%2Fpiotrzarzycki=02%7C01%7Caharui%40adobe.com%7C4d3f223be176
>>4199838708d56643928c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365273
>>62778153010=nn4DdbQaMWiA5NPeJt2IHEqSFGOcYJqWoSBelptFxCM%3D
>>=0
>> > 
>>>reon.com%2Fpiotrzarzycki=02%7C01%7Caharui%40adobe.com%7C4d3f223be176
>>4199838708d56643928c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365273
>>62778153010=nn4DdbQaMWiA5NPeJt2IHEqSFGOcYJqWoSBelptFxCM%3D
>>=0>*
>> >
>>
>>
>>
>> --
>> Carlos Rovira
>> 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%
>>2Fcarlosrovira=02%7C01%7Caharui%40adobe.com%7C4d3f223be1764199838708
>>d56643928c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63652736277815301
>>0=YoEA9I6ecNlmY5bL4FW0h2G8d75IOHyR%2BJht2pf%2BSX8%3D=0
>>
>
>
>
>-- 
>
>Piotr Zarzycki
>
>Patreon: 
>*https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patr
>eon.com%2Fpiotrzarzycki=02%7C01%7Caharui%40adobe.com%7C4d3f223be17641
>99838708d56643928c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365273627
>78153010=nn4DdbQaMWiA5NPeJt2IHEqSFGOcYJqWoSBelptFxCM%3D=0
>eon.com%2Fpiotrzarzycki=02%7C01%7Caharui%40adobe.com%7C4d3f223be17641
>99838708d56643928c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365273627
>78153010=nn4DdbQaMWiA5NPeJt2IHEqSFGOcYJqWoSBelptFxCM%3D=0>*

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

[Alex Harui]

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 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:
>
>> BTW:
>>
>> That site has 3 levels in the table of contents:
>> 
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fredux.js
>>.org%2Fdocs%2Frecipes%2Freducers%2FPrerequisiteConcepts.html=02%7C01
>>%7Caharui%40adobe.com%7Ce35c7c4743804324141308d5664c8547%7Cfa7b1b5a7b3443
>>8794aed2c178decee1%7C0%7C0%7C636527401200834465=4Bdy4FThikLGQukS0SS
>>d6DXKBbnoe0oMuSrJ%2BpxpHYw%3D=0 <
>> 
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fredux.js
>>.org%2Fdocs%2Frecipes%2Freducers%2FPrerequisiteConcepts.html=02%7C01
>>%7Caharui%40adobe.com%7Ce35c7c4743804324141308d5664c8547%7Cfa7b1b5a7b3443
>>8794aed2c178decee1%7C0%7C0%7C636527401200834465=4Bdy4FThikLGQukS0SS
>>d6DXKBbnoe0oMuSrJ%2BpxpHYw%3D=0>
>>
>> > 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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fredux.js
>>.org%2F=02%7C01%7Caharui%40adobe.com%7Ce35c7c4743804324141308d5664c8
>>547%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636527401200834465
>>=GrTlTr5PCqHK6qS9pg9dKcKyRtO6BJU1xpxLGzWYOsY%3D=0
>> >
>> > Thanks,
>> > Om
>> >
>> > On Sun, Jan 28, 2018 at 3:14 AM, OmPrakash Muppirala <
>> bigosma...@gmail.com>
>> > wrote:
>> >
>> >>
>> >>
>> >> 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 repo
>>and
>> >> builds its own site.
>> >>
>> >> Thanks,
>> >> Om
>> >>
>> >>
>> >>>
>> >>> Harbs
>> >>>
>>  On Jan 28, 2018, at 1:09 PM, OmPrakash Muppirala <
>> bigosma...@gmail.com>
>> >>> wrote:
>> 
>>  I've been playing around with the tool: GitBook
>>[https://na01.safelinks.protection.outlook.com/?url=www.gitbooks.io=
>>02%7C01%7Caharui%40adobe.com%7Ce35c7c4743804324141308d5664c8547%7Cfa7b1b5
>>a7b34438794aed2c178decee1%7C0%7C0%7C636527401200834465=VI3BEHW9v7GP
>>nAlTOg2gEp%2FgLrF61UFUShsrxY1wG7I%3D=0]
>>  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:
>>  
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbigosmal
>>lm.gitbooks.io%2Froyale-docs-test2%2Fcontent%2Fv%2F=02%7C01%7Caharui
>>%40adobe.com%7Ce35c7c4743804324141308d5664c8547%7Cfa7b1b5a7b34438794aed2c
>>178decee1%7C0%7C0%7C636527401200834465=wYN9q4TD9UFz8rwXmzoh8QDc16En
>>Q64NDLMa4XKvMdg%3D=0
>> >>> develop/Create%20An%20Application.html
>> 
>>  The advantages I see using this tool are:
>> 
>>  * Seems to be a widely used tool for documentation these days.
>> >>> NPMjs.org,
>>  React, Redux, etc. use Gitbook
>>  * Two way sync between github and gitbook app.  That is, you can
>> create
>> >>> an
>>  .md file on github and see it on gitbook.  You can also create more
>> >>> content
>>  using the WYSIWYG editor on Gitbook, which will be synced to the
>> github
>>  repo.
>>  * Seems pretty straightforward to create a TOC.  It includes
>>support
>> for
>>  tree structure by default
>>  * We can choose to use the web app on gitbook.com or use the open
>>  source(Apache V2 licensed |
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.c
>>om%2FGitbookIO%2Fgitbook=02%7C01%7Caharui%40adobe.com%7Ce35c7c474380
>>4324141308d5664c8547%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365274
>>01200834465=9yrCy9F6C7auYCI%2FEjfdLi8gTkkma%2FN4rURUrFDU%2FZI%3D
>>served=0)
>> >>> command
>>  line tool.  The CLI will help us integrate with our Jenkins build
>>for
>>  example.
>>  * Allows users to provide feedback on the site itself
>>  * Allows us to point the docs site to our custom domain address
>> 
>> 
>>  If there is more interest in trying this out, I can set up an
>> >>> Organization
>>  account (free) and add users as needed.
>> 
>>  Thanks,
>>  Om
>> 
>>  On Sun, Jan 28, 2018 at 2:53 AM, Andrew Wetmore
>>
>> >>> wrote:
>> 
>> > If the ToC accordions properly and we need three levels, I do not
>>see
>> >>> why
>> > three levels would 

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

[OmPrakash Muppirala]

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
/apache-royale-0.9.0-bin-js.tar.gz

Can we for that release ?



Yes, we can announce this.  Sorry for the confusion.

Thanks,
Om


Thanks, Piotr


2018-01-28 12:31 GMT+01:00 OmPrakash Muppirala :

> 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 for this release.  We will
> fix it in the next release of royale.
> I'm working on publishing those anyway so that we have a process setup for
> the next release.
>
> Thanks,
> Om
>
>
> >
> > Thanks,
> > Piotr
> >
> > 2018-01-28 11:24 GMT+01:00 Carlos Rovira :
> >
> > > 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 :
> > >
> > > > Alex:
> > > >
> > > > A suggestion for improving the opening sentence:
> > > > The Apache Royale project is a continuation of the previous effort
> > called
> > > > FlexJS to produce a next-generation of the Apache Flex SDK that...
> > > >
> > > >
> > > > On 1/25/2018 12:51 AM, Alex Harui wrote:
> > > >
> > > >> Apache Royale is a new project that took over the work on what was
> > being
> > > >> called FlexJS, a next-generation of the Apache Flex SDK that
enables
> > > >> developers to use MXML and ActionScript to generated HTML/JS/CSS so
> > > >> applications can run natively in browsers.  The cross-compiled code
> > can
> > > >> also be used in Apache Cordova (Adobe PhoneGap) mobile
applications.
> > > >>
> > > >
> > > > --
> > > > Jason Guild
> > > > Analyst/Programmer V
> > > > State of Alaska - Department of Transportation & Public Facilities
> > > > Information Systems and Services Division
> > > > 820 E. 15th Ave.
> > > > Anchorage, Alaska 99501
> > > >
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > *
> >
>



--

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

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

[Andrew Wetmore]

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:

> BTW:
>
> That site has 3 levels in the table of contents:
> https://redux.js.org/docs/recipes/reducers/PrerequisiteConcepts.html <
> https://redux.js.org/docs/recipes/reducers/PrerequisiteConcepts.html>
>
> > 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 <
> bigosma...@gmail.com>
> > wrote:
> >
> >>
> >>
> >> 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 repo and
> >> builds its own site.
> >>
> >> Thanks,
> >> Om
> >>
> >>
> >>>
> >>> Harbs
> >>>
>  On Jan 28, 2018, at 1:09 PM, OmPrakash Muppirala <
> bigosma...@gmail.com>
> >>> wrote:
> 
>  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:
>  https://bigosmallm.gitbooks.io/royale-docs-test2/content/v/
> >>> develop/Create%20An%20Application.html
> 
>  The advantages I see using this tool are:
> 
>  * Seems to be a widely used tool for documentation these days.
> >>> NPMjs.org,
>  React, Redux, etc. use Gitbook
>  * Two way sync between github and gitbook app.  That is, you can
> create
> >>> an
>  .md file on github and see it on gitbook.  You can also create more
> >>> content
>  using the WYSIWYG editor on Gitbook, which will be synced to the
> github
>  repo.
>  * Seems pretty straightforward to create a TOC.  It includes support
> for
>  tree structure by default
>  * We can choose to use the web app on gitbook.com or use the open
>  source(Apache V2 licensed | https://github.com/GitbookIO/gitbook)
> >>> command
>  line tool.  The CLI will help us integrate with our Jenkins build for
>  example.
>  * Allows users to provide feedback on the site itself
>  * Allows us to point the docs site to our custom domain address
> 
> 
>  If there is more interest in trying this out, I can set up an
> >>> Organization
>  account (free) and add users as needed.
> 
>  Thanks,
>  Om
> 
>  On Sun, Jan 28, 2018 at 2:53 AM, Andrew Wetmore 
> >>> wrote:
> 
> > 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 ToC fit the information, not the other way around.
> >
> > On Sun, Jan 28, 2018 at 5:56 AM, Carlos Rovira <
> >>> carlosrov...@apache.org>
> > wrote:
> >
> >> 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
> > reference.
> >>
> >> For states. I think the trick here is that a .md page has some
> >>> variables
> >> that will make the right top level branch open in TOC and as well
> make
> > the
> >> right sub option appears as selected (strong type) and without link.
> >>> As
> > we
> >> are dealing with static GitHub pages I think there's no concept of
> >> component, only that all pages has the TOC added to the sidebar.
> >>
> >>
> >>
> >> 2018-01-27 1:18 GMT+01:00 Andrew Wetmore :
> >>
> >>> What you describe sounds fine to me. I don't think we need to worry
> > about
> >>> breadcrumbs and state and helping people go backwards through their
> >> series
> >>> of clicks.
> >>>
> >>> On Fri, Jan 26, 2018 at 8:09 PM, Alex Harui
>  
> >>> wrote:
> >>>
>  Breaking out a separate thread on this...
> 
>  Thinking about this some more, I think I can generate an
> interactive
>  

Re: About Royale MDL Examples

[Piotr Zarzycki]

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 it's ok. My opinion is that example should be accesible but outside
> this project for two reasons:
>
> 1.- Could be important for people currently using MDL library.
>
> 2.- As I stated, I want to concentrate our energies in new Royale UI Set
> that eventually has an MDL theme. So maybe this change will encourage us to
> think that is more important to invest in our own set that continue working
> in a library that is based on an external set that we don't control (and
> that's deprecated too in favor of material components by google)
>
> So if you want to host it is ok for me, if you do, I'll do nothing since
> it's better to have only one repo for both samples, so people doesn't get
> confused
>
> I think we need to wait for legal decisions about this
>
> thanks!
>
> Carlos
>
>
>
> 2018-01-18 12:49 GMT+01:00 Piotr Zarzycki :
>
> > Hi Carlos,
> >
> > I don't mind if you do this.
> > I will personally for sure add those examples to my own repo as I stated
> in
> > the RC thread - IF Legal won't allow as to use it. By won't allow I mean
> > the situation where we will have to do some magic to have that example.
> >
> > Legal discussion is in progress, so I would wait once it will be
> finished.
> >
> > Thanks, Piotr
> >
> >
> > 2018-01-18 12:39 GMT+01:00 Carlos Rovira :
> >
> > > Hi,
> > >
> > > separating MDL examples problem from release so we can get that done
> soon
> > > with less noise.
> > >
> > > I want to ask here if it would be ok to upload both conflictive
> examples
> > to
> > > my own github account so people interested can access it.
> > >
> > > Let me know in order to proceed.
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > *
> >
>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>



-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

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

[Gabe Harbs]

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 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 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 repo and
>> builds its own site.
>> 
>> Thanks,
>> Om
>> 
>> 
>>> 
>>> Harbs
>>> 
 On Jan 28, 2018, at 1:09 PM, OmPrakash Muppirala 
>>> wrote:
 
 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:
 https://bigosmallm.gitbooks.io/royale-docs-test2/content/v/
>>> develop/Create%20An%20Application.html
 
 The advantages I see using this tool are:
 
 * Seems to be a widely used tool for documentation these days.
>>> NPMjs.org,
 React, Redux, etc. use Gitbook
 * Two way sync between github and gitbook app.  That is, you can create
>>> an
 .md file on github and see it on gitbook.  You can also create more
>>> content
 using the WYSIWYG editor on Gitbook, which will be synced to the github
 repo.
 * Seems pretty straightforward to create a TOC.  It includes support for
 tree structure by default
 * We can choose to use the web app on gitbook.com or use the open
 source(Apache V2 licensed | https://github.com/GitbookIO/gitbook)
>>> command
 line tool.  The CLI will help us integrate with our Jenkins build for
 example.
 * Allows users to provide feedback on the site itself
 * Allows us to point the docs site to our custom domain address
 
 
 If there is more interest in trying this out, I can set up an
>>> Organization
 account (free) and add users as needed.
 
 Thanks,
 Om
 
 On Sun, Jan 28, 2018 at 2:53 AM, Andrew Wetmore 
>>> wrote:
 
> 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 ToC fit the information, not the other way around.
> 
> On Sun, Jan 28, 2018 at 5:56 AM, Carlos Rovira <
>>> carlosrov...@apache.org>
> wrote:
> 
>> 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
> reference.
>> 
>> For states. I think the trick here is that a .md page has some
>>> variables
>> that will make the right top level branch open in TOC and as well make
> the
>> right sub option appears as selected (strong type) and without link.
>>> As
> we
>> are dealing with static GitHub pages I think there's no concept of
>> component, only that all pages has the TOC added to the sidebar.
>> 
>> 
>> 
>> 2018-01-27 1:18 GMT+01:00 Andrew Wetmore :
>> 
>>> What you describe sounds fine to me. I don't think we need to worry
> about
>>> breadcrumbs and state and helping people go backwards through their
>> series
>>> of clicks.
>>> 
>>> On Fri, Jan 26, 2018 at 8:09 PM, Alex Harui >> wrote:
>>> 
 Breaking out a separate thread on this...
 
 Thinking about this some more, I think I can generate an interactive
 control with Jekyll, but I don't know how to make it retain state.
>>> I
 think that might require cookies and/or frames.
 
 For example, let's say the TOC looked like:
 
 Welcome
 --High Level View
 --Features
 AS3
 MXML
 Get Started
 --Download
 --Hello World
 
 I've already implemented logic in the template to auto-expand the
> tree
>> to
 the document for folks who have direct links.  So, if you do a
>>> Google

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

[Piotr Zarzycki]

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 GMT+01:00 OmPrakash Muppirala :

> 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 for this release.  We will
> fix it in the next release of royale.
> I'm working on publishing those anyway so that we have a process setup for
> the next release.
>
> Thanks,
> Om
>
>
> >
> > Thanks,
> > Piotr
> >
> > 2018-01-28 11:24 GMT+01:00 Carlos Rovira :
> >
> > > 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 :
> > >
> > > > Alex:
> > > >
> > > > A suggestion for improving the opening sentence:
> > > > The Apache Royale project is a continuation of the previous effort
> > called
> > > > FlexJS to produce a next-generation of the Apache Flex SDK that...
> > > >
> > > >
> > > > On 1/25/2018 12:51 AM, Alex Harui wrote:
> > > >
> > > >> Apache Royale is a new project that took over the work on what was
> > being
> > > >> called FlexJS, a next-generation of the Apache Flex SDK that enables
> > > >> developers to use MXML and ActionScript to generated HTML/JS/CSS so
> > > >> applications can run natively in browsers.  The cross-compiled code
> > can
> > > >> also be used in Apache Cordova (Adobe PhoneGap) mobile applications.
> > > >>
> > > >
> > > > --
> > > > Jason Guild
> > > > Analyst/Programmer V
> > > > State of Alaska - Department of Transportation & Public Facilities
> > > > Information Systems and Services Division
> > > > 820 E. 15th Ave.
> > > > Anchorage, Alaska 99501
> > > >
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > *
> >
>



-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

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

[Gabe Harbs]

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 
> wrote:
> 
>> 
>> 
>> 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 repo and
>> builds its own site.
>> 
>> Thanks,
>> Om
>> 
>> 
>>> 
>>> Harbs
>>> 
 On Jan 28, 2018, at 1:09 PM, OmPrakash Muppirala 
>>> wrote:
 
 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:
 https://bigosmallm.gitbooks.io/royale-docs-test2/content/v/
>>> develop/Create%20An%20Application.html
 
 The advantages I see using this tool are:
 
 * Seems to be a widely used tool for documentation these days.
>>> NPMjs.org,
 React, Redux, etc. use Gitbook
 * Two way sync between github and gitbook app.  That is, you can create
>>> an
 .md file on github and see it on gitbook.  You can also create more
>>> content
 using the WYSIWYG editor on Gitbook, which will be synced to the github
 repo.
 * Seems pretty straightforward to create a TOC.  It includes support for
 tree structure by default
 * We can choose to use the web app on gitbook.com or use the open
 source(Apache V2 licensed | https://github.com/GitbookIO/gitbook)
>>> command
 line tool.  The CLI will help us integrate with our Jenkins build for
 example.
 * Allows users to provide feedback on the site itself
 * Allows us to point the docs site to our custom domain address
 
 
 If there is more interest in trying this out, I can set up an
>>> Organization
 account (free) and add users as needed.
 
 Thanks,
 Om
 
 On Sun, Jan 28, 2018 at 2:53 AM, Andrew Wetmore 
>>> wrote:
 
> 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 ToC fit the information, not the other way around.
> 
> On Sun, Jan 28, 2018 at 5:56 AM, Carlos Rovira <
>>> carlosrov...@apache.org>
> wrote:
> 
>> 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
> reference.
>> 
>> For states. I think the trick here is that a .md page has some
>>> variables
>> that will make the right top level branch open in TOC and as well make
> the
>> right sub option appears as selected (strong type) and without link.
>>> As
> we
>> are dealing with static GitHub pages I think there's no concept of
>> component, only that all pages has the TOC added to the sidebar.
>> 
>> 
>> 
>> 2018-01-27 1:18 GMT+01:00 Andrew Wetmore :
>> 
>>> What you describe sounds fine to me. I don't think we need to worry
> about
>>> breadcrumbs and state and helping people go backwards through their
>> series
>>> of clicks.
>>> 
>>> On Fri, Jan 26, 2018 at 8:09 PM, Alex Harui >> wrote:
>>> 
 Breaking out a separate thread on this...
 
 Thinking about this some more, I think I can generate an interactive
 control with Jekyll, but I don't know how to make it retain state.
>>> I
 think that might require cookies and/or frames.
 
 For example, let's say the TOC looked like:
 
 Welcome
 --High Level View
 --Features
 AS3
 MXML
 Get Started
 --Download
 --Hello World
 
 I've already implemented logic in the template to auto-expand the
> tree
>> to
 the document for folks who have direct links.  So, if you do a
>>> Google
 Search and find the link to the MXML page, when you go to that page,
>> the
 ToC will automatically look like:
 
 Welcome
 --High 

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

[OmPrakash Muppirala]

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 for this release.  We will
fix it in the next release of royale.
I'm working on publishing those anyway so that we have a process setup for
the next release.

Thanks,
Om


>
> Thanks,
> Piotr
>
> 2018-01-28 11:24 GMT+01:00 Carlos Rovira :
>
> > 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 :
> >
> > > Alex:
> > >
> > > A suggestion for improving the opening sentence:
> > > The Apache Royale project is a continuation of the previous effort
> called
> > > FlexJS to produce a next-generation of the Apache Flex SDK that...
> > >
> > >
> > > On 1/25/2018 12:51 AM, Alex Harui wrote:
> > >
> > >> Apache Royale is a new project that took over the work on what was
> being
> > >> called FlexJS, a next-generation of the Apache Flex SDK that enables
> > >> developers to use MXML and ActionScript to generated HTML/JS/CSS so
> > >> applications can run natively in browsers.  The cross-compiled code
> can
> > >> also be used in Apache Cordova (Adobe PhoneGap) mobile applications.
> > >>
> > >
> > > --
> > > Jason Guild
> > > Analyst/Programmer V
> > > State of Alaska - Department of Transportation & Public Facilities
> > > Information Systems and Services Division
> > > 820 E. 15th Ave.
> > > Anchorage, Alaska 99501
> > >
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>

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

[Piotr Zarzycki]

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 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 :
>
> > Alex:
> >
> > A suggestion for improving the opening sentence:
> > The Apache Royale project is a continuation of the previous effort called
> > FlexJS to produce a next-generation of the Apache Flex SDK that...
> >
> >
> > On 1/25/2018 12:51 AM, Alex Harui wrote:
> >
> >> Apache Royale is a new project that took over the work on what was being
> >> called FlexJS, a next-generation of the Apache Flex SDK that enables
> >> developers to use MXML and ActionScript to generated HTML/JS/CSS so
> >> applications can run natively in browsers.  The cross-compiled code can
> >> also be used in Apache Cordova (Adobe PhoneGap) mobile applications.
> >>
> >
> > --
> > Jason Guild
> > Analyst/Programmer V
> > State of Alaska - Department of Transportation & Public Facilities
> > Information Systems and Services Division
> > 820 E. 15th Ave.
> > Anchorage, Alaska 99501
> >
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>



-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

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

[OmPrakash Muppirala]

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 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 repo and
> builds its own site.
>
> Thanks,
> Om
>
>
>>
>> Harbs
>>
>> > On Jan 28, 2018, at 1:09 PM, OmPrakash Muppirala 
>> wrote:
>> >
>> > 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:
>> > https://bigosmallm.gitbooks.io/royale-docs-test2/content/v/
>> develop/Create%20An%20Application.html
>> >
>> > The advantages I see using this tool are:
>> >
>> > * Seems to be a widely used tool for documentation these days.
>> NPMjs.org,
>> > React, Redux, etc. use Gitbook
>> > * Two way sync between github and gitbook app.  That is, you can create
>> an
>> > .md file on github and see it on gitbook.  You can also create more
>> content
>> > using the WYSIWYG editor on Gitbook, which will be synced to the github
>> > repo.
>> > * Seems pretty straightforward to create a TOC.  It includes support for
>> > tree structure by default
>> > * We can choose to use the web app on gitbook.com or use the open
>> > source(Apache V2 licensed | https://github.com/GitbookIO/gitbook)
>> command
>> > line tool.  The CLI will help us integrate with our Jenkins build for
>> > example.
>> > * Allows users to provide feedback on the site itself
>> > * Allows us to point the docs site to our custom domain address
>> >
>> >
>> > If there is more interest in trying this out, I can set up an
>> Organization
>> > account (free) and add users as needed.
>> >
>> > Thanks,
>> > Om
>> >
>> > On Sun, Jan 28, 2018 at 2:53 AM, Andrew Wetmore 
>> wrote:
>> >
>> >> 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 ToC fit the information, not the other way around.
>> >>
>> >> On Sun, Jan 28, 2018 at 5:56 AM, Carlos Rovira <
>> carlosrov...@apache.org>
>> >> wrote:
>> >>
>> >>> 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
>> >> reference.
>> >>>
>> >>> For states. I think the trick here is that a .md page has some
>> variables
>> >>> that will make the right top level branch open in TOC and as well make
>> >> the
>> >>> right sub option appears as selected (strong type) and without link.
>> As
>> >> we
>> >>> are dealing with static GitHub pages I think there's no concept of
>> >>> component, only that all pages has the TOC added to the sidebar.
>> >>>
>> >>>
>> >>>
>> >>> 2018-01-27 1:18 GMT+01:00 Andrew Wetmore :
>> >>>
>>  What you describe sounds fine to me. I don't think we need to worry
>> >> about
>>  breadcrumbs and state and helping people go backwards through their
>> >>> series
>>  of clicks.
>> 
>>  On Fri, Jan 26, 2018 at 8:09 PM, Alex Harui > >
>>  wrote:
>> 
>> > Breaking out a separate thread on this...
>> >
>> > Thinking about this some more, I think I can generate an interactive
>> > control with Jekyll, but I don't know how to make it retain state.
>> I
>> > think that might require cookies and/or frames.
>> >
>> > For example, let's say the TOC looked like:
>> >
>> > Welcome
>> > --High Level View
>> > --Features
>> > AS3
>> > MXML
>> > Get Started
>> > --Download
>> > --Hello World
>> >
>> > I've already implemented logic in the template to auto-expand the
>> >> tree
>> >>> to
>> > the document for folks who have direct links.  So, if you do a
>> Google
>> > Search and find the link to the MXML page, when you go to that page,
>> >>> the
>> > ToC will automatically look like:
>> >
>> > Welcome
>> > --High Level View
>> > --Features
>> > AS3
>> > ---*MXML*
>> > Get Started
>> >
>> >
>> >
>> > If you hit the main doc page, the ToC starts out collapsed so that
>> >> Get
>> 

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

[OmPrakash Muppirala]

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 repo and
builds its own site.

Thanks,
Om


>
> Harbs
>
> > On Jan 28, 2018, at 1:09 PM, OmPrakash Muppirala 
> wrote:
> >
> > 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:
> > https://bigosmallm.gitbooks.io/royale-docs-test2/content/
> v/develop/Create%20An%20Application.html
> >
> > The advantages I see using this tool are:
> >
> > * Seems to be a widely used tool for documentation these days.
> NPMjs.org,
> > React, Redux, etc. use Gitbook
> > * Two way sync between github and gitbook app.  That is, you can create
> an
> > .md file on github and see it on gitbook.  You can also create more
> content
> > using the WYSIWYG editor on Gitbook, which will be synced to the github
> > repo.
> > * Seems pretty straightforward to create a TOC.  It includes support for
> > tree structure by default
> > * We can choose to use the web app on gitbook.com or use the open
> > source(Apache V2 licensed | https://github.com/GitbookIO/gitbook)
> command
> > line tool.  The CLI will help us integrate with our Jenkins build for
> > example.
> > * Allows users to provide feedback on the site itself
> > * Allows us to point the docs site to our custom domain address
> >
> >
> > If there is more interest in trying this out, I can set up an
> Organization
> > account (free) and add users as needed.
> >
> > Thanks,
> > Om
> >
> > On Sun, Jan 28, 2018 at 2:53 AM, Andrew Wetmore 
> wrote:
> >
> >> 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 ToC fit the information, not the other way around.
> >>
> >> On Sun, Jan 28, 2018 at 5:56 AM, Carlos Rovira  >
> >> wrote:
> >>
> >>> 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
> >> reference.
> >>>
> >>> For states. I think the trick here is that a .md page has some
> variables
> >>> that will make the right top level branch open in TOC and as well make
> >> the
> >>> right sub option appears as selected (strong type) and without link. As
> >> we
> >>> are dealing with static GitHub pages I think there's no concept of
> >>> component, only that all pages has the TOC added to the sidebar.
> >>>
> >>>
> >>>
> >>> 2018-01-27 1:18 GMT+01:00 Andrew Wetmore :
> >>>
>  What you describe sounds fine to me. I don't think we need to worry
> >> about
>  breadcrumbs and state and helping people go backwards through their
> >>> series
>  of clicks.
> 
>  On Fri, Jan 26, 2018 at 8:09 PM, Alex Harui  >
>  wrote:
> 
> > Breaking out a separate thread on this...
> >
> > Thinking about this some more, I think I can generate an interactive
> > control with Jekyll, but I don't know how to make it retain state.  I
> > think that might require cookies and/or frames.
> >
> > For example, let's say the TOC looked like:
> >
> > Welcome
> > --High Level View
> > --Features
> > AS3
> > MXML
> > Get Started
> > --Download
> > --Hello World
> >
> > I've already implemented logic in the template to auto-expand the
> >> tree
> >>> to
> > the document for folks who have direct links.  So, if you do a Google
> > Search and find the link to the MXML page, when you go to that page,
> >>> the
> > ToC will automatically look like:
> >
> > Welcome
> > --High Level View
> > --Features
> > AS3
> > ---*MXML*
> > Get Started
> >
> >
> >
> > If you hit the main doc page, the ToC starts out collapsed so that
> >> Get
> > Started isn't pushed down by a bunch of Welcome sub-topics.  So the
> >> ToC
> > initially looks like:
> >
> > Welcome
> > Get Started
> >
> > Now let's say you expand both Welcome and Get Started so you see:
> >
> > Welcome
> > --High Level View
> > --Features
> > Get Started
> > --Download
> 

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

[Gabe Harbs]

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 [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:
> https://bigosmallm.gitbooks.io/royale-docs-test2/content/v/develop/Create%20An%20Application.html
> 
> The advantages I see using this tool are:
> 
> * Seems to be a widely used tool for documentation these days.  NPMjs.org,
> React, Redux, etc. use Gitbook
> * Two way sync between github and gitbook app.  That is, you can create an
> .md file on github and see it on gitbook.  You can also create more content
> using the WYSIWYG editor on Gitbook, which will be synced to the github
> repo.
> * Seems pretty straightforward to create a TOC.  It includes support for
> tree structure by default
> * We can choose to use the web app on gitbook.com or use the open
> source(Apache V2 licensed | https://github.com/GitbookIO/gitbook) command
> line tool.  The CLI will help us integrate with our Jenkins build for
> example.
> * Allows users to provide feedback on the site itself
> * Allows us to point the docs site to our custom domain address
> 
> 
> If there is more interest in trying this out, I can set up an Organization
> account (free) and add users as needed.
> 
> Thanks,
> Om
> 
> On Sun, Jan 28, 2018 at 2:53 AM, Andrew Wetmore  wrote:
> 
>> 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 ToC fit the information, not the other way around.
>> 
>> On Sun, Jan 28, 2018 at 5:56 AM, Carlos Rovira 
>> wrote:
>> 
>>> 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
>> reference.
>>> 
>>> For states. I think the trick here is that a .md page has some variables
>>> that will make the right top level branch open in TOC and as well make
>> the
>>> right sub option appears as selected (strong type) and without link. As
>> we
>>> are dealing with static GitHub pages I think there's no concept of
>>> component, only that all pages has the TOC added to the sidebar.
>>> 
>>> 
>>> 
>>> 2018-01-27 1:18 GMT+01:00 Andrew Wetmore :
>>> 
 What you describe sounds fine to me. I don't think we need to worry
>> about
 breadcrumbs and state and helping people go backwards through their
>>> series
 of clicks.
 
 On Fri, Jan 26, 2018 at 8:09 PM, Alex Harui 
 wrote:
 
> Breaking out a separate thread on this...
> 
> Thinking about this some more, I think I can generate an interactive
> control with Jekyll, but I don't know how to make it retain state.  I
> think that might require cookies and/or frames.
> 
> For example, let's say the TOC looked like:
> 
> Welcome
> --High Level View
> --Features
> AS3
> MXML
> Get Started
> --Download
> --Hello World
> 
> I've already implemented logic in the template to auto-expand the
>> tree
>>> to
> the document for folks who have direct links.  So, if you do a Google
> Search and find the link to the MXML page, when you go to that page,
>>> the
> ToC will automatically look like:
> 
> Welcome
> --High Level View
> --Features
> AS3
> ---*MXML*
> Get Started
> 
> 
> 
> If you hit the main doc page, the ToC starts out collapsed so that
>> Get
> Started isn't pushed down by a bunch of Welcome sub-topics.  So the
>> ToC
> initially looks like:
> 
> Welcome
> Get Started
> 
> Now let's say you expand both Welcome and Get Started so you see:
> 
> Welcome
> --High Level View
> --Features
> Get Started
> --Download
> --Hello World
> 
> Then you click on Features.  The logic that opens trees to direct
>> links
 is
> going to cause the ToC to look like:
> 
> 
> Welcome
> --High Level View
> --Features
> Get Started
> 
> Even though you had expanded "Get Started" it will collapse when
>> going
>>> to
> the Features page.  That's because, without frames, each page is its
>>> own
> HTML page.  No state about 

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

[OmPrakash Muppirala]

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:
https://bigosmallm.gitbooks.io/royale-docs-test2/content/v/develop/Create%20An%20Application.html

The advantages I see using this tool are:

* Seems to be a widely used tool for documentation these days.  NPMjs.org,
React, Redux, etc. use Gitbook
* Two way sync between github and gitbook app.  That is, you can create an
.md file on github and see it on gitbook.  You can also create more content
using the WYSIWYG editor on Gitbook, which will be synced to the github
repo.
* Seems pretty straightforward to create a TOC.  It includes support for
tree structure by default
* We can choose to use the web app on gitbook.com or use the open
source(Apache V2 licensed | https://github.com/GitbookIO/gitbook) command
line tool.  The CLI will help us integrate with our Jenkins build for
example.
* Allows users to provide feedback on the site itself
* Allows us to point the docs site to our custom domain address


If there is more interest in trying this out, I can set up an Organization
account (free) and add users as needed.

Thanks,
Om

On Sun, Jan 28, 2018 at 2:53 AM, Andrew Wetmore  wrote:

> 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 ToC fit the information, not the other way around.
>
> On Sun, Jan 28, 2018 at 5:56 AM, Carlos Rovira 
> wrote:
>
> > 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
> reference.
> >
> > For states. I think the trick here is that a .md page has some variables
> > that will make the right top level branch open in TOC and as well make
> the
> > right sub option appears as selected (strong type) and without link. As
> we
> > are dealing with static GitHub pages I think there's no concept of
> > component, only that all pages has the TOC added to the sidebar.
> >
> >
> >
> > 2018-01-27 1:18 GMT+01:00 Andrew Wetmore :
> >
> > > What you describe sounds fine to me. I don't think we need to worry
> about
> > > breadcrumbs and state and helping people go backwards through their
> > series
> > > of clicks.
> > >
> > > On Fri, Jan 26, 2018 at 8:09 PM, Alex Harui 
> > > wrote:
> > >
> > > > Breaking out a separate thread on this...
> > > >
> > > > Thinking about this some more, I think I can generate an interactive
> > > > control with Jekyll, but I don't know how to make it retain state.  I
> > > > think that might require cookies and/or frames.
> > > >
> > > > For example, let's say the TOC looked like:
> > > >
> > > > Welcome
> > > > --High Level View
> > > > --Features
> > > > AS3
> > > > MXML
> > > > Get Started
> > > > --Download
> > > > --Hello World
> > > >
> > > > I've already implemented logic in the template to auto-expand the
> tree
> > to
> > > > the document for folks who have direct links.  So, if you do a Google
> > > > Search and find the link to the MXML page, when you go to that page,
> > the
> > > > ToC will automatically look like:
> > > >
> > > > Welcome
> > > > --High Level View
> > > > --Features
> > > > AS3
> > > > ---*MXML*
> > > > Get Started
> > > >
> > > >
> > > >
> > > > If you hit the main doc page, the ToC starts out collapsed so that
> Get
> > > > Started isn't pushed down by a bunch of Welcome sub-topics.  So the
> ToC
> > > > initially looks like:
> > > >
> > > > Welcome
> > > > Get Started
> > > >
> > > > Now let's say you expand both Welcome and Get Started so you see:
> > > >
> > > > Welcome
> > > > --High Level View
> > > > --Features
> > > > Get Started
> > > > --Download
> > > > --Hello World
> > > >
> > > > Then you click on Features.  The logic that opens trees to direct
> links
> > > is
> > > > going to cause the ToC to look like:
> > > >
> > > >
> > > > Welcome
> > > > --High Level View
> > > > --Features
> > > > Get Started
> > > >
> > > > Even though you had expanded "Get Started" it will collapse when
> going
> > to
> > > > the Features page.  That's because, without frames, each page is its
> > own
> > > > HTML page.  No state about the ToC is retained or shared.
> > > >
> > > > If folks are ok with that, I can probably get that to work.
> > > >
> > > > Thoughts?
> > > > -Alex
> > > >
> > > --
> > > Andrew Wetmore
> > >
> > > http://cottage14.blogspot.com/
> 

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

[Andrew Wetmore]

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 ToC fit the information, not the other way around.

On Sun, Jan 28, 2018 at 5:56 AM, Carlos Rovira 
wrote:

> 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 reference.
>
> For states. I think the trick here is that a .md page has some variables
> that will make the right top level branch open in TOC and as well make the
> right sub option appears as selected (strong type) and without link. As we
> are dealing with static GitHub pages I think there's no concept of
> component, only that all pages has the TOC added to the sidebar.
>
>
>
> 2018-01-27 1:18 GMT+01:00 Andrew Wetmore :
>
> > What you describe sounds fine to me. I don't think we need to worry about
> > breadcrumbs and state and helping people go backwards through their
> series
> > of clicks.
> >
> > On Fri, Jan 26, 2018 at 8:09 PM, Alex Harui 
> > wrote:
> >
> > > Breaking out a separate thread on this...
> > >
> > > Thinking about this some more, I think I can generate an interactive
> > > control with Jekyll, but I don't know how to make it retain state.  I
> > > think that might require cookies and/or frames.
> > >
> > > For example, let's say the TOC looked like:
> > >
> > > Welcome
> > > --High Level View
> > > --Features
> > > AS3
> > > MXML
> > > Get Started
> > > --Download
> > > --Hello World
> > >
> > > I've already implemented logic in the template to auto-expand the tree
> to
> > > the document for folks who have direct links.  So, if you do a Google
> > > Search and find the link to the MXML page, when you go to that page,
> the
> > > ToC will automatically look like:
> > >
> > > Welcome
> > > --High Level View
> > > --Features
> > > AS3
> > > ---*MXML*
> > > Get Started
> > >
> > >
> > >
> > > If you hit the main doc page, the ToC starts out collapsed so that Get
> > > Started isn't pushed down by a bunch of Welcome sub-topics.  So the ToC
> > > initially looks like:
> > >
> > > Welcome
> > > Get Started
> > >
> > > Now let's say you expand both Welcome and Get Started so you see:
> > >
> > > Welcome
> > > --High Level View
> > > --Features
> > > Get Started
> > > --Download
> > > --Hello World
> > >
> > > Then you click on Features.  The logic that opens trees to direct links
> > is
> > > going to cause the ToC to look like:
> > >
> > >
> > > Welcome
> > > --High Level View
> > > --Features
> > > Get Started
> > >
> > > Even though you had expanded "Get Started" it will collapse when going
> to
> > > the Features page.  That's because, without frames, each page is its
> own
> > > HTML page.  No state about the ToC is retained or shared.
> > >
> > > If folks are ok with that, I can probably get that to work.
> > >
> > > Thoughts?
> > > -Alex
> > >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/
> >
> >
> >
> >
> >
> >  > source=link_campaign=sig-email_content=webmail>
> > Virus-free.
> > www.avast.com
> >  > source=link_campaign=sig-email_content=webmail>
> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >
>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>



-- 
Andrew Wetmore

http://cottage14.blogspot.com/

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

[Carlos Rovira]

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 :

> Alex:
>
> A suggestion for improving the opening sentence:
> The Apache Royale project is a continuation of the previous effort called
> FlexJS to produce a next-generation of the Apache Flex SDK that...
>
>
> On 1/25/2018 12:51 AM, Alex Harui wrote:
>
>> Apache Royale is a new project that took over the work on what was being
>> called FlexJS, a next-generation of the Apache Flex SDK that enables
>> developers to use MXML and ActionScript to generated HTML/JS/CSS so
>> applications can run natively in browsers.  The cross-compiled code can
>> also be used in Apache Cordova (Adobe PhoneGap) mobile applications.
>>
>
> --
> Jason Guild
> Analyst/Programmer V
> State of Alaska - Department of Transportation & Public Facilities
> Information Systems and Services Division
> 820 E. 15th Ave.
> Anchorage, Alaska 99501
>
>


-- 
Carlos Rovira
http://about.me/carlosrovira

Re: Royale Documentation Page Layout Proposal

[Carlos Rovira]

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 follow this, and configure our _config.yml with the
published result.

Before changing more in the page doc example I did in WP, I think we should
follow this steps and try to make a theme with that and see the results.

Carlos



2018-01-28 8:02 GMT+01:00 Alex Harui :

>
>
> On 1/27/18, 10:37 AM, "Gabe Harbs"  wrote:
>
> >Nice direction. I wonder if it makes sense to start with a Jekyll theme
> >such as the Jekyll-doc-theme[1] and build off of that.
>
> IMO, no.  I just don't want to spend time chasing down the IP of all of
> the bits of these themes.  They may say they are MIT, but who knows about
> some font or css they've borrowed from somewhere.  I think I've done a
> pretty good replication of the Royale Website header and footer.  If we
> can agree on what Carlos proposes or my suggested changes to it, I think I
> can have it ready in a couple of hours and then we can just produce
> content instead of providing more surface for IP nitpickers.  I keep
> hoping we will find a simple HTML implementation of what we want so we can
> replicate parts of it across all of our web pages, from royale.a.o to
> royale-docs to asdoc and the TryItNow app.  If we keep using different
> themes, we have to try to reproduce the commonality in each of those
> themes.
>
> >The theme I linked to has the advantage of offering simple blogging
> >capabilities as well.
>
> Jekyll was designed for blogs.  Again, I think I can take a proposal from
> Carlos and get it working in a couple of hours.
>
> Keep it simple.  Less process, more content.  We can get fancy later.
>
> My 2 cents,
> -Alex
>
>


-- 
Carlos Rovira
http://about.me/carlosrovira

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

[Carlos Rovira]

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 reference.

For states. I think the trick here is that a .md page has some variables
that will make the right top level branch open in TOC and as well make the
right sub option appears as selected (strong type) and without link. As we
are dealing with static GitHub pages I think there's no concept of
component, only that all pages has the TOC added to the sidebar.



2018-01-27 1:18 GMT+01:00 Andrew Wetmore :

> What you describe sounds fine to me. I don't think we need to worry about
> breadcrumbs and state and helping people go backwards through their series
> of clicks.
>
> On Fri, Jan 26, 2018 at 8:09 PM, Alex Harui 
> wrote:
>
> > Breaking out a separate thread on this...
> >
> > Thinking about this some more, I think I can generate an interactive
> > control with Jekyll, but I don't know how to make it retain state.  I
> > think that might require cookies and/or frames.
> >
> > For example, let's say the TOC looked like:
> >
> > Welcome
> > --High Level View
> > --Features
> > AS3
> > MXML
> > Get Started
> > --Download
> > --Hello World
> >
> > I've already implemented logic in the template to auto-expand the tree to
> > the document for folks who have direct links.  So, if you do a Google
> > Search and find the link to the MXML page, when you go to that page, the
> > ToC will automatically look like:
> >
> > Welcome
> > --High Level View
> > --Features
> > AS3
> > ---*MXML*
> > Get Started
> >
> >
> >
> > If you hit the main doc page, the ToC starts out collapsed so that Get
> > Started isn't pushed down by a bunch of Welcome sub-topics.  So the ToC
> > initially looks like:
> >
> > Welcome
> > Get Started
> >
> > Now let's say you expand both Welcome and Get Started so you see:
> >
> > Welcome
> > --High Level View
> > --Features
> > Get Started
> > --Download
> > --Hello World
> >
> > Then you click on Features.  The logic that opens trees to direct links
> is
> > going to cause the ToC to look like:
> >
> >
> > Welcome
> > --High Level View
> > --Features
> > Get Started
> >
> > Even though you had expanded "Get Started" it will collapse when going to
> > the Features page.  That's because, without frames, each page is its own
> > HTML page.  No state about the ToC is retained or shared.
> >
> > If folks are ok with that, I can probably get that to work.
> >
> > Thoughts?
> > -Alex
> >
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>
>
>
>
>
>  source=link_campaign=sig-email_content=webmail>
> Virus-free.
> www.avast.com
>  source=link_campaign=sig-email_content=webmail>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>



-- 
Carlos Rovira
http://about.me/carlosrovira