Re: Help docs ToC and links

[Alex Harui]

OK, I figured out how to generate the ToC from a JSON file
(_data/toc.json).  Basically, it is a hierarchical structure.  Each ToC
entry is a JSON Object with a path property and an optional children array
of other ToC entries.

The title and links are pulled from the site information gathered by
Jekyll, so you won't see ToC entries on the page for entries in the
toc.json that don't have an actual file.  Which also means that if you
don't match the path to the actual file name it won't show either.  Make
sure you have your capital letters and everything correct.

I also figured you were asleep at this hour so I did the license sweep.
Make sure you sync up any local working copies before making more changes.

On 1/25/18, 6:51 PM, "Alex Harui"  wrote:

>OK, I saw your other email about more ToC changes coming.  I think I am
>going to try to generate the ToC.
>
>-Alex
>
>On 1/25/18, 6:32 PM, "Alex Harui"  wrote:
>
>>On 1/25/18, 4:11 PM, "Andrew Wetmore"  wrote:
>>
>>>Hi:
>>>
>>>I have not been touching the ToC file because it looks very easy to get
>>>wrong. 
>>
>>Yeah, I was fiddling with the ToC and thinking the same thing.  I'm
>>wondering how many more changes to the ToC we'll be doing.  If it is just
>>a few more to implement your proposed ToC, we could just keep the current
>>way and fix the small things as we find it.  If we think we're going to
>>be
>>adding new entries and/or renaming entries, maybe it is worth it for me
>>to
>>try to spend a day making the ToC "generate" from the .MD files.  We
>>would
>>probably dictate the organization of the ToC in a JSON file, but the
>>entries would be less error prone.  Maybe like:
>>
>>{ "toc": [ "index.md" : [ "welcome/high-level-view.md" : [] ,
>>  "welcome/features-and-concepts.md": [
>>"welcome/features/as3.md" ...
>>   "get-started.md" : ["get-started/system-requirements.md" ...
>>
>>Essentially, a hierarchical object that just lists the file names in the
>>order you want them to appear in the ToC.  I think I can get Jekyll to
>>generate the ToC by using the page titles.
>>
>>
>>
>>>I have also not been inserting links from one .md page to another
>>>because I am not clear whether we are using relative or absolute links
>>>(not
>>>sure, for instance, whether there is a performance benefit of one over
>>>the
>>>other...).
>>
>>In the .md files, links have to be a full path without the leading slash.
>>So to link to /welcome/features/as3.md, you would use
>>
>>  [as3](welcome/features/as3.html)
>>
>>>
>>>Also, when we link out from the help docs to another section of the
>>>Royale
>>>site, or any other resource, we should pop a new browser window, not
>>>take
>>>the reader away from the help docs. Is there a standard way to declare
>>>that
>>>when writing a link in markdown? Is it the same as in HTML
>>>("target=_blank")?
>>
>>I had to look it up.  The syntax is:
>>
>>>[as3](welcome/features/as3.html){:target='_blank'}
>>
>>I just modified index.md and tested it and it seemed to work.
>>
>>-Alex
>>
>

Re: Help docs ToC and links

[Alex Harui]

OK, I saw your other email about more ToC changes coming.  I think I am
going to try to generate the ToC.

-Alex

On 1/25/18, 6:32 PM, "Alex Harui"  wrote:

>On 1/25/18, 4:11 PM, "Andrew Wetmore"  wrote:
>
>>Hi:
>>
>>I have not been touching the ToC file because it looks very easy to get
>>wrong. 
>
>Yeah, I was fiddling with the ToC and thinking the same thing.  I'm
>wondering how many more changes to the ToC we'll be doing.  If it is just
>a few more to implement your proposed ToC, we could just keep the current
>way and fix the small things as we find it.  If we think we're going to be
>adding new entries and/or renaming entries, maybe it is worth it for me to
>try to spend a day making the ToC "generate" from the .MD files.  We would
>probably dictate the organization of the ToC in a JSON file, but the
>entries would be less error prone.  Maybe like:
>
>{ "toc": [ "index.md" : [ "welcome/high-level-view.md" : [] ,
>  "welcome/features-and-concepts.md": [
>"welcome/features/as3.md" ...
>   "get-started.md" : ["get-started/system-requirements.md" ...
>
>Essentially, a hierarchical object that just lists the file names in the
>order you want them to appear in the ToC.  I think I can get Jekyll to
>generate the ToC by using the page titles.
>
>
>
>>I have also not been inserting links from one .md page to another
>>because I am not clear whether we are using relative or absolute links
>>(not
>>sure, for instance, whether there is a performance benefit of one over
>>the
>>other...).
>
>In the .md files, links have to be a full path without the leading slash.
>So to link to /welcome/features/as3.md, you would use
>
>  [as3](welcome/features/as3.html)
>
>>
>>Also, when we link out from the help docs to another section of the
>>Royale
>>site, or any other resource, we should pop a new browser window, not take
>>the reader away from the help docs. Is there a standard way to declare
>>that
>>when writing a link in markdown? Is it the same as in HTML
>>("target=_blank")?
>
>I had to look it up.  The syntax is:
>
>>[as3](welcome/features/as3.html){:target='_blank'}
>
>I just modified index.md and tested it and it seemed to work.
>
>-Alex
>

Re: Help docs ToC and links

[Alex Harui]

On 1/25/18, 4:11 PM, "Andrew Wetmore"  wrote:

>Hi:
>
>I have not been touching the ToC file because it looks very easy to get
>wrong. 

Yeah, I was fiddling with the ToC and thinking the same thing.  I'm
wondering how many more changes to the ToC we'll be doing.  If it is just
a few more to implement your proposed ToC, we could just keep the current
way and fix the small things as we find it.  If we think we're going to be
adding new entries and/or renaming entries, maybe it is worth it for me to
try to spend a day making the ToC "generate" from the .MD files.  We would
probably dictate the organization of the ToC in a JSON file, but the
entries would be less error prone.  Maybe like:

{ "toc": [ "index.md" : [ "welcome/high-level-view.md" : [] ,
  "welcome/features-and-concepts.md": [
"welcome/features/as3.md" ...
   "get-started.md" : ["get-started/system-requirements.md" ...

Essentially, a hierarchical object that just lists the file names in the
order you want them to appear in the ToC.  I think I can get Jekyll to
generate the ToC by using the page titles.



>I have also not been inserting links from one .md page to another
>because I am not clear whether we are using relative or absolute links
>(not
>sure, for instance, whether there is a performance benefit of one over the
>other...).

In the .md files, links have to be a full path without the leading slash.
So to link to /welcome/features/as3.md, you would use

  [as3](welcome/features/as3.html)

>
>Also, when we link out from the help docs to another section of the Royale
>site, or any other resource, we should pop a new browser window, not take
>the reader away from the help docs. Is there a standard way to declare
>that
>when writing a link in markdown? Is it the same as in HTML
>("target=_blank")?

I had to look it up.  The syntax is:

>[as3](welcome/features/as3.html){:target='_blank'}

I just modified index.md and tested it and it seemed to work.

-Alex

Re: Proposed table of contents for Royale help documentation

[Alex Harui]

Hi Carlos,

I don't know how big the changes you are thinking of and how much time you
have, but you could mock up something in your WP instance or post an image
and I could try to make the changes in the current template.

Let me know,
-Alex

On 1/25/18, 4:17 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>Hi Alex,
>
>getting up with the last day info. Right, I'll try this week-end to make
>something that looks good. First I have to figure how to work taking into
>account the other threads I read and the way you guys are working.
>Thanks
>
>2018-01-25 0:23 GMT+01:00 Alex Harui :
>
>> MIT is fine, as is BSD.  But again, if the theme has many parts, it may
>> result in the PMC spending time researching each of the parts.  Just
>> because the theme author claims MIT for his work, he might have used
>> third-party works under other licenses that aren't as compatible with
>>the
>> Apache License.
>>
>> I guess my question is this:  I don't expect that the look-and-feel of
>>our
>> documentation pages needs much if any animation.  IOW, I would think the
>> visuals around the content will be pretty much static.  If that's the
>> case, why will it be so difficult to just continue improving the
>>template
>> I put in there?  If you want to take a theme and WP and mock up
>>something
>> quickly, that's fine as long as all of the creativity can be considered
>> yours or under a friendly license.  But maybe instead of another export
>>of
>> a WP theme, we should just try to mimic that in plain HTML.  I think I
>>got
>> pretty close to the royale.a.o look in the docpage.html template.
>>
>> Thoughts?
>> -Alex
>>
>> On 1/24/18, 1:57 PM, "carlos.rov...@gmail.com on behalf of Carlos
>>Rovira"
>>  wrote:
>>
>> >Hi Alex,
>> >
>> >right, I'm looking for something that is ALv2. Unfortunately almost all
>> >docs themes are MIT license. Is MIT right for us?
>> >
>> >2018-01-24 18:14 GMT+01:00 Alex Harui :
>> >
>> >> Hi Carlos,
>> >>
>> >> Right now, the master branch is set up to use the Cayman theme.
>>When I
>> >> took a quick look at Cayman, it appeared to be under Creative
>>Commons,
>> >> which makes it very difficult for us to use.  Unfortunately, just
>> >>because
>> >> it is "Open Source" and on GitHub doesn't mean it is compatible with
>>the
>> >> Apache License.  That was one reason I put in a docpage.html as the
>> >> initial template for the doc site.  If you can find a simple theme
>>that
>> >> isn't under CC, then let's take a look at it, but every third party
>> >>theme
>> >> seems to have lots of pieces and is going to have to get scrubbed
>>which
>> >> takes us time thinking about legal stuff.  I believe we can
>> >>incrementally
>> >> add to the initial template or make different templates over time and
>> >>make
>> >> a first-class doc site without having to spend so much time scrubbing
>> >> other people's works.  I don't think people are going to care too
>>much
>> >> about how cool our doc site is, at least not right now.  I don't
>>think
>> >> there is a rush to make it cool.  On the other hand, we do want to
>>make
>> >>a
>> >> good first impression over at royale.a.o, which is why I'm glad you
>>have
>> >> provided something great for that.
>> >>
>> >> My 2 cents,
>> >> -Alex
>> >>
>> >> On 1/24/18, 12:45 AM, "carlos.rov...@gmail.com on behalf of Carlos
>> >>Rovira"
>> >>  wrote:
>> >>
>> >> >Hi Alex, for this reason is better to go with a OS GitHub theme that
>> >>only
>> >> >needs to use the colors, fonts and logos from our website. Those
>>where
>> >> >selected by me and are not provided by the WP theme. The other main
>> >>reason
>> >> >is that we need to use something done for that task with the maximum
>> >> >quality. And that is something we can develop ourselves from scratch
>> >> >without invest lots of time.
>> >> >
>> >> >2018-01-24 5:10 GMT+01:00 Alex Harui :
>> >> >
>> >> >> Personally, I would be very cautious about WP themes or copying
>> >> >> look-and-feel of other sites.  I would like our doc to be
>> >>license-able
>> >> >> under ALv2 and not run into IP and licensing issues.
>> >> >>
>> >> >> -Alex
>> >> >>
>> >> >> On 1/23/18, 3:11 PM, "carlos.rov...@gmail.com on behalf of Carlos
>> >> >>Rovira"
>> >> >> 
>> wrote:
>> >> >>
>> >> >> >Hi,
>> >> >> >
>> >> >> >I tried to read through this thread, but many mails to catch all
>> >>whats
>> >> >> >happening at the moment, and just want to say a couple of things:
>> >> >> >
>> >> >> >1.- Regarding TOC, I think it's ok (in a quick review, I should
>> >>work a
>> >> >>bit
>> >> >> >on docs too to see how this works). But as anything, I assume
>>that
>> >> >>it's a
>> >> >> >starting point and we 

Re: YouTube channel

[Dave Fisher]

Hi -

The current set of channels is related mostly to Apachecon and is owned by 
press@. Let’s wait to see what Sally has to say.

Regards,
Dave

Sent from my iPhone

> On Jan 25, 2018, at 1:54 PM, Carlos Rovira  
> wrote:
> 
> Hi,
> 
> I think this is a wonderful idea. I think youtube is nowadays a great way
> to learn things, so a great way to learn about how to use Apache Royale.
> 
> So big +1! :)
> 
> 2018-01-25 20:06 GMT+01:00 Dave Fisher :
> 
>> Hi -
>> 
>> Does the Com Dev team know if there is an ASF YouTube channel that
>> projects can use?
>> 
>> Note this email is crossposted with dev@royale.
>> 
>> I’ve asked privately at fundraising@
>> 
>> Regards,
>> Dave
>> 
>>> On Jan 25, 2018, at 10:43 AM, Andrew Wetmore 
>> wrote:
>>> 
>>> Having a unified ASF channel would also be a good option. It could be a
>>> much more lively channel than what any individual Apache project could
>>> support.
>>> 
 On Jan 25, 2018 2:39 PM, "Dave Fisher"  wrote:
 
 Hi Andrew,
 
 That’s interesting. Since there is a donate button available I am going
>> to
 ask the Fundraising committee. Stay tuned.
 
 Regards,
 Dave
 
> On Jan 25, 2018, at 9:50 AM, Andrew Wetmore 
>> wrote:
> 
> Hi, Dave.
> 
> My first step was to find out if such a channel already existed. I
>> gather
> it does not. I can either set one up under my own ID or go through the
> "Google for Nonprofits" path[1] to see if they will let us set up a
 channel
> for an ASF project rather than for ASF as a unit
> 
> a
> 
> [1]
> https://www.google.com/nonprofits/products/youtube-
 nonprofit-program.html
> 
> On Thu, Jan 25, 2018 at 1:34 PM, Dave Fisher 
 wrote:
> 
>> Hi Andrew,
>> 
>> Great idea. Just make sure you share the details including access
>> information with the PMC by sending an email to
 priv...@royale.apache.org
>> 
>> Regards,
>> Dave
>> 
>> On Jan 25, 2018, at 8:34 AM, Andrew Wetmore 
 wrote:
>> 
>> Hi:
>> 
>> Does the project have a YouTube channel? I am thinking that, once we
 have
>> some apps to showcase (including the existing ones), I could create a
>> little video tour of each app, pointing out how it works and what
>> Royale
>> lets you do to make it happen. We can then embed one or more videos in
 the
>> website as, oooh, eye candy.
>> 
>> The app creator can do the script and narration, or I can do that for
 them
>> and assemble the video. Each one of these things would run for two or
 three
>> minutes.
>> 
>> --
>> Andrew Wetmore
>> 
>> http://cottage14.blogspot.com/
>> 
>> 
>> 
> 
> 
> --
> Andrew Wetmore
> 
> http://cottage14.blogspot.com/
 
 
>> 
>> 
> 
> 
> -- 
> 
> 
> 
> Carlos Rovira
> 
> Director General
> 
> M: +34 607 22 60 05
> 
> http://www.codeoscopic.com
> 
> 
> Conócenos en 1 minuto! 
> 
> 
> Este mensaje se dirige exclusivamente a su destinatario y puede contener
> información privilegiada o confidencial. Si ha recibido este mensaje por
> error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
> proceda a su destrucción.
> 
> De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
> que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
> S.A. La finalidad de dicho tratamiento es facilitar la prestación del
> servicio o información solicitados, teniendo usted derecho de acceso,
> rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
> oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
> necesaria.

Re: Proposed table of contents for Royale help documentation

[Carlos Rovira]

Hi Alex,

getting up with the last day info. Right, I'll try this week-end to make
something that looks good. First I have to figure how to work taking into
account the other threads I read and the way you guys are working.
Thanks

2018-01-25 0:23 GMT+01:00 Alex Harui :

> MIT is fine, as is BSD.  But again, if the theme has many parts, it may
> result in the PMC spending time researching each of the parts.  Just
> because the theme author claims MIT for his work, he might have used
> third-party works under other licenses that aren't as compatible with the
> Apache License.
>
> I guess my question is this:  I don't expect that the look-and-feel of our
> documentation pages needs much if any animation.  IOW, I would think the
> visuals around the content will be pretty much static.  If that's the
> case, why will it be so difficult to just continue improving the template
> I put in there?  If you want to take a theme and WP and mock up something
> quickly, that's fine as long as all of the creativity can be considered
> yours or under a friendly license.  But maybe instead of another export of
> a WP theme, we should just try to mimic that in plain HTML.  I think I got
> pretty close to the royale.a.o look in the docpage.html template.
>
> Thoughts?
> -Alex
>
> On 1/24/18, 1:57 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
>  wrote:
>
> >Hi Alex,
> >
> >right, I'm looking for something that is ALv2. Unfortunately almost all
> >docs themes are MIT license. Is MIT right for us?
> >
> >2018-01-24 18:14 GMT+01:00 Alex Harui :
> >
> >> Hi Carlos,
> >>
> >> Right now, the master branch is set up to use the Cayman theme.  When I
> >> took a quick look at Cayman, it appeared to be under Creative Commons,
> >> which makes it very difficult for us to use.  Unfortunately, just
> >>because
> >> it is "Open Source" and on GitHub doesn't mean it is compatible with the
> >> Apache License.  That was one reason I put in a docpage.html as the
> >> initial template for the doc site.  If you can find a simple theme that
> >> isn't under CC, then let's take a look at it, but every third party
> >>theme
> >> seems to have lots of pieces and is going to have to get scrubbed which
> >> takes us time thinking about legal stuff.  I believe we can
> >>incrementally
> >> add to the initial template or make different templates over time and
> >>make
> >> a first-class doc site without having to spend so much time scrubbing
> >> other people's works.  I don't think people are going to care too much
> >> about how cool our doc site is, at least not right now.  I don't think
> >> there is a rush to make it cool.  On the other hand, we do want to make
> >>a
> >> good first impression over at royale.a.o, which is why I'm glad you have
> >> provided something great for that.
> >>
> >> My 2 cents,
> >> -Alex
> >>
> >> On 1/24/18, 12:45 AM, "carlos.rov...@gmail.com on behalf of Carlos
> >>Rovira"
> >>  wrote:
> >>
> >> >Hi Alex, for this reason is better to go with a OS GitHub theme that
> >>only
> >> >needs to use the colors, fonts and logos from our website. Those where
> >> >selected by me and are not provided by the WP theme. The other main
> >>reason
> >> >is that we need to use something done for that task with the maximum
> >> >quality. And that is something we can develop ourselves from scratch
> >> >without invest lots of time.
> >> >
> >> >2018-01-24 5:10 GMT+01:00 Alex Harui :
> >> >
> >> >> Personally, I would be very cautious about WP themes or copying
> >> >> look-and-feel of other sites.  I would like our doc to be
> >>license-able
> >> >> under ALv2 and not run into IP and licensing issues.
> >> >>
> >> >> -Alex
> >> >>
> >> >> On 1/23/18, 3:11 PM, "carlos.rov...@gmail.com on behalf of Carlos
> >> >>Rovira"
> >> >> 
> wrote:
> >> >>
> >> >> >Hi,
> >> >> >
> >> >> >I tried to read through this thread, but many mails to catch all
> >>whats
> >> >> >happening at the moment, and just want to say a couple of things:
> >> >> >
> >> >> >1.- Regarding TOC, I think it's ok (in a quick review, I should
> >>work a
> >> >>bit
> >> >> >on docs too to see how this works). But as anything, I assume that
> >> >>it's a
> >> >> >starting point and we should be working on it a evolving it as we
> >> >> >experience it.
> >> >> >
> >> >> >2.- Although Flex doc is a good start I want to point as well to
> >> >>React[1]
> >> >> >and Angular[2] to compare with what we want to do to get/copy ideas
> >>on
> >> >>how
> >> >> >they are doing things and help to get same level of quality and/or
> >>even
> >> >> >improve over it. I use to always reference this two projects since
> >>are
> >> >>the
> >> >> >standard right now in any aspect and we should compare what we do
> >>with
> >> 

Help docs ToC and links

[Andrew Wetmore]

Hi:

I have not been touching the ToC file because it looks very easy to get
wrong. I have also not been inserting links from one .md page to another
because I am not clear whether we are using relative or absolute links (not
sure, for instance, whether there is a performance benefit of one over the
other...).

Also, when we link out from the help docs to another section of the Royale
site, or any other resource, we should pop a new browser window, not take
the reader away from the help docs. Is there a standard way to declare that
when writing a link in markdown? Is it the same as in HTML
("target=_blank")?

a

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Royale in 10 minutes (was Re: Proposed table of contents for Royale help documentation)

[Andrew Wetmore]

Hi:

I think the "Royale in 10 Minutes" goes where the ToC "Hello, World!" is in
the "Get Started" section. I saw the "Create an Application" section as
what you would turn to when you had gone through building a first little
application and decided, yes, maybe this Royale is the thing I need for
what I want to build.

I took the "application lifecycle" lineup from the old Adobe Flex help doc
structure [1] section "Application Architecture / Application development
phases". Of course, the under-the-hood tick-tock of what happens in a
Royale app when you run it is equally valuable, but different. Feel free to
use "Application Lifecycle" to describe what you want to write about, and
we can change the top title for my stack to something like "Application
development phases", as you suggest.

Each night I wake up at least once thinking something like, "Oh, I forgot
an entry for Events!" The ToC is far from complete!

I have added the info about the Apache header in README.md, which I take to
be the place where documentation contributors would look for guidance. Just
pick a time and let me know and I will be out of the way for your sweep
through the existing files. I am in Nova Scotia in Canada, four hours ahead
of you if you are on the West Coast.

a


[1] https://help.adobe.com/en_US/flex/using/index.html


On Thu, Jan 25, 2018 at 7:14 PM, Alex Harui 
wrote:

> Hi Andrew,
>
> So I just pushed more stubs for the Create An Application section.  As I
> was doing so, I started thinking that what you expect in that section is
> different from what I'm interested in working on.  It isn't that we don't
> need that section, but it appears that you want to address application
> development as a general topic, discussing the design phase, and
> maintenance phases, etc.
>
> What I want to write is a "Royale in 10 minutes".  Sort of a tutorial for
> building something more than a Hello World, and discuss some
> "under-the-hood" things like how the app starts up, how you know the app
> is ready, calling a web service, stuff like that.  If you agree we want
> such a thing, where would it go?
>
> Also, we have to be a bit careful about terminology.  The reason I
> initially thought that I would do the "Royale in 10 minutes" in the
> "Create an Application" section is because one subsection is titled
> "Application Lifecycle".  To me, that meant the under-the-hood lifecycle
> of an application like what its entry point is, what gets initialized
> first, etc.  I'm tempted to rename the current "Application Lifecycle" to
> "Application Development Phases" so I can use "Lifecycle" for the
> under-the-hood section.  Or is there a better name for how an application
> starts up?
>
> I'm going to go spend some time on ASDoc while we figure this out.
>
> Also, at some point, we should sweep through all of the files and add the
> Apache header to them.  I did it in "Create an Application.md" to make
> sure it didn't pollute the output.  I didn't do the sweep now since I
> didn't know if you have files under edit.  I'm not sure what hours you are
> working on this, so we should just pick a time where we have everything
> committed and do a sweep.  I could do it on my Sunday night on the US west
> coast.
>
> Thoughts?
> Alex
>
> --
Andrew Wetmore

http://cottage14.blogspot.com/

Royale in 10 minutes (was Re: Proposed table of contents for Royale help documentation)

[Alex Harui]

Hi Andrew,

So I just pushed more stubs for the Create An Application section.  As I
was doing so, I started thinking that what you expect in that section is
different from what I'm interested in working on.  It isn't that we don't
need that section, but it appears that you want to address application
development as a general topic, discussing the design phase, and
maintenance phases, etc.

What I want to write is a "Royale in 10 minutes".  Sort of a tutorial for
building something more than a Hello World, and discuss some
"under-the-hood" things like how the app starts up, how you know the app
is ready, calling a web service, stuff like that.  If you agree we want
such a thing, where would it go?

Also, we have to be a bit careful about terminology.  The reason I
initially thought that I would do the "Royale in 10 minutes" in the
"Create an Application" section is because one subsection is titled
"Application Lifecycle".  To me, that meant the under-the-hood lifecycle
of an application like what its entry point is, what gets initialized
first, etc.  I'm tempted to rename the current "Application Lifecycle" to
"Application Development Phases" so I can use "Lifecycle" for the
under-the-hood section.  Or is there a better name for how an application
starts up?

I'm going to go spend some time on ASDoc while we figure this out.

Also, at some point, we should sweep through all of the files and add the
Apache header to them.  I did it in "Create an Application.md" to make
sure it didn't pollute the output.  I didn't do the sweep now since I
didn't know if you have files under edit.  I'm not sure what hours you are
working on this, so we should just pick a time where we have everything
committed and do a sweep.  I could do it on my Sunday night on the US west
coast.

Thoughts?
Alex


On 1/24/18, 3:33 AM, "Andrew Wetmore"  wrote:

>Hi!
>
>Yes, I feel like a real committer now.
>
>I am going to migrate some material from the FlexJS documentation to see
>what that experience is like. I am going to draw from "Overview" [1]
>ache.org%2Fconfluence%2Fpages%2Fviewpage.action%3FpageId%3D34013930=0
>2%7C01%7Caharui%40adobe.com%7C2c1e3998a2a74e3f711008d5631e4dff%7Cfa7b1b5a7
>b34438794aed2c178decee1%7C0%7C0%7C636523904169740086=xvrjFAbcWsrqNxC
>NLM8f9si466Td%2F1LWp2lkDiVKG5U%3D=0>
>to populate both "High level view" and the third-level "Migrate from Flex"
>under "Create an application".
>
>I have added a note about the "front matter" to the README file.
>
>Will take a look at your changes to the ToC structure before adding other
>page entries.
>
>This is fun!
>
>
>
>
>
>
>
>[1]
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apa
>che.org%2Fconfluence%2Fpages%2Fviewpage.action%3FpageId%3D34013930=02
>%7C01%7Caharui%40adobe.com%7C2c1e3998a2a74e3f711008d5631e4dff%7Cfa7b1b5a7b
>34438794aed2c178decee1%7C0%7C0%7C636523904169740086=xvrjFAbcWsrqNxCN
>LM8f9si466Td%2F1LWp2lkDiVKG5U%3D=0
>
>On Wed, Jan 24, 2018 at 3:50 AM, Alex Harui 
>wrote:
>
>> Hi Andrew,
>>
>> Looks like your commit privileges are working.
>>
>> I think we need to coordinate so we don't step on each others toes.  I'm
>> thinking I will add a bit to Features and Concepts so it links to its
>> children (AS3, MXML, PAYG, Strand and Beads) so I can make sure the
>> third-level of the TOC works, then move on to Create An Application as
>> that's where I want to spend more time building out some sort of app "in
>> 10 minutes".  Ideas for what to put in that app are welcome from
>>anybody.
>> I don't want it to just be "Hello World".  Maybe hit the network or a
>>JSON
>> file.  Or maybe I'll spend some time on ASDoc instead and come back to
>> this later.
>>
>> Couple of other things:
>> I reviewed your commits.  All .MD files need the "Front Matter".  See
>>one
>> of the .MD files I did and copy and modify the first lines with the
>>dashed
>> lines.  See Jekyll doc to understand it better.
>>
>> I just pushed a significant change to the pattern for new TOC entries in
>> docpage.html so please sync up before making more changes to that file.
>>
>> The main Welcome page is currently in index.md, not in Welcome/index.md.
>> The TOC does not point to Welcome/index.html.  I'm not sure that's right
>> so we might need to tweak how that works.  A related issue is that I
>>think
>> you wanted only the top-level TOC items visible when you first landed at
>> the doc, but that means that clicking on a TOC link doesn't expand to
>>show
>> child pages in the TOC, otherwise the Welcome would be expanded and show
>> High Level and Features and push Get Started further down.  If we do
>>have
>> a different /index.html as the landing page and Welcome in the TOC opens
>> Welcome/index.html, then we can have clicking a TOC link show the child
>> pages in the TOC.
>>
>> Another thing on my to-do list is to figure out how to use media query

Re: DropDownList with ArrayList

[Gabe Harbs]

Yeah. Maybe. In my case, I just used Array instead of ArrayList, but that 
shouldn’t really be necessary…

> On Jan 26, 2018, at 12:29 AM, Piotr Zarzycki  
> wrote:
> 
> Hi Harbs,
> 
> I've looked couple of times into the DropDownList from Basic. Maybe it's
> time to reorganize things. Add there View, Model, Renderers etc ? I did
> that for MDL DropDownList.
> 
> Thanks, Piotr
> 
> 2018-01-25 23:18 GMT+01:00 Gabe Harbs :
> 
>> The dataProvider setter in DropDownList has the following code:
>> 
>>for (i = 0; i < n; i++) {
>>opt = document.createElement('option') as
>> HTMLOptionElement;
>>if (lf)
>>opt.text = value[i][lf];
>>else
>>opt.text = value[i];
>>dd.add(opt, null);
>>}
>> 
>> Basically, it makes the assumption that the dataProvider is an
>> index-accessible object. This is not the case if the dataProvider is a
>> collection. In that case, the code should be something like this:
>> 
>>opt.text = value.getItemAt(i)[lf];
>>else
>>opt.text = value.getItemAt(i);
>> 
>> I’m not sure of the best way to generalize this.
>> 
>> Thoughts?
>> Harbs
> 
> 
> 
> 
> -- 
> 
> Piotr Zarzycki
> 
> Patreon: *https://www.patreon.com/piotrzarzycki
> *

DropDownList with ArrayList

[Gabe Harbs]

The dataProvider setter in DropDownList has the following code:

for (i = 0; i < n; i++) {
opt = document.createElement('option') as HTMLOptionElement;
if (lf)
opt.text = value[i][lf];
else
opt.text = value[i];
dd.add(opt, null);
}

Basically, it makes the assumption that the dataProvider is an index-accessible 
object. This is not the case if the dataProvider is a collection. In that case, 
the code should be something like this:

opt.text = value.getItemAt(i)[lf];
else
opt.text = value.getItemAt(i);

I’m not sure of the best way to generalize this.

Thoughts?
Harbs

Re: YouTube channel

[Carlos Rovira]

Hi,

I think this is a wonderful idea. I think youtube is nowadays a great way
to learn things, so a great way to learn about how to use Apache Royale.

So big +1! :)

2018-01-25 20:06 GMT+01:00 Dave Fisher :

> Hi -
>
> Does the Com Dev team know if there is an ASF YouTube channel that
> projects can use?
>
> Note this email is crossposted with dev@royale.
>
> I’ve asked privately at fundraising@
>
> Regards,
> Dave
>
> > On Jan 25, 2018, at 10:43 AM, Andrew Wetmore 
> wrote:
> >
> > Having a unified ASF channel would also be a good option. It could be a
> > much more lively channel than what any individual Apache project could
> > support.
> >
> > On Jan 25, 2018 2:39 PM, "Dave Fisher"  wrote:
> >
> >> Hi Andrew,
> >>
> >> That’s interesting. Since there is a donate button available I am going
> to
> >> ask the Fundraising committee. Stay tuned.
> >>
> >> Regards,
> >> Dave
> >>
> >>> On Jan 25, 2018, at 9:50 AM, Andrew Wetmore 
> wrote:
> >>>
> >>> Hi, Dave.
> >>>
> >>> My first step was to find out if such a channel already existed. I
> gather
> >>> it does not. I can either set one up under my own ID or go through the
> >>> "Google for Nonprofits" path[1] to see if they will let us set up a
> >> channel
> >>> for an ASF project rather than for ASF as a unit
> >>>
> >>> a
> >>>
> >>> [1]
> >>> https://www.google.com/nonprofits/products/youtube-
> >> nonprofit-program.html
> >>>
> >>> On Thu, Jan 25, 2018 at 1:34 PM, Dave Fisher 
> >> wrote:
> >>>
>  Hi Andrew,
> 
>  Great idea. Just make sure you share the details including access
>  information with the PMC by sending an email to
> >> priv...@royale.apache.org
> 
>  Regards,
>  Dave
> 
>  On Jan 25, 2018, at 8:34 AM, Andrew Wetmore 
> >> wrote:
> 
>  Hi:
> 
>  Does the project have a YouTube channel? I am thinking that, once we
> >> have
>  some apps to showcase (including the existing ones), I could create a
>  little video tour of each app, pointing out how it works and what
> Royale
>  lets you do to make it happen. We can then embed one or more videos in
> >> the
>  website as, oooh, eye candy.
> 
>  The app creator can do the script and narration, or I can do that for
> >> them
>  and assemble the video. Each one of these things would run for two or
> >> three
>  minutes.
> 
>  --
>  Andrew Wetmore
> 
>  http://cottage14.blogspot.com/
> 
> 
> 
> >>>
> >>>
> >>> --
> >>> Andrew Wetmore
> >>>
> >>> http://cottage14.blogspot.com/
> >>
> >>
>
>


-- 



Carlos Rovira

Director General

M: +34 607 22 60 05

http://www.codeoscopic.com


Conócenos en 1 minuto! 


Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.

De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.

Re: YouTube channel

[Dave Fisher]

Hi -

Does the Com Dev team know if there is an ASF YouTube channel that projects can 
use?

Note this email is crossposted with dev@royale.

I’ve asked privately at fundraising@

Regards,
Dave

> On Jan 25, 2018, at 10:43 AM, Andrew Wetmore  wrote:
> 
> Having a unified ASF channel would also be a good option. It could be a
> much more lively channel than what any individual Apache project could
> support.
> 
> On Jan 25, 2018 2:39 PM, "Dave Fisher"  wrote:
> 
>> Hi Andrew,
>> 
>> That’s interesting. Since there is a donate button available I am going to
>> ask the Fundraising committee. Stay tuned.
>> 
>> Regards,
>> Dave
>> 
>>> On Jan 25, 2018, at 9:50 AM, Andrew Wetmore  wrote:
>>> 
>>> Hi, Dave.
>>> 
>>> My first step was to find out if such a channel already existed. I gather
>>> it does not. I can either set one up under my own ID or go through the
>>> "Google for Nonprofits" path[1] to see if they will let us set up a
>> channel
>>> for an ASF project rather than for ASF as a unit
>>> 
>>> a
>>> 
>>> [1]
>>> https://www.google.com/nonprofits/products/youtube-
>> nonprofit-program.html
>>> 
>>> On Thu, Jan 25, 2018 at 1:34 PM, Dave Fisher 
>> wrote:
>>> 
 Hi Andrew,
 
 Great idea. Just make sure you share the details including access
 information with the PMC by sending an email to
>> priv...@royale.apache.org
 
 Regards,
 Dave
 
 On Jan 25, 2018, at 8:34 AM, Andrew Wetmore 
>> wrote:
 
 Hi:
 
 Does the project have a YouTube channel? I am thinking that, once we
>> have
 some apps to showcase (including the existing ones), I could create a
 little video tour of each app, pointing out how it works and what Royale
 lets you do to make it happen. We can then embed one or more videos in
>> the
 website as, oooh, eye candy.
 
 The app creator can do the script and narration, or I can do that for
>> them
 and assemble the video. Each one of these things would run for two or
>> three
 minutes.
 
 --
 Andrew Wetmore
 
 http://cottage14.blogspot.com/
 
 
 
>>> 
>>> 
>>> --
>>> Andrew Wetmore
>>> 
>>> http://cottage14.blogspot.com/
>> 
>> 



signature.asc
Description: Message signed with OpenPGP

Re: YouTube channel

[Andrew Wetmore]

Having a unified ASF channel would also be a good option. It could be a
much more lively channel than what any individual Apache project could
support.

On Jan 25, 2018 2:39 PM, "Dave Fisher"  wrote:

> Hi Andrew,
>
> That’s interesting. Since there is a donate button available I am going to
> ask the Fundraising committee. Stay tuned.
>
> Regards,
> Dave
>
> > On Jan 25, 2018, at 9:50 AM, Andrew Wetmore  wrote:
> >
> > Hi, Dave.
> >
> > My first step was to find out if such a channel already existed. I gather
> > it does not. I can either set one up under my own ID or go through the
> > "Google for Nonprofits" path[1] to see if they will let us set up a
> channel
> > for an ASF project rather than for ASF as a unit
> >
> > a
> >
> > [1]
> > https://www.google.com/nonprofits/products/youtube-
> nonprofit-program.html
> >
> > On Thu, Jan 25, 2018 at 1:34 PM, Dave Fisher 
> wrote:
> >
> >> Hi Andrew,
> >>
> >> Great idea. Just make sure you share the details including access
> >> information with the PMC by sending an email to
> priv...@royale.apache.org
> >>
> >> Regards,
> >> Dave
> >>
> >> On Jan 25, 2018, at 8:34 AM, Andrew Wetmore 
> wrote:
> >>
> >> Hi:
> >>
> >> Does the project have a YouTube channel? I am thinking that, once we
> have
> >> some apps to showcase (including the existing ones), I could create a
> >> little video tour of each app, pointing out how it works and what Royale
> >> lets you do to make it happen. We can then embed one or more videos in
> the
> >> website as, oooh, eye candy.
> >>
> >> The app creator can do the script and narration, or I can do that for
> them
> >> and assemble the video. Each one of these things would run for two or
> three
> >> minutes.
> >>
> >> --
> >> Andrew Wetmore
> >>
> >> http://cottage14.blogspot.com/
> >>
> >>
> >>
> >
> >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/
>
>

Re: YouTube channel

[Dave Fisher]

Hi Andrew,

That’s interesting. Since there is a donate button available I am going to ask 
the Fundraising committee. Stay tuned.

Regards,
Dave

> On Jan 25, 2018, at 9:50 AM, Andrew Wetmore  wrote:
> 
> Hi, Dave.
> 
> My first step was to find out if such a channel already existed. I gather
> it does not. I can either set one up under my own ID or go through the
> "Google for Nonprofits" path[1] to see if they will let us set up a channel
> for an ASF project rather than for ASF as a unit
> 
> a
> 
> [1]
> https://www.google.com/nonprofits/products/youtube-nonprofit-program.html
> 
> On Thu, Jan 25, 2018 at 1:34 PM, Dave Fisher  wrote:
> 
>> Hi Andrew,
>> 
>> Great idea. Just make sure you share the details including access
>> information with the PMC by sending an email to priv...@royale.apache.org
>> 
>> Regards,
>> Dave
>> 
>> On Jan 25, 2018, at 8:34 AM, Andrew Wetmore  wrote:
>> 
>> Hi:
>> 
>> Does the project have a YouTube channel? I am thinking that, once we have
>> some apps to showcase (including the existing ones), I could create a
>> little video tour of each app, pointing out how it works and what Royale
>> lets you do to make it happen. We can then embed one or more videos in the
>> website as, oooh, eye candy.
>> 
>> The app creator can do the script and narration, or I can do that for them
>> and assemble the video. Each one of these things would run for two or three
>> minutes.
>> 
>> --
>> Andrew Wetmore
>> 
>> http://cottage14.blogspot.com/
>> 
>> 
>> 
> 
> 
> --
> Andrew Wetmore
> 
> http://cottage14.blogspot.com/



signature.asc
Description: Message signed with OpenPGP

Re: Different results for compilation Error in JS and SWF compilation

[Piotr Zarzycki]

I have raised issue -> https://github.com/apache/royale-compiler/issues/21

2018-01-25 18:38 GMT+01:00 Alex Harui :

> Hmm.  Maybe MXMLJSC isn't able to pick up the ErrorFormat and just uses
> %s.  I've never looked into how the language resources work.
>
> HTH,
> -Alex
>
> On 1/25/18, 9:24 AM, "Piotr Zarzycki"  wrote:
>
> >Alex,
> >
> >I looked into that and without debugging there is no option for me figure
> >out what has happened. Both classes are using the same formatter and
> >printer to output errors. WorkspaceProblemFormatter and ProblemPrinter
> >
> >MXMLC is taking ErrorFormat=Error: %s from language resources. During the
> >compilation MXMLJSC is even using methods from MXMLC.
> >
> >
> >
> >2018-01-24 22:49 GMT+01:00 Piotr Zarzycki :
> >
> >> Ok now I understand! I will look into that :)
> >>
> >> 2018-01-24 21:40 GMT+01:00 Alex Harui :
> >>
> >>> I'm saying that if you want JSRoyale to have the same output as the SWF
> >>> target, I would look at the compiler source in those files and see if
> >>>they
> >>> are doing something different.  I could go fix it myself, but I am
> >>>trying
> >>> to encourage other committers to get more familiar with the compiler
> >>> source.
> >>>
> >>> HTH,
> >>> -Alex
> >>>
> >>> On 1/24/18, 12:37 PM, "Piotr Zarzycki" 
> >>>wrote:
> >>>
> >>> >Not sure what do you mean ? That's how we use it I think so.
> >>> >
> >>> >2018-01-24 21:28 GMT+01:00 Alex Harui :
> >>> >
> >>> >> Interesting.  Hadn't noticed that.  I guess you could compare the
> >>> output
> >>> >> logic in the compilers.  MXMLC.java should be used for SWF compiles
> >>>and
> >>> >> MXMLJSC.java for JS compiles.
> >>> >>
> >>> >> -Alex
> >>> >>
> >>> >> On 1/24/18, 11:59 AM, "Piotr Zarzycki" 
> >>> >>wrote:
> >>> >>
> >>> >> >Once Again:
> >>> >> >
> >>> >> >JSRoyale:
> >>> >> >col: 12 This attribute is unexpected. It will be ignored.
> >>> >> >:
> >>> >> >: 
> >>> >> >
> >>> >> >SWF:
> >>> >> >col: 12 Error: This attribute is unexpected. It will be ignored.
> >>> >> >:
> >>> >> >: 
> >>> >> >
> >>> >> >
> >>> >> >
> >>> >> >2018-01-24 20:47 GMT+01:00 Alex Harui :
> >>> >> >
> >>> >> >> Links are still broken.  Paste.a.o might be having problems.  Try
> >>> >>just
> >>> >> >>cut
> >>> >> >> and paste of a section of the main differences.
> >>> >> >>
> >>> >> >> -Alex
> >>> >> >>
> >>> >> >> On 1/24/18, 10:19 AM, "Piotr Zarzycki"
> >>>
> >>> >> >>wrote:
> >>> >> >>
> >>> >> >> >Something happened with Apache paste. Posting once again.
> >>> >> >> >
> >>> >> >> >JSRoyale compilation error [1]
> >>> >> >> >SWF compilation error [2]
> >>> >> >> >
> >>> >> >> >[1]
> >>> >> >> >https://na01.safelinks.protection.outlook.com/?url=
> >>> >> >> https%3A%2F%2Fpaste.apa
> >>> >> >> >che.org%2FJdNf=02%7C01%7Caharui%40adobe.com%
> >>> >> >> 7Cafcc22074376430e972508d
> >>> >> >> >5635711da%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> >>> >> >> 7C636524147998979848&
> >>> >> >> >sdata=11pnBHmUDQhSfiCfYIsbBw9G1n8vPfwEoAP09onRP14%3D=0
> >>> >> >> >[2]
> >>> >> >> >https://na01.safelinks.protection.outlook.com/?url=
> >>> >> >> https%3A%2F%2Fpaste.apa
> >>> >> >> >che.org%2FQgUo=02%7C01%7Caharui%40adobe.com%
> >>> >> >> 7Cafcc22074376430e972508d
> >>> >> >> >5635711da%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> >>> >> >> 7C636524147998979848&
> >>> >> >> >sdata=EcK0PgVPJWOa9YxQcvP6LbIbFZ32hNK6pjgsN695lxE%3D=0
> >>> >> >> >
> >>> >> >> >
> >>> >> >> >
> >>> >> >> >2018-01-24 18:22 GMT+01:00 Alex Harui
> >>>:
> >>> >> >> >
> >>> >> >> >> The links do not work for me.
> >>> >> >> >>
> >>> >> >> >> -Alex
> >>> >> >> >>
> >>> >> >> >> On 1/24/18, 4:19 AM, "Piotr Zarzycki"
> >>> >>> >
> >>> >> >> wrote:
> >>> >> >> >>
> >>> >> >> >> >Carlos,
> >>> >> >> >> >
> >>> >> >> >> >I know what causes the error :) I just wanted to know why the
> >>> >> >>message
> >>> >> >> >> >provided by compiler is different :)
> >>> >> >> >> >
> >>> >> >> >> >Piotr
> >>> >> >> >> >
> >>> >> >> >> >2018-01-24 13:18 GMT+01:00 Carlos Rovira
> >>> >>:
> >>> >> >> >> >
> >>> >> >> >> >> there's a need for a final "h" here percentWidt
> >>> >> >> >> >>
> >>> >> >> >> >> so it seems something is wrong in the generation right?
> >>> >> >> >> >>
> >>> >> >> >> >>
> >>> >> >> >> >> 2018-01-24 13:08 GMT+01:00 Piotr Zarzycki
> >>> >> >> >>:
> >>> >> >> >> >>
> >>> >> >> >> >> > Hi,
> >>> >> >> >> >> >
> >>> >> >> >> >> > I have found that during SWF only compilation and JS only
> >>> >> >>although
> >>> >> >> >>I'm
> >>> >> >> >> >> > getting the same errors they are reported a bit
> >>>differently.
> >>> >> >> >> >> >
> >>> >> >> >> >> > In build: compiler.targets=JSRoyale I got [1]
> >>> >> >> >> >> > In build: 

Re: YouTube channel

[Andrew Wetmore]

Hi, Dave.

My first step was to find out if such a channel already existed. I gather
it does not. I can either set one up under my own ID or go through the
"Google for Nonprofits" path[1] to see if they will let us set up a channel
for an ASF project rather than for ASF as a unit

a

[1]
https://www.google.com/nonprofits/products/youtube-nonprofit-program.html

On Thu, Jan 25, 2018 at 1:34 PM, Dave Fisher  wrote:

> Hi Andrew,
>
> Great idea. Just make sure you share the details including access
> information with the PMC by sending an email to priv...@royale.apache.org
>
> Regards,
> Dave
>
> On Jan 25, 2018, at 8:34 AM, Andrew Wetmore  wrote:
>
> Hi:
>
> Does the project have a YouTube channel? I am thinking that, once we have
> some apps to showcase (including the existing ones), I could create a
> little video tour of each app, pointing out how it works and what Royale
> lets you do to make it happen. We can then embed one or more videos in the
> website as, oooh, eye candy.
>
> The app creator can do the script and narration, or I can do that for them
> and assemble the video. Each one of these things would run for two or three
> minutes.
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>
>
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

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

[Piotr Zarzycki]

Great we can than use that link and point at least in the announce to that.

Piotr

2018-01-25 18:34 GMT+01:00 Alex Harui :

> Thanks Piotr.
>
> I was able to use NPM to install it by doing (on 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 users should be able to do this:
>
>   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
>
> I get a ton of output saying "WARN tar invalid entry".  At some point
> we'll have to investigate that.
>
>
>
>
> I guess it doesn't matter to me if you want to upload the other packages.
> If you do, I think you can remove the links to the mirrors.
>
> -Alex
>
> On 1/25/18, 8:32 AM, "Piotr Zarzycki"  wrote:
>
> >Done! Take a look. I can upload rest of the packages.
> >
> >2018-01-25 17:26 GMT+01:00 Alex Harui :
> >
> >> I would like you to try attaching just the bin-js.tar.gz
> >> I think that's the only package that will work with NPM.
> >>
> >> Thanks,
> >> -Alex
> >>
> >> On 1/25/18, 2:31 AM, "Piotr Zarzycki" 
> wrote:
> >>
> >> >It looks like we can attach those files to GitHub. I see there is such
> >> >option. Do you want me to download and attach them ?
> >> >
> >> >2018-01-25 10:49 GMT+01:00 Alex Harui :
> >> >
> >> >> Hi Piotr,
> >> >>
> >> >> Was there any way to add the -bin files to GitHub somewhere?
> >>Linking to
> >> >> the binaries on the mirrors is ok, but I was hoping we could find a
> >> >> non-mirrored URL so we can instruct folks to use npm with the url to
> >>the
> >> >> binaries.  If they use the mirrors, it is a two-step process, they
> >>have
> >> >>to
> >> >> go to the mirror and pick a mirror and use that with npm.
> >> >>
> >> >> Maybe I should put a copy on the CI server.
> >> >>
> >> >> Thoughts?
> >> >> -Alex
> >> >>
> >> >>
> >> >>
> >> >> On 1/24/18, 10:55 PM, "Piotr Zarzycki" 
> >> >>wrote:
> >> >>
> >> >> >I have published ->
> >> >> >https://na01.safelinks.protection.outlook.com/?url=
> >> >> https%3A%2F%2Fgithub.co
> >> >> >m%2Fapache%2Froyale-asjs%2Freleases%2Ftag%2Fapache-
> >> >> royale-0.9.0=02%7C
> >> >> >01%7Caharui%40adobe.com%7C6dd26e630781475a026b08d563c0
> >> >> adf9%7Cfa7b1b5a7b344
> >> >> >38794aed2c178decee1%7C0%7C0%7C636524601572591983=
> >> >> 3wGTQuEfLQnV6LHZr0h
> >> >> >FyZ1MVnRnSb5BwAyoWQm1Dqk%3D=0
> >> >> >
> >> >> >2018-01-25 7:18 GMT+01:00 Piotr Zarzycki
> >>:
> >> >> >
> >> >> >> Alex,
> >> >> >>
> >> >> >> We can edit text later, that is not a problem.
> >> >> >>
> >> >> >> Piotr
> >> >> >>
> >> >> >> 2018-01-25 0:35 GMT+01:00 OmPrakash Muppirala
> >> >> >:
> >> >> >>
> >> >> >>> I think it is perfectly fine to announce without npm support.  We
> >> >>can
> >> >> >>>add
> >> >> >>> it in our next release.
> >> >> >>>
> >> >> >>> Thanks,
> >> >> >>> Om
> >> >> >>>
> >> >> >>> On Wed, Jan 24, 2018 at 3:31 PM, Alex Harui
> >> >>
> >> >> >>> wrote:
> >> >> >>>
> >> >> >>> > If we can edit the text later, then IMO, go ahead and publish.
> >> >> >>> >
> >> >> >>> > If not, we might want to wait to hear from more folks.
> >> >> >>> >
> >> >> >>> > -Alex
> >> >> >>> >
> >> >> >>> > On 1/24/18, 3:20 PM, "Piotr Zarzycki"
> >>
> >> >> >>> wrote:
> >> >> >>> >
> >> >> >>> > >I have created release on GitHub - It's unpublished [1] - Do
> >>we
> >> >> >>>want to
> >> >> >>> > >add
> >> >> >>> > >something more there ?
> >> >> >>> > >
> >> >> >>> > >[1]
> >> >> >>> > >https://na01.safelinks.protection.outlook.com/?url=
> >> >> >>> > https%3A%2F%2Fgithub.co
> >> >> >>> > >m%2Fapache%2Froyale-asjs%2Freleases%2Ftag%2Funtagged-
> >> >> >>> > 3e7dc9305c4ad1eaa804&
> >> >> >>> >
> >>>data=02%7C01%7Caharui%40adobe.com%7C2688068931e74b0ed20b08d56381
> >> >> >>> > 0cae%7Cfa7
> >> >> >>> > >b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524328276148227&
> >> >> >>> > sdata=waf5UTV1g
> >> >> >>> > >Rint9dmutBs6v2y7USv3KNP3dJKI7%2FzZFs%3D=0
> >> >> >>> > >
> >> >> >>> > >Thanks, Piotr
> >> >> >>> > >
> >> >> >>> > >2018-01-24 23:06 GMT+01:00 Carlos Rovira
> >> >>:
> >> >> >>> > >
> >> >> >>> > >> Hi thanks Alex and Andrew,
> >> >> >>> > >>
> >> >> >>> > >> right now we are having such moderate impact on internet.
> >>For
> >> >> >>> example in
> >> >> >>> > >> twitter we have 135 followers, in facebook 40. We have the
> >> >> >>>accounts
> >> >> >>> open
> >> >> >>> > >> about 15 days like the website. So we can make huge noise
> >>right
> >> >> >>>now.
> >> >> >>> > >>Just
> >> >> >>> > >> letting people know we release our first release is great,
> >>but
> >> >>we
> >> >> >>> must
> >> >> >>> > >> lower expectations about actual Apache Royale state since
> >> >>although

Re: Different results for compilation Error in JS and SWF compilation

[Alex Harui]

Hmm.  Maybe MXMLJSC isn't able to pick up the ErrorFormat and just uses
%s.  I've never looked into how the language resources work.

HTH,
-Alex

On 1/25/18, 9:24 AM, "Piotr Zarzycki"  wrote:

>Alex,
>
>I looked into that and without debugging there is no option for me figure
>out what has happened. Both classes are using the same formatter and
>printer to output errors. WorkspaceProblemFormatter and ProblemPrinter
>
>MXMLC is taking ErrorFormat=Error: %s from language resources. During the
>compilation MXMLJSC is even using methods from MXMLC.
>
>
>
>2018-01-24 22:49 GMT+01:00 Piotr Zarzycki :
>
>> Ok now I understand! I will look into that :)
>>
>> 2018-01-24 21:40 GMT+01:00 Alex Harui :
>>
>>> I'm saying that if you want JSRoyale to have the same output as the SWF
>>> target, I would look at the compiler source in those files and see if
>>>they
>>> are doing something different.  I could go fix it myself, but I am
>>>trying
>>> to encourage other committers to get more familiar with the compiler
>>> source.
>>>
>>> HTH,
>>> -Alex
>>>
>>> On 1/24/18, 12:37 PM, "Piotr Zarzycki" 
>>>wrote:
>>>
>>> >Not sure what do you mean ? That's how we use it I think so.
>>> >
>>> >2018-01-24 21:28 GMT+01:00 Alex Harui :
>>> >
>>> >> Interesting.  Hadn't noticed that.  I guess you could compare the
>>> output
>>> >> logic in the compilers.  MXMLC.java should be used for SWF compiles
>>>and
>>> >> MXMLJSC.java for JS compiles.
>>> >>
>>> >> -Alex
>>> >>
>>> >> On 1/24/18, 11:59 AM, "Piotr Zarzycki" 
>>> >>wrote:
>>> >>
>>> >> >Once Again:
>>> >> >
>>> >> >JSRoyale:
>>> >> >col: 12 This attribute is unexpected. It will be ignored.
>>> >> >:
>>> >> >: 
>>> >> >
>>> >> >SWF:
>>> >> >col: 12 Error: This attribute is unexpected. It will be ignored.
>>> >> >:
>>> >> >: 
>>> >> >
>>> >> >
>>> >> >
>>> >> >2018-01-24 20:47 GMT+01:00 Alex Harui :
>>> >> >
>>> >> >> Links are still broken.  Paste.a.o might be having problems.  Try
>>> >>just
>>> >> >>cut
>>> >> >> and paste of a section of the main differences.
>>> >> >>
>>> >> >> -Alex
>>> >> >>
>>> >> >> On 1/24/18, 10:19 AM, "Piotr Zarzycki"
>>>
>>> >> >>wrote:
>>> >> >>
>>> >> >> >Something happened with Apache paste. Posting once again.
>>> >> >> >
>>> >> >> >JSRoyale compilation error [1]
>>> >> >> >SWF compilation error [2]
>>> >> >> >
>>> >> >> >[1]
>>> >> >> >https://na01.safelinks.protection.outlook.com/?url=
>>> >> >> https%3A%2F%2Fpaste.apa
>>> >> >> >che.org%2FJdNf=02%7C01%7Caharui%40adobe.com%
>>> >> >> 7Cafcc22074376430e972508d
>>> >> >> >5635711da%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>>> >> >> 7C636524147998979848&
>>> >> >> >sdata=11pnBHmUDQhSfiCfYIsbBw9G1n8vPfwEoAP09onRP14%3D=0
>>> >> >> >[2]
>>> >> >> >https://na01.safelinks.protection.outlook.com/?url=
>>> >> >> https%3A%2F%2Fpaste.apa
>>> >> >> >che.org%2FQgUo=02%7C01%7Caharui%40adobe.com%
>>> >> >> 7Cafcc22074376430e972508d
>>> >> >> >5635711da%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>>> >> >> 7C636524147998979848&
>>> >> >> >sdata=EcK0PgVPJWOa9YxQcvP6LbIbFZ32hNK6pjgsN695lxE%3D=0
>>> >> >> >
>>> >> >> >
>>> >> >> >
>>> >> >> >2018-01-24 18:22 GMT+01:00 Alex Harui
>>>:
>>> >> >> >
>>> >> >> >> The links do not work for me.
>>> >> >> >>
>>> >> >> >> -Alex
>>> >> >> >>
>>> >> >> >> On 1/24/18, 4:19 AM, "Piotr Zarzycki"
>>>>> >
>>> >> >> wrote:
>>> >> >> >>
>>> >> >> >> >Carlos,
>>> >> >> >> >
>>> >> >> >> >I know what causes the error :) I just wanted to know why the
>>> >> >>message
>>> >> >> >> >provided by compiler is different :)
>>> >> >> >> >
>>> >> >> >> >Piotr
>>> >> >> >> >
>>> >> >> >> >2018-01-24 13:18 GMT+01:00 Carlos Rovira
>>> >>:
>>> >> >> >> >
>>> >> >> >> >> there's a need for a final "h" here percentWidt
>>> >> >> >> >>
>>> >> >> >> >> so it seems something is wrong in the generation right?
>>> >> >> >> >>
>>> >> >> >> >>
>>> >> >> >> >> 2018-01-24 13:08 GMT+01:00 Piotr Zarzycki
>>> >> >> >>:
>>> >> >> >> >>
>>> >> >> >> >> > Hi,
>>> >> >> >> >> >
>>> >> >> >> >> > I have found that during SWF only compilation and JS only
>>> >> >>although
>>> >> >> >>I'm
>>> >> >> >> >> > getting the same errors they are reported a bit
>>>differently.
>>> >> >> >> >> >
>>> >> >> >> >> > In build: compiler.targets=JSRoyale I got [1]
>>> >> >> >> >> > In build: compiler.targets=SWF I got [2]
>>> >> >> >> >> >
>>> >> >> >> >> > There is no word "Error" in case of JSRoyale - Is this a
>>>bug
>>> >>?
>>> >> >> >> >> >
>>> >> >> >> >> > [1]
>>> >> >> >> >>https://na01.safelinks.protection.outlook.com/?url=
>>> >> >> >> https%3A%2F%2Fpaste.ap
>>> >> >> >> >>ache.org%2FH7m7=02%7C01%7Caharui%40adobe.com%
>>> >> >> >> 7C86539a854146402e21510
>>> >> >> >> 

Re: YouTube channel

[Dave Fisher]

Hi Andrew,

Great idea. Just make sure you share the details including access information 
with the PMC by sending an email to priv...@royale.apache.org 


Regards,
Dave

> On Jan 25, 2018, at 8:34 AM, Andrew Wetmore  wrote:
> 
> Hi:
> 
> Does the project have a YouTube channel? I am thinking that, once we have
> some apps to showcase (including the existing ones), I could create a
> little video tour of each app, pointing out how it works and what Royale
> lets you do to make it happen. We can then embed one or more videos in the
> website as, oooh, eye candy.
> 
> The app creator can do the script and narration, or I can do that for them
> and assemble the video. Each one of these things would run for two or three
> minutes.
> 
> --
> Andrew Wetmore
> 
> http://cottage14.blogspot.com/



signature.asc
Description: Message signed with OpenPGP

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

[Alex Harui]

Thanks Piotr.

I was able to use NPM to install it by doing (on 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 users should be able to do this:

  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

I get a ton of output saying "WARN tar invalid entry".  At some point
we'll have to investigate that.




I guess it doesn't matter to me if you want to upload the other packages.
If you do, I think you can remove the links to the mirrors.

-Alex

On 1/25/18, 8:32 AM, "Piotr Zarzycki"  wrote:

>Done! Take a look. I can upload rest of the packages.
>
>2018-01-25 17:26 GMT+01:00 Alex Harui :
>
>> I would like you to try attaching just the bin-js.tar.gz
>> I think that's the only package that will work with NPM.
>>
>> Thanks,
>> -Alex
>>
>> On 1/25/18, 2:31 AM, "Piotr Zarzycki"  wrote:
>>
>> >It looks like we can attach those files to GitHub. I see there is such
>> >option. Do you want me to download and attach them ?
>> >
>> >2018-01-25 10:49 GMT+01:00 Alex Harui :
>> >
>> >> Hi Piotr,
>> >>
>> >> Was there any way to add the -bin files to GitHub somewhere?
>>Linking to
>> >> the binaries on the mirrors is ok, but I was hoping we could find a
>> >> non-mirrored URL so we can instruct folks to use npm with the url to
>>the
>> >> binaries.  If they use the mirrors, it is a two-step process, they
>>have
>> >>to
>> >> go to the mirror and pick a mirror and use that with npm.
>> >>
>> >> Maybe I should put a copy on the CI server.
>> >>
>> >> Thoughts?
>> >> -Alex
>> >>
>> >>
>> >>
>> >> On 1/24/18, 10:55 PM, "Piotr Zarzycki" 
>> >>wrote:
>> >>
>> >> >I have published ->
>> >> >https://na01.safelinks.protection.outlook.com/?url=
>> >> https%3A%2F%2Fgithub.co
>> >> >m%2Fapache%2Froyale-asjs%2Freleases%2Ftag%2Fapache-
>> >> royale-0.9.0=02%7C
>> >> >01%7Caharui%40adobe.com%7C6dd26e630781475a026b08d563c0
>> >> adf9%7Cfa7b1b5a7b344
>> >> >38794aed2c178decee1%7C0%7C0%7C636524601572591983=
>> >> 3wGTQuEfLQnV6LHZr0h
>> >> >FyZ1MVnRnSb5BwAyoWQm1Dqk%3D=0
>> >> >
>> >> >2018-01-25 7:18 GMT+01:00 Piotr Zarzycki
>>:
>> >> >
>> >> >> Alex,
>> >> >>
>> >> >> We can edit text later, that is not a problem.
>> >> >>
>> >> >> Piotr
>> >> >>
>> >> >> 2018-01-25 0:35 GMT+01:00 OmPrakash Muppirala
>>> >:
>> >> >>
>> >> >>> I think it is perfectly fine to announce without npm support.  We
>> >>can
>> >> >>>add
>> >> >>> it in our next release.
>> >> >>>
>> >> >>> Thanks,
>> >> >>> Om
>> >> >>>
>> >> >>> On Wed, Jan 24, 2018 at 3:31 PM, Alex Harui
>> >>
>> >> >>> wrote:
>> >> >>>
>> >> >>> > If we can edit the text later, then IMO, go ahead and publish.
>> >> >>> >
>> >> >>> > If not, we might want to wait to hear from more folks.
>> >> >>> >
>> >> >>> > -Alex
>> >> >>> >
>> >> >>> > On 1/24/18, 3:20 PM, "Piotr Zarzycki"
>>
>> >> >>> wrote:
>> >> >>> >
>> >> >>> > >I have created release on GitHub - It's unpublished [1] - Do
>>we
>> >> >>>want to
>> >> >>> > >add
>> >> >>> > >something more there ?
>> >> >>> > >
>> >> >>> > >[1]
>> >> >>> > >https://na01.safelinks.protection.outlook.com/?url=
>> >> >>> > https%3A%2F%2Fgithub.co
>> >> >>> > >m%2Fapache%2Froyale-asjs%2Freleases%2Ftag%2Funtagged-
>> >> >>> > 3e7dc9305c4ad1eaa804&
>> >> >>> > 
>>>data=02%7C01%7Caharui%40adobe.com%7C2688068931e74b0ed20b08d56381
>> >> >>> > 0cae%7Cfa7
>> >> >>> > >b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524328276148227&
>> >> >>> > sdata=waf5UTV1g
>> >> >>> > >Rint9dmutBs6v2y7USv3KNP3dJKI7%2FzZFs%3D=0
>> >> >>> > >
>> >> >>> > >Thanks, Piotr
>> >> >>> > >
>> >> >>> > >2018-01-24 23:06 GMT+01:00 Carlos Rovira
>> >>:
>> >> >>> > >
>> >> >>> > >> Hi thanks Alex and Andrew,
>> >> >>> > >>
>> >> >>> > >> right now we are having such moderate impact on internet.
>>For
>> >> >>> example in
>> >> >>> > >> twitter we have 135 followers, in facebook 40. We have the
>> >> >>>accounts
>> >> >>> open
>> >> >>> > >> about 15 days like the website. So we can make huge noise
>>right
>> >> >>>now.
>> >> >>> > >>Just
>> >> >>> > >> letting people know we release our first release is great,
>>but
>> >>we
>> >> >>> must
>> >> >>> > >> lower expectations about actual Apache Royale state since
>> >>although
>> >> >>> the
>> >> >>> > >> technology in in place, to make real apps it's not as
>>friendly
>> >>as
>> >> >>> Flex,
>> >> >>> > >>and
>> >> >>> > >> we don't want people coming get frustrated about that. But
>>this
>> >> >>>is a
>> >> >>> > >> required step in order to follow up improving royale
>> >> >>> > >>
>> >> >>> > >>
>> >> >>> > >>
>> >> >>> > >>
>> >> >>> > >> 2018-01-24 19:00 GMT+01:00 Andrew Wetmore
>> >>:
>> >> 

Re: Different results for compilation Error in JS and SWF compilation

[Piotr Zarzycki]

Alex,

I looked into that and without debugging there is no option for me figure
out what has happened. Both classes are using the same formatter and
printer to output errors. WorkspaceProblemFormatter and ProblemPrinter

MXMLC is taking ErrorFormat=Error: %s from language resources. During the
compilation MXMLJSC is even using methods from MXMLC.



2018-01-24 22:49 GMT+01:00 Piotr Zarzycki :

> Ok now I understand! I will look into that :)
>
> 2018-01-24 21:40 GMT+01:00 Alex Harui :
>
>> I'm saying that if you want JSRoyale to have the same output as the SWF
>> target, I would look at the compiler source in those files and see if they
>> are doing something different.  I could go fix it myself, but I am trying
>> to encourage other committers to get more familiar with the compiler
>> source.
>>
>> HTH,
>> -Alex
>>
>> On 1/24/18, 12:37 PM, "Piotr Zarzycki"  wrote:
>>
>> >Not sure what do you mean ? That's how we use it I think so.
>> >
>> >2018-01-24 21:28 GMT+01:00 Alex Harui :
>> >
>> >> Interesting.  Hadn't noticed that.  I guess you could compare the
>> output
>> >> logic in the compilers.  MXMLC.java should be used for SWF compiles and
>> >> MXMLJSC.java for JS compiles.
>> >>
>> >> -Alex
>> >>
>> >> On 1/24/18, 11:59 AM, "Piotr Zarzycki" 
>> >>wrote:
>> >>
>> >> >Once Again:
>> >> >
>> >> >JSRoyale:
>> >> >col: 12 This attribute is unexpected. It will be ignored.
>> >> >:
>> >> >: 
>> >> >
>> >> >SWF:
>> >> >col: 12 Error: This attribute is unexpected. It will be ignored.
>> >> >:
>> >> >: 
>> >> >
>> >> >
>> >> >
>> >> >2018-01-24 20:47 GMT+01:00 Alex Harui :
>> >> >
>> >> >> Links are still broken.  Paste.a.o might be having problems.  Try
>> >>just
>> >> >>cut
>> >> >> and paste of a section of the main differences.
>> >> >>
>> >> >> -Alex
>> >> >>
>> >> >> On 1/24/18, 10:19 AM, "Piotr Zarzycki" 
>> >> >>wrote:
>> >> >>
>> >> >> >Something happened with Apache paste. Posting once again.
>> >> >> >
>> >> >> >JSRoyale compilation error [1]
>> >> >> >SWF compilation error [2]
>> >> >> >
>> >> >> >[1]
>> >> >> >https://na01.safelinks.protection.outlook.com/?url=
>> >> >> https%3A%2F%2Fpaste.apa
>> >> >> >che.org%2FJdNf=02%7C01%7Caharui%40adobe.com%
>> >> >> 7Cafcc22074376430e972508d
>> >> >> >5635711da%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> >> >> 7C636524147998979848&
>> >> >> >sdata=11pnBHmUDQhSfiCfYIsbBw9G1n8vPfwEoAP09onRP14%3D=0
>> >> >> >[2]
>> >> >> >https://na01.safelinks.protection.outlook.com/?url=
>> >> >> https%3A%2F%2Fpaste.apa
>> >> >> >che.org%2FQgUo=02%7C01%7Caharui%40adobe.com%
>> >> >> 7Cafcc22074376430e972508d
>> >> >> >5635711da%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> >> >> 7C636524147998979848&
>> >> >> >sdata=EcK0PgVPJWOa9YxQcvP6LbIbFZ32hNK6pjgsN695lxE%3D=0
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> >2018-01-24 18:22 GMT+01:00 Alex Harui :
>> >> >> >
>> >> >> >> The links do not work for me.
>> >> >> >>
>> >> >> >> -Alex
>> >> >> >>
>> >> >> >> On 1/24/18, 4:19 AM, "Piotr Zarzycki" > >
>> >> >> wrote:
>> >> >> >>
>> >> >> >> >Carlos,
>> >> >> >> >
>> >> >> >> >I know what causes the error :) I just wanted to know why the
>> >> >>message
>> >> >> >> >provided by compiler is different :)
>> >> >> >> >
>> >> >> >> >Piotr
>> >> >> >> >
>> >> >> >> >2018-01-24 13:18 GMT+01:00 Carlos Rovira
>> >>:
>> >> >> >> >
>> >> >> >> >> there's a need for a final "h" here percentWidt
>> >> >> >> >>
>> >> >> >> >> so it seems something is wrong in the generation right?
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> 2018-01-24 13:08 GMT+01:00 Piotr Zarzycki
>> >> >> >>:
>> >> >> >> >>
>> >> >> >> >> > Hi,
>> >> >> >> >> >
>> >> >> >> >> > I have found that during SWF only compilation and JS only
>> >> >>although
>> >> >> >>I'm
>> >> >> >> >> > getting the same errors they are reported a bit differently.
>> >> >> >> >> >
>> >> >> >> >> > In build: compiler.targets=JSRoyale I got [1]
>> >> >> >> >> > In build: compiler.targets=SWF I got [2]
>> >> >> >> >> >
>> >> >> >> >> > There is no word "Error" in case of JSRoyale - Is this a bug
>> >>?
>> >> >> >> >> >
>> >> >> >> >> > [1]
>> >> >> >> >>https://na01.safelinks.protection.outlook.com/?url=
>> >> >> >> https%3A%2F%2Fpaste.ap
>> >> >> >> >>ache.org%2FH7m7=02%7C01%7Caharui%40adobe.com%
>> >> >> >> 7C86539a854146402e21510
>> >> >> >> >>8d56324c4af%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> >> >> >> 7C6365239319247711
>> >> >> >>
>> 78=I0RlFQKtU8QJ48nFi3Zv6e9gmrVHfTqUiCD0rHxOfYs%3D=0
>> >> >> >> >> > [2]
>> >> >> >> >>https://na01.safelinks.protection.outlook.com/?url=
>> >> >> >> https%3A%2F%2Fpaste.ap
>> >> >> >> >>ache.org%2FtvL9=02%7C01%7Caharui%40adobe.com%
>> >> >> >> 7C86539a854146402e21510
>> >> >> >> 

Re: YouTube channel

[Alex Harui]

If you've got the time, go for it!

On 1/25/18, 8:34 AM, "Andrew Wetmore"  wrote:

>Hi:
>
>Does the project have a YouTube channel? I am thinking that, once we have
>some apps to showcase (including the existing ones), I could create a
>little video tour of each app, pointing out how it works and what Royale
>lets you do to make it happen. We can then embed one or more videos in the
>website as, oooh, eye candy.
>
>The app creator can do the script and narration, or I can do that for them
>and assemble the video. Each one of these things would run for two or
>three
>minutes.
>
>-- 
>Andrew Wetmore
>
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.
>blogspot.com%2F=02%7C01%7Caharui%40adobe.com%7C4707a5d21bf54dd0bf2708
>d564118d2c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524948903241816
>=Zh2VhhNpsPZstnzqLZGPmrm9cOSJqz%2BPxAMItD9%2BdpE%3D=0

YouTube channel

[Andrew Wetmore]

Hi:

Does the project have a YouTube channel? I am thinking that, once we have
some apps to showcase (including the existing ones), I could create a
little video tour of each app, pointing out how it works and what Royale
lets you do to make it happen. We can then embed one or more videos in the
website as, oooh, eye candy.

The app creator can do the script and narration, or I can do that for them
and assemble the video. Each one of these things would run for two or three
minutes.

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

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

[Piotr Zarzycki]

Done! Take a look. I can upload rest of the packages.

2018-01-25 17:26 GMT+01:00 Alex Harui :

> I would like you to try attaching just the bin-js.tar.gz
> I think that's the only package that will work with NPM.
>
> Thanks,
> -Alex
>
> On 1/25/18, 2:31 AM, "Piotr Zarzycki"  wrote:
>
> >It looks like we can attach those files to GitHub. I see there is such
> >option. Do you want me to download and attach them ?
> >
> >2018-01-25 10:49 GMT+01:00 Alex Harui :
> >
> >> Hi Piotr,
> >>
> >> Was there any way to add the -bin files to GitHub somewhere?  Linking to
> >> the binaries on the mirrors is ok, but I was hoping we could find a
> >> non-mirrored URL so we can instruct folks to use npm with the url to the
> >> binaries.  If they use the mirrors, it is a two-step process, they have
> >>to
> >> go to the mirror and pick a mirror and use that with npm.
> >>
> >> Maybe I should put a copy on the CI server.
> >>
> >> Thoughts?
> >> -Alex
> >>
> >>
> >>
> >> On 1/24/18, 10:55 PM, "Piotr Zarzycki" 
> >>wrote:
> >>
> >> >I have published ->
> >> >https://na01.safelinks.protection.outlook.com/?url=
> >> https%3A%2F%2Fgithub.co
> >> >m%2Fapache%2Froyale-asjs%2Freleases%2Ftag%2Fapache-
> >> royale-0.9.0=02%7C
> >> >01%7Caharui%40adobe.com%7C6dd26e630781475a026b08d563c0
> >> adf9%7Cfa7b1b5a7b344
> >> >38794aed2c178decee1%7C0%7C0%7C636524601572591983=
> >> 3wGTQuEfLQnV6LHZr0h
> >> >FyZ1MVnRnSb5BwAyoWQm1Dqk%3D=0
> >> >
> >> >2018-01-25 7:18 GMT+01:00 Piotr Zarzycki :
> >> >
> >> >> Alex,
> >> >>
> >> >> We can edit text later, that is not a problem.
> >> >>
> >> >> Piotr
> >> >>
> >> >> 2018-01-25 0:35 GMT+01:00 OmPrakash Muppirala  >:
> >> >>
> >> >>> I think it is perfectly fine to announce without npm support.  We
> >>can
> >> >>>add
> >> >>> it in our next release.
> >> >>>
> >> >>> Thanks,
> >> >>> Om
> >> >>>
> >> >>> On Wed, Jan 24, 2018 at 3:31 PM, Alex Harui
> >>
> >> >>> wrote:
> >> >>>
> >> >>> > If we can edit the text later, then IMO, go ahead and publish.
> >> >>> >
> >> >>> > If not, we might want to wait to hear from more folks.
> >> >>> >
> >> >>> > -Alex
> >> >>> >
> >> >>> > On 1/24/18, 3:20 PM, "Piotr Zarzycki" 
> >> >>> wrote:
> >> >>> >
> >> >>> > >I have created release on GitHub - It's unpublished [1] - Do we
> >> >>>want to
> >> >>> > >add
> >> >>> > >something more there ?
> >> >>> > >
> >> >>> > >[1]
> >> >>> > >https://na01.safelinks.protection.outlook.com/?url=
> >> >>> > https%3A%2F%2Fgithub.co
> >> >>> > >m%2Fapache%2Froyale-asjs%2Freleases%2Ftag%2Funtagged-
> >> >>> > 3e7dc9305c4ad1eaa804&
> >> >>> > >data=02%7C01%7Caharui%40adobe.com%7C2688068931e74b0ed20b08d56381
> >> >>> > 0cae%7Cfa7
> >> >>> > >b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524328276148227&
> >> >>> > sdata=waf5UTV1g
> >> >>> > >Rint9dmutBs6v2y7USv3KNP3dJKI7%2FzZFs%3D=0
> >> >>> > >
> >> >>> > >Thanks, Piotr
> >> >>> > >
> >> >>> > >2018-01-24 23:06 GMT+01:00 Carlos Rovira
> >>:
> >> >>> > >
> >> >>> > >> Hi thanks Alex and Andrew,
> >> >>> > >>
> >> >>> > >> right now we are having such moderate impact on internet. For
> >> >>> example in
> >> >>> > >> twitter we have 135 followers, in facebook 40. We have the
> >> >>>accounts
> >> >>> open
> >> >>> > >> about 15 days like the website. So we can make huge noise right
> >> >>>now.
> >> >>> > >>Just
> >> >>> > >> letting people know we release our first release is great, but
> >>we
> >> >>> must
> >> >>> > >> lower expectations about actual Apache Royale state since
> >>although
> >> >>> the
> >> >>> > >> technology in in place, to make real apps it's not as friendly
> >>as
> >> >>> Flex,
> >> >>> > >>and
> >> >>> > >> we don't want people coming get frustrated about that. But this
> >> >>>is a
> >> >>> > >> required step in order to follow up improving royale
> >> >>> > >>
> >> >>> > >>
> >> >>> > >>
> >> >>> > >>
> >> >>> > >> 2018-01-24 19:00 GMT+01:00 Andrew Wetmore
> >>:
> >> >>> > >>
> >> >>> > >> > Tweakage: I would change this passage
> >> >>> > >> >
> >> >>> > >> > This release should be considered ‘beta' quality. The
> >>purpose of
> >> >>> this
> >> >>> > >> > release is to gather feedback about the features and
> >> >>>implementation
> >> >>> > >> > strategies, and recruit new contributors as we grow the code
> >> >>>base
> >> >>> > >>into an
> >> >>> > >> > SDK and tool chain that delivers the highest productivity
> >> >>> developing
> >> >>> > >> > applications that can run in the most places. These releases
> >>may
> >> >>> not
> >> >>> > >> > handle production needs.
> >> >>> > >> >
> >> >>> > >> > to this
> >> >>> > >> >
> >> >>> > >> > This release should be considered ‘beta' quality. The
> >>purpose of
> >> >>> this
> >> >>> > >> > release is to gather feedback about the features and
> >> 

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

[Alex Harui]

I would like you to try attaching just the bin-js.tar.gz
I think that's the only package that will work with NPM.

Thanks,
-Alex

On 1/25/18, 2:31 AM, "Piotr Zarzycki"  wrote:

>It looks like we can attach those files to GitHub. I see there is such
>option. Do you want me to download and attach them ?
>
>2018-01-25 10:49 GMT+01:00 Alex Harui :
>
>> Hi Piotr,
>>
>> Was there any way to add the -bin files to GitHub somewhere?  Linking to
>> the binaries on the mirrors is ok, but I was hoping we could find a
>> non-mirrored URL so we can instruct folks to use npm with the url to the
>> binaries.  If they use the mirrors, it is a two-step process, they have
>>to
>> go to the mirror and pick a mirror and use that with npm.
>>
>> Maybe I should put a copy on the CI server.
>>
>> Thoughts?
>> -Alex
>>
>>
>>
>> On 1/24/18, 10:55 PM, "Piotr Zarzycki" 
>>wrote:
>>
>> >I have published ->
>> >https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Fgithub.co
>> >m%2Fapache%2Froyale-asjs%2Freleases%2Ftag%2Fapache-
>> royale-0.9.0=02%7C
>> >01%7Caharui%40adobe.com%7C6dd26e630781475a026b08d563c0
>> adf9%7Cfa7b1b5a7b344
>> >38794aed2c178decee1%7C0%7C0%7C636524601572591983=
>> 3wGTQuEfLQnV6LHZr0h
>> >FyZ1MVnRnSb5BwAyoWQm1Dqk%3D=0
>> >
>> >2018-01-25 7:18 GMT+01:00 Piotr Zarzycki :
>> >
>> >> Alex,
>> >>
>> >> We can edit text later, that is not a problem.
>> >>
>> >> Piotr
>> >>
>> >> 2018-01-25 0:35 GMT+01:00 OmPrakash Muppirala :
>> >>
>> >>> I think it is perfectly fine to announce without npm support.  We
>>can
>> >>>add
>> >>> it in our next release.
>> >>>
>> >>> Thanks,
>> >>> Om
>> >>>
>> >>> On Wed, Jan 24, 2018 at 3:31 PM, Alex Harui
>>
>> >>> wrote:
>> >>>
>> >>> > If we can edit the text later, then IMO, go ahead and publish.
>> >>> >
>> >>> > If not, we might want to wait to hear from more folks.
>> >>> >
>> >>> > -Alex
>> >>> >
>> >>> > On 1/24/18, 3:20 PM, "Piotr Zarzycki" 
>> >>> wrote:
>> >>> >
>> >>> > >I have created release on GitHub - It's unpublished [1] - Do we
>> >>>want to
>> >>> > >add
>> >>> > >something more there ?
>> >>> > >
>> >>> > >[1]
>> >>> > >https://na01.safelinks.protection.outlook.com/?url=
>> >>> > https%3A%2F%2Fgithub.co
>> >>> > >m%2Fapache%2Froyale-asjs%2Freleases%2Ftag%2Funtagged-
>> >>> > 3e7dc9305c4ad1eaa804&
>> >>> > >data=02%7C01%7Caharui%40adobe.com%7C2688068931e74b0ed20b08d56381
>> >>> > 0cae%7Cfa7
>> >>> > >b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524328276148227&
>> >>> > sdata=waf5UTV1g
>> >>> > >Rint9dmutBs6v2y7USv3KNP3dJKI7%2FzZFs%3D=0
>> >>> > >
>> >>> > >Thanks, Piotr
>> >>> > >
>> >>> > >2018-01-24 23:06 GMT+01:00 Carlos Rovira
>>:
>> >>> > >
>> >>> > >> Hi thanks Alex and Andrew,
>> >>> > >>
>> >>> > >> right now we are having such moderate impact on internet. For
>> >>> example in
>> >>> > >> twitter we have 135 followers, in facebook 40. We have the
>> >>>accounts
>> >>> open
>> >>> > >> about 15 days like the website. So we can make huge noise right
>> >>>now.
>> >>> > >>Just
>> >>> > >> letting people know we release our first release is great, but
>>we
>> >>> must
>> >>> > >> lower expectations about actual Apache Royale state since
>>although
>> >>> the
>> >>> > >> technology in in place, to make real apps it's not as friendly
>>as
>> >>> Flex,
>> >>> > >>and
>> >>> > >> we don't want people coming get frustrated about that. But this
>> >>>is a
>> >>> > >> required step in order to follow up improving royale
>> >>> > >>
>> >>> > >>
>> >>> > >>
>> >>> > >>
>> >>> > >> 2018-01-24 19:00 GMT+01:00 Andrew Wetmore
>>:
>> >>> > >>
>> >>> > >> > Tweakage: I would change this passage
>> >>> > >> >
>> >>> > >> > This release should be considered ‘beta' quality. The
>>purpose of
>> >>> this
>> >>> > >> > release is to gather feedback about the features and
>> >>>implementation
>> >>> > >> > strategies, and recruit new contributors as we grow the code
>> >>>base
>> >>> > >>into an
>> >>> > >> > SDK and tool chain that delivers the highest productivity
>> >>> developing
>> >>> > >> > applications that can run in the most places. These releases
>>may
>> >>> not
>> >>> > >> > handle production needs.
>> >>> > >> >
>> >>> > >> > to this
>> >>> > >> >
>> >>> > >> > This release should be considered ‘beta' quality. The
>>purpose of
>> >>> this
>> >>> > >> > release is to gather feedback about the features and
>> >>>implementation
>> >>> > >> > strategies, and 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.
>> >>> > >> >
>> >>> > >> > On Wed, Jan 24, 2018 at 

Re: Updating 2015 FlexJS presentation

[Andrew Wetmore]

This is nice.

Some notes:


   - NOTE that none, one or more than one answer could be right => NOTE
   that no answer, or one or more than one answer, could be right

   - Each answer must be correct on *it *own not in combination with other
   answers. => Each answer must be correct on* its own,* not in combination
   with other answers.

   - improvemnets => improvement

   - Apache only produces source releases and users can only be directed to
   official *voted on releases*. => Apache only produces source releases
   and users can only be directed to official releases that have been voted on.
   - Sorry that's not quite right. *Here some* help so you'll get it right
   next time. => Sorr*y, *that's not quite right. Here *is *some help...
   - .and *copyright *from 3rd party => and copyrights from 3rd party

   - Once released what must the PMC do? => Once *a new version of the
   project has been* released, what must the PMC do?

   - *Released *need to published => Releases need to be published

I saw the same question twice, even though I had answered it correctly the
first time.

On Wed, Jan 24, 2018 at 9:55 PM, Justin Mclean 
wrote:

> Hi,
>
> I also have a couple of Royale examples on GitHub that might be useful.
> [1][2] They are not complex applications but they are a little more that a
> basic hello world app. You can see them working here. [3][4]
>
> For the Quiz (I just put up today) I may of made mistakes and it likely
> some words and sentences probably need correcting. Proof readers and PRs
> welcome.
>
> BTW it doesn’t save your scores anywhere so if you get a question wrong
> only you will know but hopefully you might learn something :-)
>
> Thanks,
> Justin
>
> 1. https://github.com/justinmclean/ApacheLogos
> 2. https://github.com/justinmclean/ApacheQuiz
> 3. https://rawgit.com/justinmclean/ApacheLogos/master/compiled/index.html
> 4. https://rawgit.com/justinmclean/ApacheQuiz/master/compiled/index.html




-- 
Andrew Wetmore

http://cottage14.blogspot.com/

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

[Piotr Zarzycki]

It looks like we can attach those files to GitHub. I see there is such
option. Do you want me to download and attach them ?

2018-01-25 10:49 GMT+01:00 Alex Harui :

> Hi Piotr,
>
> Was there any way to add the -bin files to GitHub somewhere?  Linking to
> the binaries on the mirrors is ok, but I was hoping we could find a
> non-mirrored URL so we can instruct folks to use npm with the url to the
> binaries.  If they use the mirrors, it is a two-step process, they have to
> go to the mirror and pick a mirror and use that with npm.
>
> Maybe I should put a copy on the CI server.
>
> Thoughts?
> -Alex
>
>
>
> On 1/24/18, 10:55 PM, "Piotr Zarzycki"  wrote:
>
> >I have published ->
> >https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fgithub.co
> >m%2Fapache%2Froyale-asjs%2Freleases%2Ftag%2Fapache-
> royale-0.9.0=02%7C
> >01%7Caharui%40adobe.com%7C6dd26e630781475a026b08d563c0
> adf9%7Cfa7b1b5a7b344
> >38794aed2c178decee1%7C0%7C0%7C636524601572591983=
> 3wGTQuEfLQnV6LHZr0h
> >FyZ1MVnRnSb5BwAyoWQm1Dqk%3D=0
> >
> >2018-01-25 7:18 GMT+01:00 Piotr Zarzycki :
> >
> >> Alex,
> >>
> >> We can edit text later, that is not a problem.
> >>
> >> Piotr
> >>
> >> 2018-01-25 0:35 GMT+01:00 OmPrakash Muppirala :
> >>
> >>> I think it is perfectly fine to announce without npm support.  We can
> >>>add
> >>> it in our next release.
> >>>
> >>> Thanks,
> >>> Om
> >>>
> >>> On Wed, Jan 24, 2018 at 3:31 PM, Alex Harui 
> >>> wrote:
> >>>
> >>> > If we can edit the text later, then IMO, go ahead and publish.
> >>> >
> >>> > If not, we might want to wait to hear from more folks.
> >>> >
> >>> > -Alex
> >>> >
> >>> > On 1/24/18, 3:20 PM, "Piotr Zarzycki" 
> >>> wrote:
> >>> >
> >>> > >I have created release on GitHub - It's unpublished [1] - Do we
> >>>want to
> >>> > >add
> >>> > >something more there ?
> >>> > >
> >>> > >[1]
> >>> > >https://na01.safelinks.protection.outlook.com/?url=
> >>> > https%3A%2F%2Fgithub.co
> >>> > >m%2Fapache%2Froyale-asjs%2Freleases%2Ftag%2Funtagged-
> >>> > 3e7dc9305c4ad1eaa804&
> >>> > >data=02%7C01%7Caharui%40adobe.com%7C2688068931e74b0ed20b08d56381
> >>> > 0cae%7Cfa7
> >>> > >b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524328276148227&
> >>> > sdata=waf5UTV1g
> >>> > >Rint9dmutBs6v2y7USv3KNP3dJKI7%2FzZFs%3D=0
> >>> > >
> >>> > >Thanks, Piotr
> >>> > >
> >>> > >2018-01-24 23:06 GMT+01:00 Carlos Rovira :
> >>> > >
> >>> > >> Hi thanks Alex and Andrew,
> >>> > >>
> >>> > >> right now we are having such moderate impact on internet. For
> >>> example in
> >>> > >> twitter we have 135 followers, in facebook 40. We have the
> >>>accounts
> >>> open
> >>> > >> about 15 days like the website. So we can make huge noise right
> >>>now.
> >>> > >>Just
> >>> > >> letting people know we release our first release is great, but we
> >>> must
> >>> > >> lower expectations about actual Apache Royale state since although
> >>> the
> >>> > >> technology in in place, to make real apps it's not as friendly as
> >>> Flex,
> >>> > >>and
> >>> > >> we don't want people coming get frustrated about that. But this
> >>>is a
> >>> > >> required step in order to follow up improving royale
> >>> > >>
> >>> > >>
> >>> > >>
> >>> > >>
> >>> > >> 2018-01-24 19:00 GMT+01:00 Andrew Wetmore :
> >>> > >>
> >>> > >> > Tweakage: I would change this passage
> >>> > >> >
> >>> > >> > This release should be considered ‘beta' quality. The purpose of
> >>> this
> >>> > >> > release is to gather feedback about the features and
> >>>implementation
> >>> > >> > strategies, and recruit new contributors as we grow the code
> >>>base
> >>> > >>into an
> >>> > >> > SDK and tool chain that delivers the highest productivity
> >>> developing
> >>> > >> > applications that can run in the most places. These releases may
> >>> not
> >>> > >> > handle production needs.
> >>> > >> >
> >>> > >> > to this
> >>> > >> >
> >>> > >> > This release should be considered ‘beta' quality. The purpose of
> >>> this
> >>> > >> > release is to gather feedback about the features and
> >>>implementation
> >>> > >> > strategies, and 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.
> >>> > >> >
> >>> > >> > On Wed, Jan 24, 2018 at 1:49 PM, Alex Harui
> >>>  >>> > >
> >>> > >> > wrote:
> >>> > >> >
> >>> > >> > > Please comment on the draft below. Quite frankly, I'm not
> >>>clear
> >>> how
> >>> > >> much
> >>> > >> > > noise we want to make about 0.9.0.  Looks like NPM is not
> >>> working at
> >>> > >> all.
> >>> > >> > >
> >>> > >> > > Thoughts?
> >>> > >> > > -Alex
> 

[DRAFT2][ANNOUNCE] Apache Royale 0.9.0 Released

[Alex Harui]

Please comment on the draft below which tries to implement feedback on the
first draft.  I'm thinking we should wait to see if Om can find a way to
publish the artifacts via NPM or find a non-mirrored URL for the NPM
package before we finalize instructions about NPM and send out the
announcement.

Thoughts?
-Alex

---

The Apache Royale community is pleased to announce the release of Apache
Royale 0.9.0.

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.

(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 

Windows:

  npm install -g 

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: [DRAFT] [ANNOUNCE] Apache Royale 0.9.0 Released

[Alex Harui]

Hi Piotr,

Was there any way to add the -bin files to GitHub somewhere?  Linking to
the binaries on the mirrors is ok, but I was hoping we could find a
non-mirrored URL so we can instruct folks to use npm with the url to the
binaries.  If they use the mirrors, it is a two-step process, they have to
go to the mirror and pick a mirror and use that with npm.

Maybe I should put a copy on the CI server.

Thoughts?
-Alex



On 1/24/18, 10:55 PM, "Piotr Zarzycki"  wrote:

>I have published ->
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co
>m%2Fapache%2Froyale-asjs%2Freleases%2Ftag%2Fapache-royale-0.9.0=02%7C
>01%7Caharui%40adobe.com%7C6dd26e630781475a026b08d563c0adf9%7Cfa7b1b5a7b344
>38794aed2c178decee1%7C0%7C0%7C636524601572591983=3wGTQuEfLQnV6LHZr0h
>FyZ1MVnRnSb5BwAyoWQm1Dqk%3D=0
>
>2018-01-25 7:18 GMT+01:00 Piotr Zarzycki :
>
>> Alex,
>>
>> We can edit text later, that is not a problem.
>>
>> Piotr
>>
>> 2018-01-25 0:35 GMT+01:00 OmPrakash Muppirala :
>>
>>> I think it is perfectly fine to announce without npm support.  We can
>>>add
>>> it in our next release.
>>>
>>> Thanks,
>>> Om
>>>
>>> On Wed, Jan 24, 2018 at 3:31 PM, Alex Harui 
>>> wrote:
>>>
>>> > If we can edit the text later, then IMO, go ahead and publish.
>>> >
>>> > If not, we might want to wait to hear from more folks.
>>> >
>>> > -Alex
>>> >
>>> > On 1/24/18, 3:20 PM, "Piotr Zarzycki" 
>>> wrote:
>>> >
>>> > >I have created release on GitHub - It's unpublished [1] - Do we
>>>want to
>>> > >add
>>> > >something more there ?
>>> > >
>>> > >[1]
>>> > >https://na01.safelinks.protection.outlook.com/?url=
>>> > https%3A%2F%2Fgithub.co
>>> > >m%2Fapache%2Froyale-asjs%2Freleases%2Ftag%2Funtagged-
>>> > 3e7dc9305c4ad1eaa804&
>>> > >data=02%7C01%7Caharui%40adobe.com%7C2688068931e74b0ed20b08d56381
>>> > 0cae%7Cfa7
>>> > >b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524328276148227&
>>> > sdata=waf5UTV1g
>>> > >Rint9dmutBs6v2y7USv3KNP3dJKI7%2FzZFs%3D=0
>>> > >
>>> > >Thanks, Piotr
>>> > >
>>> > >2018-01-24 23:06 GMT+01:00 Carlos Rovira :
>>> > >
>>> > >> Hi thanks Alex and Andrew,
>>> > >>
>>> > >> right now we are having such moderate impact on internet. For
>>> example in
>>> > >> twitter we have 135 followers, in facebook 40. We have the
>>>accounts
>>> open
>>> > >> about 15 days like the website. So we can make huge noise right
>>>now.
>>> > >>Just
>>> > >> letting people know we release our first release is great, but we
>>> must
>>> > >> lower expectations about actual Apache Royale state since although
>>> the
>>> > >> technology in in place, to make real apps it's not as friendly as
>>> Flex,
>>> > >>and
>>> > >> we don't want people coming get frustrated about that. But this
>>>is a
>>> > >> required step in order to follow up improving royale
>>> > >>
>>> > >>
>>> > >>
>>> > >>
>>> > >> 2018-01-24 19:00 GMT+01:00 Andrew Wetmore :
>>> > >>
>>> > >> > Tweakage: I would change this passage
>>> > >> >
>>> > >> > This release should be considered ‘beta' quality. The purpose of
>>> this
>>> > >> > release is to gather feedback about the features and
>>>implementation
>>> > >> > strategies, and recruit new contributors as we grow the code
>>>base
>>> > >>into an
>>> > >> > SDK and tool chain that delivers the highest productivity
>>> developing
>>> > >> > applications that can run in the most places. These releases may
>>> not
>>> > >> > handle production needs.
>>> > >> >
>>> > >> > to this
>>> > >> >
>>> > >> > This release should be considered ‘beta' quality. The purpose of
>>> this
>>> > >> > release is to gather feedback about the features and
>>>implementation
>>> > >> > strategies, and 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.
>>> > >> >
>>> > >> > On Wed, Jan 24, 2018 at 1:49 PM, Alex Harui
>>> >> > >
>>> > >> > wrote:
>>> > >> >
>>> > >> > > Please comment on the draft below. Quite frankly, I'm not
>>>clear
>>> how
>>> > >> much
>>> > >> > > noise we want to make about 0.9.0.  Looks like NPM is not
>>> working at
>>> > >> all.
>>> > >> > >
>>> > >> > > Thoughts?
>>> > >> > > -Alex
>>> > >> > >
>>> > >> > > ---
>>> > >> > >
>>> > >> > > The Apache Royale community is pleased to announce the
>>>release of
>>> > >> Apache
>>> > >> > > Royale 0.9.0.
>>> > >> > >
>>> > >> > > 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 

Re: Migrating existing FlexJS documentation to Royale

[Justin Mclean]

Hi,

Or possibly you could just link the markdown content  to "src/site/markdown” 
(ln -s ../../../royale-docs markdown from /src/site is royale-asjs) [1] and do 
a “mvn site site:stage” to test locally and a "mvn site-deploy” to deploy if 
you have permission. I believe Chris set this all of this up a while back. I 
think you need to add and set absoluteResourceURL to site.xml.

Might be worth a try anyway if you want a quick and easy way to do this.

Thanks,
Justin

[1] 
https://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html