On Mon, Jan 29, 2018 at 11:00 PM, Alex Harui <aha...@adobe.com.invalid>
wrote:

> Hi Om,
>
> I ran the install.  I don't think the package.json is the one from the
> released source artifact, so I think we might need to call this a nightly.
>  But it does seem to work!
>

Cool, thanks for testing.  Yes, as I mentioned in this thread [1], I had a
modify the package.json and a couple of .js files that deal with
downloading the dependencies.
But the Royale SDK part is exactly the same.  Since the NPM release is not
an official Apache release, it is okay for us to claim that this is Apache
Royale v0.9.0.


[1]
https://lists.apache.org/thread.html/a610c585f6d3d35f1be742d8cf66b160c27e7a3f5db6dbdab59c59ab@%3Cdev.royale.apache.org%3E


>
> Thanks for figuring something out so folks don't have to use URLs.  One
> question though:  Is having folks use @apache-royale/royale-js better than
> some day having folks use just apache-royale-js or might we switch to
> apache-royale-js some day?  I've never seen the @org/package before, but I
> don't use NPM much, so I don't know what folks expect.
>

It will be better for us as an organization if we maintain scoped releases
instead of one offs.  I see this trend in other projects as well.  For
example, the latest Angular code is available under the @angular org:
https://www.npmjs.com/~angular.  Vue is available under @vue:
https://www.npmjs.com/org/vue

This approach would also protect us from outsiders taking up package names
that might cause confusion with our packages.  Only we can deploy packages
under the @apache-royale namespace going forward.

Thanks,
Om


>
> Thanks,
> -Alex
>
> On 1/29/18, 1:14 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
> <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote:
>
> >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:
> >> > >
> >>https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.apach
> >>e.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.0%2F&data=02%
> 7C01%7Caharui%40adob
> >>e.com%7Cafc6683ae225455b441f08d5675d51cb%7Cfa7b1b5a7b34438794aed2c178de
> ce
> >>e1%7C0%7C0%7C636528572861041185&sdata=W6vjxZJ2Iy3XuHc5Z8VjaeDAtxVRxX
> 6GWha
> >>eoI2BeFc%3D&reserved=0
> >> > > binaries/apache-royale-0.9.0-bin-js.tar.gz
> >> > >
> >>https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.apach
> >>e.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.0%2F&data=02%
> 7C01%7Caharui%40adob
> >>e.com%7Cafc6683ae225455b441f08d5675d51cb%7Cfa7b1b5a7b34438794aed2c178de
> ce
> >>e1%7C0%7C0%7C636528572861041185&sdata=W6vjxZJ2Iy3XuHc5Z8VjaeDAtxVRxX
> 6GWha
> >>eoI2BeFc%3D&reserved=0
> >> > > binaries/apache-royale-0.9.0-bin-js.zip
> >> > >
> >> > > To create JavaScript or Flash applications:
> >> > >
> >>https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.apach
> >>e.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.0%2F&data=02%
> 7C01%7Caharui%40adob
> >>e.com%7Cafc6683ae225455b441f08d5675d51cb%7Cfa7b1b5a7b34438794aed2c178de
> ce
> >>e1%7C0%7C0%7C636528572861041185&sdata=W6vjxZJ2Iy3XuHc5Z8VjaeDAtxVRxX
> 6GWha
> >>eoI2BeFc%3D&reserved=0
> >> > > binaries/apache-royale-0.9.0-bin-js-swf.tar.gz
> >> > >
> >>https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.apach
> >>e.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.0%2F&data=02%
> 7C01%7Caharui%40adob
> >>e.com%7Cafc6683ae225455b441f08d5675d51cb%7Cfa7b1b5a7b34438794aed2c178de
> ce
> >>e1%7C0%7C0%7C636528572861041185&sdata=W6vjxZJ2Iy3XuHc5Z8VjaeDAtxVRxX
> 6GWha
> >>eoI2BeFc%3D&reserved=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
> >> > >
> >> > >
> >>https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fcottage14
> >>.blogspot.com%2F&data=02%7C01%7Caharui%40adobe.com%
> 7Cafc6683ae225455b441f
> >>08d5675d51cb%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636528572861041
> >>185&sdata=%2B%2BAvR137jJhvhbm6RrGkAfx9jjSos5
> E2qB%2BdYwMC2rY%3D&reserved=0
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >>
> >> Piotr Zarzycki
> >>
> >> Patreon:
> >>*https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fwww.pat
> >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com
> %7Cafc6683ae225
> >>455b441f08d5675d51cb%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6365285
> >>72861041185&sdata=BP%2BMJ%2BTIaNNhBuMLgVEWy1CvWQqSTaMYif
> 8ywdaitYk%3D&rese
> >>rved=0
> >>
> >><https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fwww.pat
> >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com
> %7Cafc6683ae225
> >>455b441f08d5675d51cb%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6365285
> >>72861041185&sdata=BP%2BMJ%2BTIaNNhBuMLgVEWy1CvWQqSTaMYif
> 8ywdaitYk%3D&rese
> >>rved=0>*
> >>
>
>

Reply via email to