On Mon, Jan 29, 2018 at 1:11 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com> wrote:
> Om, > > Does that install our release or Nightly ? > The release version, i.e. 0.9.0. > > > 2018-01-29 22:09 GMT+01:00 OmPrakash Muppirala <bigosma...@gmail.com>: > > > On Mon, Jan 29, 2018 at 1:06 PM, Andrew Wetmore <cottag...@gmail.com> > > wrote: > > > > > What about text like this for the download page on the website? > > > === > > > > > > The current version of Apache Royale is 0.9.0, released in January, > 2018. > > > It is beta-quality. This means that Royale may not work entirely as you > > or > > > we want it to, and that certain “standard” components or functions are > > not > > > yet available. However, you can create applications in Royale and > compile > > > them to run either in a browser window or on the Flash/AIR platforms. > > > > > > *Download *the compiled (binary) version of Royale from one of the > Apache > > > mirror sites: > > > > > > To create JavaScript applications only: > > > 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 > > > > > > To create JavaScript or Flash applications: > > > 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 > > > > > > Copy the contents of the download into a directory on your computer, > then > > > connect it to the IDE you are using. > > > > > > > > > *NPM*: > > > > > > If you use npm, [WHAT GOES HERE?] > > > > > > > > npm install @apache-royale/royale-js -g > > npm install @apache-royale/royale-js-swf -g > > > > Thanks, > > Om > > > > > > > > > > === > > > > > > > > > > > > On Mon, Jan 29, 2018 at 4:16 PM, Alex Harui <aha...@adobe.com.invalid> > > > wrote: > > > > > > > > > > > > > > > On 1/29/18, 10:43 AM, "Andrew Wetmore" <cottag...@gmail.com> wrote: > > > > > > > > >I as a reader would want to see a summary of what is in the release, > > > where > > > > >and how to get it, and what to do with it once I have it. The same > > > > >information would go into the appropriate pages in the help docs. I > > can > > > do > > > > >a rough cut based on what I see in the README files, unless somebody > > > with > > > > >more knowledge wants to do the first draft. > > > > > > > > Go for it. I don't have time for that today. > > > > > > > > > >On that front, here is a naive reader's question: I see lots of > > > > >instructions in the README about compiling Royale, as if that were > > > > >something I would always have to do. Then, almost as a throw-away, I > > see > > > > >notes about the already-compiled binaries. Does EVERYBODY download > and > > > > >build Royale for themselves? I would have thought your average > > > app-builder > > > > >would start with the compiled binaries and just want to know how to > > > > >reference them from the IDE of choice. > > > > > > > > Apache is very source-code oriented since it is about Open Source. > In > > > > fact, to Apache, the binaries are not official releases, just > > convenience > > > > artifacts. So websites, readme's and lots of other things are > supposed > > > to > > > > be about working from the source code. > > > > > > > > We could put a different README in the binary artifacts. I just > don't > > > > know how many people will read it instead of the "Get Started" we put > > on > > > > the docs page soon. > > > > > > > > HTH, > > > > -Alex > > > > > > > > > > > > > > > > > -- > > > Andrew Wetmore > > > > > > http://cottage14.blogspot.com/ > > > > > > > > > -- > > Piotr Zarzycki > > Patreon: *https://www.patreon.com/piotrzarzycki > <https://www.patreon.com/piotrzarzycki>* >
