Give others to look into that! :)

Thanks! Piotr

2017-11-19 20:44 GMT+01:00 Carlos Rovira <[email protected]>:

> Ok Piotr,
> I'll ok, I'll modify that in short.
> Thanks! :)
>
> 2017-11-19 19:09 GMT+01:00 Piotr Zarzycki <[email protected]>:
>
> > Hi Carlos,
> >
> > This solution with link to wiki is really good :) I have only one
> comment:
> > "We are working on other possible outputs like WebAssembly or SWF" - I
> > think we should not mention SWF here, cause compiler is able to do output
> > to SWF, it's ready. No one is working on that, rather on the framework
> > sight someone can work from the UI perspective on SWF output.
> >
> > Thanks, Piotr
> >
> >
> > 2017-11-19 18:43 GMT+01:00 Carlos Rovira <[email protected]>:
> >
> > > Hi,
> > >
> > > just end Source Code page:
> > >
> > > http://royale.codeoscopic.com/source-code/
> > >
> > > Here I only mention the 3 repos that I consider are of interest for
> > Royale
> > > users. I'm talking about compiler, typedefs and framework.
> > >
> > > The other three are website, docs and tourjs. I thought about those
> repos
> > > and:
> > >
> > > * website is nothing we release, so no point in make it relevant in a
> > > marketing web, since it even will have a negative point of introduce
> > noise,
> > > and that should avoided.
> > > * docs: The documentation, wiki and other resources are of use to
> consume
> > > web, make accesible through the website, be available in GitHub, and
> the
> > > rest. If people wants to contribute, they will be entering the royale
> > world
> > > as a developer and will end having knowledge, and conversations with
> us.
> > So
> > > they will end knowing about Royale-docs repo.
> > > * tourjs: is the only one I think is interesting to post in this page,
> > but
> > > I think it currently is not developed, so at this time, we should avoid
> > to
> > > post things that are not in an usable form. We can get back to this at
> a
> > > later time.
> > >
> > > Finaly, other way to make people go directly to source code is in the
> > menu
> > > through the GitHub menu item as many other projects out there does. The
> > > difference is that we have several repos and other projects only has
> one.
> > > So we need some "index" page.
> > >
> > > I put temporarily the following link as I was looking for some GitHub
> > > "project" page, but that does not exist in GitHub:
> > >
> > > https://github.com/search?utf8=%E2%9C%93&q=apache+royale&type=
> > >
> > > The problem here is that a search shows the official Apache Royale
> repos,
> > > but as well others could enter in the list (like Piotr repo).
> > >
> > > So I created a similar one in our wiki to make the entry point from our
> > web
> > > to GitHub :
> > >
> > > https://github.com/apache/royale-asjs/wiki/Apache-Royale-Source-Code-
> > > Repositories
> > >
> > > And this is the page I linked in the main Github menu item in the
> website
> > > and in the footer menu
> > >
> > >
> > > Let me know whatever point you want to consider here.
> > >
> > > Thanks
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>



-- 

Piotr Zarzycki

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

Reply via email to