Re: [PR] Cascading style sheets reference [royale-docs]

[Andrew Wetmore]

I do not believe this has been donated. The material would need a rewrite
in the committer's own words, so that the result is clearly not a copy from
the earlier material.

I would be happy to help with refreshing the text and examples, if the
substance of the pull request is correct.

a

On Wed, Apr 24, 2024 at 4:15 PM joshtynjala (via GitHub) 
wrote:

>
> joshtynjala commented on PR #30:
> URL: https://github.com/apache/royale-docs/pull/30#issuecomment-2075661869
>
>Some of the content in this PR appears to be copied from the Using
> Adobe Flex documentation, which is licensed CC BY-NC-SA 3.0.
>
>
> https://web.archive.org/web/20160322180947/http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf62883-7ff2.html
>
>According to [ASF 3rd Party License Policy](
> https://www.apache.org/legal/resolved.html#asf-3rd-party-license-policy)](https://www.apache.org/legal/resolved.html),
> we (unfortunately) may not be able to include documentation derived from a
> CC **NC** license:
>
>> You may NOT include the following licenses within Apache products:
>> Creative Commons Non-Commercial variants
>
>Unless a fellow contributor in Flex/Royale knows that Adobe donated
> "Using Flex" to the ASF with Apache 2.0 or another compatible license?
>
>
> --
> This is an automated message from the Apache Git Service.
> To respond to the message, please log on to GitHub and use the
> URL above to go to the specific comment.
>
> To unsubscribe, e-mail: dev-unsubscr...@royale.apache.org
>
> For queries about this service, please contact Infrastructure at:
> us...@infra.apache.org
>
>

-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: Royale AS3 with Starling Framework

[Andrew Wetmore]

That's as cute as anything. Subject for a blog post? I will write it if you
help me understand this.

<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
Virus-free.www.avast.com
<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Mon, Sep 25, 2023 at 4:50 PM Josh Tynjala 
wrote:

> Hi Royale community,
>
> As you may know, I'm a big fan of finding ways for Royale's AS3 to JS
> compiler to work with emulated Flash APIs. Today, I'm sharing a little
> project created by Fancy2209 that uses AS3/Royale to build an app running
> on the GPU-accelerated Starling Framework.
>
> Here's the "Flappy Starling" sample, compiled from AS3 to JS, running on
> top of OpenFL and Starling — in your web browser!
>
> https://fancy2209.github.io/FlappyStarlingRoyale/
>
> Source code available here:
>
> https://github.com/Fancy2209/Flappy-Starling-Royale
>
> --
> Josh Tynjala
>


-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: Rich media in Royale

[Andrew Wetmore]

ia.westw...@nd.edu.au<mailto:virginia.westw...@nd.edu.au
> ><mailto:virginia.westw...@nd.edu.au<mailto:virginia.westw...@nd.edu.au>>>
>
> Disclaimer
>
> The information contained in this communication from the sender is
> confidential. It is intended solely for use by the recipient and others
> authorized to receive it. If you are not the recipient, you are hereby
> notified that any disclosure, copying, distribution or taking action in
> relation of the contents of this information is strictly prohibited and may
> be unlawful.
>
> This email has been scanned for viruses and malware, and may have been
> automatically archived by Mimecast Ltd, an innovator in Software as a
> Service (SaaS) for business. Providing a safer and more useful place for
> your human generated data. Specializing in; Security, archiving and
> compliance. To find out more visit the Mimecast website.
>
>
>
>
> --
>
> Frédéric Gilli
>
> mob.0668542622
>
> http://www.cristallium.com
>
> [cid:image001.png@01D9ECB5.403DADC0]<http://www.cristallium.com/>
>
>
>

-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.10 released

[Andrew Wetmore]

Should the documentation link go to the docs page on the website [1],
instead of to a GitHub repo?

[1] https://royale.apache.org/docs/

On Wed, May 31, 2023 at 3:18 AM Yishay Weiss  wrote:

> Here's another version with mirrors replaced and a footnote on npm version
> confision. Thoughts?
>
> -
>
> The Apache Royale community is pleased to announce the release of Apache
> Royale 0.9.10.
>
> The Apache Royale project is the next generation of the Apache Flex SDK. It
> lets developers use MXML and ActionScript 3 to generate HTML/JS/CSS
> applications which can run natively in browsers. The cross-compiled code
> can also run on platforms like Electron or Apache Cordova (Adobe PhoneGap)
> to build mobile applications.
>
> This release should be considered ‘beta’ quality, although we’re very close
> to a 1.0 release and we have many applications in production at this point.
> The purpose of this release is to continue to gather feedback about
> Royale’s features and the project’s 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, however, may
> not handle all production needs.
>
> Changes in 0.9.10:
>
> Apache Royale Framework 0.9.10:
>
> https://github.com/apache/royale-asjs/blob/apache-royale-0.9.10/RELEASE_NOTES.md
> Apache Royale Compiler 0.9.10:
>
> https://github.com/apache/royale-compiler/blob/apache-royale-0.9.10/RELEASE_NOTES.md
>
> 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 [hidden email].
> For questions and feedback on the development of the source code in the
> release, send email to [hidden email].
>
> Apache Royale is available in source and binary form from the
> ASF Content Distribution Network (CDN):
>
> Source:
>
> https://www.apache.org/dyn/closer.lua/royale/0.9.10/apache-royale-0.9.10-src.tar.gz
>
>
> https://www.apache.org/dyn/closer.lua/royale/0.9.10/apache-royale-0.9.10-src.zip
>
> Binary:
>
> https://www.apache.org/dyn/closer.lua/royale/0.9.10/binaries/apache-royale-0.9.10-bin-js.tar.gz
>
> https://www.apache.org/dyn/closer.lua/royale/0.9.10/binaries/apache-royale-0.9.10-bin-js.zip
>
> Binary with SWF support:
>
> https://www.apache.org/dyn/closer.lua/royale/0.9.10/binaries/apache-royale-0.9.10-bin-js-swf.tar.gz
>
> https://www.apache.org/dyn/closer.lua/royale/0.9.10/binaries/apache-royale-0.9.10-bin-js-swf.zip
>
> When downloading from a CDN site, please remember to verify the
> downloads using signatures or MD5 hashes.
>
> The binary packages can also be installed via NPM [1].
>
> Mac:
> sudo npm install @apache-royale/royale-js -g
>
> Or for SWF Support:
> sudo npm install @apache-royale/royale-js-swf -g
>
> Windows:
> npm install @apache-royale/royale-js -g
>
> Or for SWF Support:
> npm install @apache-royale/royale-js-swf -g
>
> See the README for more information. The language reference (ASDoc) is
> here: https://royale.apache.org/asdoc/
>
> Additional documentation is here: https://apache.github.io/royale-docs/
>
> The documentation is still a work in progress. Volunteers are welcome to
> help improve it. Visit https://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
>
> [1] Please note that version number on the NPM registry is 0.9.11, but it
> refers to Apache Royale 0.9.10. We
> will try to fix that for the next release.
>
>
> 
> From: Andrew Wetmore 
> Sent: Sunday, May 28, 2023 3:57 PM
> To: dev@royale.apache.org 
> Subject: Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.10 released
>
> No, the links seem to be valid.
>
> On Sun, May 28, 2023 at 9:52 AM Yishay Weiss 
> wrote:
>
> > Thanks, Andrew. Do the links need to reflect the transition from mirrors
> > somehow?
> > 
> > From: Andrew Wetmore 
> > Sent: Sunday, May 28, 2023 3:44 PM
> > To: dev@royale.apache.org 
> > Subject: Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.10 released
> >
> > I think this is very clear and hopeful.
> >
> > Two notes: The ASF has retired its mirror system, and is moving away from
> > prominent use of "Apache", usually in favour of "The ASF". This is in
> > response to concerns about appropriation of

Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.10 released

[Andrew Wetmore]

No, the links seem to be valid.

On Sun, May 28, 2023 at 9:52 AM Yishay Weiss  wrote:

> Thanks, Andrew. Do the links need to reflect the transition from mirrors
> somehow?
> 
> From: Andrew Wetmore 
> Sent: Sunday, May 28, 2023 3:44 PM
> To: dev@royale.apache.org 
> Subject: Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.10 released
>
> I think this is very clear and hopeful.
>
> Two notes: The ASF has retired its mirror system, and is moving away from
> prominent use of "Apache", usually in favour of "The ASF". This is in
> response to concerns about appropriation of images (feather) and mythos
> (noble Indians) without consultation or agreement with the indigenous
> people involved. A committee of the ASF Board is working on what of the
> Foundation's branding can and should change, and how to do it with
> the least disruption, so we will need to keep an eye out for their eventual
> decision.
>
> In the meantime, two sentences should change:
>
> 1. Apache Royale is available in source and binary form from the Apache
> mirrors:
> should be
> Apache Royale is available in source and binary form from the ASF Content
> Distribution Network (CDN):
>
> 2. When downloading from a mirror site, please remember to verify the
> downloads using signatures or MD5 hashes.
> should be
> When downloading from the CDN, please remember to verify the downloads
> using signatures or MD5 hashes.
>
> a
>
> On Sun, May 28, 2023 at 9:22 AM Yishay Weiss 
> wrote:
>
> > The Apache Royale community is pleased to announce the release of Apache
> > Royale 0.9.10.
> >
> > The Apache Royale project is the next generation of the Apache Flex SDK.
> It
> > lets developers use MXML and ActionScript 3 to generate HTML/JS/CSS
> > applications which can run natively in browsers. The cross-compiled code
> > can also run on platforms like Electron or Apache Cordova (Adobe
> PhoneGap)
> > to build mobile applications.
> >
> > This release should be considered ‘beta’ quality, although we’re very
> close
> > to a 1.0 release and we have many applications in production at this
> point.
> > The purpose of this release is to continue to gather feedback about
> > Royale’s features and the project’s 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, however, may
> > not handle all production needs.
> >
> > Changes in 0.9.10:
> >
> > Apache Royale Framework 0.9.10:
> >
> >
> https://github.com/apache/royale-asjs/blob/apache-royale-0.9.10/RELEASE_NOTES.md
> > Apache Royale Compiler 0.9.10:
> >
> >
> https://github.com/apache/royale-compiler/blob/apache-royale-0.9.10/RELEASE_NOTES.md
> >
> > 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 [hidden email].
> > For questions and feedback on the development of the source code in the
> > release, send email to [hidden email].
> >
> > Apache Royale is available in source and binary form from the Apache
> > mirrors:
> >
> > Source:
> >
> >
> https://www.apache.org/dyn/closer.lua/royale/0.9.10/apache-royale-0.9.10-src.tar.gz
> >
> >
> >
> https://www.apache.org/dyn/closer.lua/royale/0.9.10/apache-royale-0.9.10-src.zip
> >
> > Binary:
> >
> >
> https://www.apache.org/dyn/closer.lua/royale/0.9.10/binaries/apache-royale-0.9.10-bin-js.tar.gz
> >
> >
> https://www.apache.org/dyn/closer.lua/royale/0.9.10/binaries/apache-royale-0.9.10-bin-js.zip
> >
> > Binary with SWF support:
> >
> >
> https://www.apache.org/dyn/closer.lua/royale/0.9.10/binaries/apache-royale-0.9.10-bin-js-swf.tar.gz
> >
> >
> https://www.apache.org/dyn/closer.lua/royale/0.9.10/binaries/apache-royale-0.9.10-bin-js-swf.zip
> >
> > When downloading from a mirror site, please remember to verify the
> > downloads using signatures or MD5 hashes.
> >
> > The binary packages can also be installed via NPM.
> >
> > Mac:
> > sudo npm install @apache-royale/royale-js -g
> >
> > Or for SWF Support:
> > sudo npm install @apache-royale/royale-js-swf -g
> >
> > Windows:
> > npm install @apache-royale/royale-js -g
> >
> > Or for

Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.10 released

[Andrew Wetmore]

I think this is very clear and hopeful.

Two notes: The ASF has retired its mirror system, and is moving away from
prominent use of "Apache", usually in favour of "The ASF". This is in
response to concerns about appropriation of images (feather) and mythos
(noble Indians) without consultation or agreement with the indigenous
people involved. A committee of the ASF Board is working on what of the
Foundation's branding can and should change, and how to do it with
the least disruption, so we will need to keep an eye out for their eventual
decision.

In the meantime, two sentences should change:

1. Apache Royale is available in source and binary form from the Apache
mirrors:
should be
Apache Royale is available in source and binary form from the ASF Content
Distribution Network (CDN):

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

a

On Sun, May 28, 2023 at 9:22 AM Yishay Weiss  wrote:

> The Apache Royale community is pleased to announce the release of Apache
> Royale 0.9.10.
>
> The Apache Royale project is the next generation of the Apache Flex SDK. It
> lets developers use MXML and ActionScript 3 to generate HTML/JS/CSS
> applications which can run natively in browsers. The cross-compiled code
> can also run on platforms like Electron or Apache Cordova (Adobe PhoneGap)
> to build mobile applications.
>
> This release should be considered ‘beta’ quality, although we’re very close
> to a 1.0 release and we have many applications in production at this point.
> The purpose of this release is to continue to gather feedback about
> Royale’s features and the project’s 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, however, may
> not handle all production needs.
>
> Changes in 0.9.10:
>
> Apache Royale Framework 0.9.10:
>
> https://github.com/apache/royale-asjs/blob/apache-royale-0.9.10/RELEASE_NOTES.md
> Apache Royale Compiler 0.9.10:
>
> https://github.com/apache/royale-compiler/blob/apache-royale-0.9.10/RELEASE_NOTES.md
>
> 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 [hidden email].
> For questions and feedback on the development of the source code in the
> release, send email to [hidden email].
>
> Apache Royale is available in source and binary form from the Apache
> mirrors:
>
> Source:
>
> https://www.apache.org/dyn/closer.lua/royale/0.9.10/apache-royale-0.9.10-src.tar.gz
>
>
> https://www.apache.org/dyn/closer.lua/royale/0.9.10/apache-royale-0.9.10-src.zip
>
> Binary:
>
> https://www.apache.org/dyn/closer.lua/royale/0.9.10/binaries/apache-royale-0.9.10-bin-js.tar.gz
>
> https://www.apache.org/dyn/closer.lua/royale/0.9.10/binaries/apache-royale-0.9.10-bin-js.zip
>
> Binary with SWF support:
>
> https://www.apache.org/dyn/closer.lua/royale/0.9.10/binaries/apache-royale-0.9.10-bin-js-swf.tar.gz
>
> https://www.apache.org/dyn/closer.lua/royale/0.9.10/binaries/apache-royale-0.9.10-bin-js-swf.zip
>
> When downloading from a mirror site, please remember to verify the
> downloads using signatures or MD5 hashes.
>
> The binary packages can also be installed via NPM.
>
> Mac:
> sudo npm install @apache-royale/royale-js -g
>
> Or for SWF Support:
> sudo npm install @apache-royale/royale-js-swf -g
>
> Windows:
> npm install @apache-royale/royale-js -g
>
> Or for SWF Support:
> npm install @apache-royale/royale-js-swf -g
>
> See the README for more information. The language reference (ASDoc) is
> here: https://royale.apache.org/asdoc/
>
> Additional documentation is here: https://apache.github.io/royale-docs/
>
> The documentation is still a work in progress. Volunteers are welcome to
> help improve it. Visit https://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
>
>

-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Speaking at the next ASF event

[Andrew Wetmore]

Hi:

The ASF has announced "Community over Code 2023" and is calling for
presentation tracks. Would we like to put together our own track of
presentations? We have to let Rich Bowen know by two days from now, if so.
Otherwise, once we see what the tracks are, we could see if there is a
place among them for Royale presentations.

So far I have seen Fintech, Search, Big Data, and IoT tracks. I honestly do
not know where Royale talks would go, if not in their own track.

a

-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: Welcome Hugo Ferreira to Apache Royale's PMC

[Andrew Wetmore]

Yay hooray!

On Thu, Oct 27, 2022 at 10:22 AM Yishay Weiss 
wrote:

> Hi All,
>
> It is with great pleasure that I announce that the Apache Royale PMC
> members have voted in Hugo Ferreira to the PMC.  Please join us in
> welcoming him. This is in recognition of Hugo’s great work in helping out
> with Apache Royale's Jewel component set, among other things.
>
>
> Regards,
> Yishay
> (On behalf of Apache Royale PMC)
>
>

-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: Introducing asformat

[Andrew Wetmore]

 > --insert-space-anonymous-function-keyword: Controls whether a space is
> > inserted between the function keyword and the following ( open
> parenthesis,
> > if the function is anonymous (if it doesn't have a name). (Default:
> false)
> > >
> > > --insert-space-binary-operators: Controls whether a space is inserted
> > before and after binary operators (like +, -, *, /, &&, ||, etc.)
> (Default:
> > true)
> > >
> > > --insert-space-comma-delimiter: Controls whether a space is inserted
> > after comma delimiters in Object and Array literals. (Default: true)
> > >
> > > --collapse-empty-blocks: Controls whether empty blocks are collapsed so
> > that the opening and closing curly brace are both on the same line or
> not.
> > (Default: false)
> > >
> > > --max-preserve-new-lines: Specify the maximum number of new line
> > characters that are allowed to appear consecutively. (Default: 2)
> > >
> > > --semicolons: Controls how semicolons are handled. Valid values are
> > insert, remove, and ignore. Insert means that missing semicolons are
> > inserted. Remove means that all semicolons are removed, and ignore means
> > that there is no change to semicolons in the file. (Default: insert)
> > >
> > > Additional notes:
> > >
> > > If neither --write-files nor --list-files is specified, the formatted
> > source code is written to standard output instead.
> > >
> > > If no files are specified, asformat waits for standard input instead.
> > >
> > > --
> > > Josh Tynjala
> > > Bowler Hat LLC <https://bowlerhat.dev/>
> >
> >
>


-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: Deploy new Royale static site as-is?

[Andrew Wetmore]

Ah, thank you. Is it in the page that had the information for the WordPress
site?

a

On Tue, Sep 27, 2022 at 7:02 PM Josh Tynjala 
wrote:

> FYI — I wrote the new documentation for updating the Royale website.
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Tue, Aug 30, 2022 at 3:24 PM Andrew Wetmore 
> wrote:
>
> > If we now have a working process to maintain our website, can someone
> help
> > me update our documentation about it? This page [1] still gives guidance
> > for the WordPress site.
> >
> > a
> >
> > 1. https://github.com/apache/royale-asjs/wiki/Release-Manager-(Web-Site)
> >
> > On Mon, Aug 1, 2022 at 1:35 PM Andrew Wetmore 
> wrote:
> >
> > > The help docs for working with the Pelican website template are now up
> to
> > > date. The main page is here [1].
> > >
> > > The main changes are on the getting-started page [2] and the page about
> > > building and testing locally [3]. For the latter, there is now a
> > > downloadable tool that simplifies the local-build process.
> > >
> > > [1] https://infra.apache.org/asf-pelican.html
> > > [2] https://infra.apache.org/asf-pelican-gettingstarted.html
> > > [3] https://infra.apache.org/asf-pelican-local.html
> > >
> > > On Tue, Jul 19, 2022 at 4:42 AM Maria Jose Esteve 
> > > wrote:
> > >
> > >> +1
> > >>
> > >> Hiedra
> > >>
> > >> -Mensaje original-
> > >> De: Josh Tynjala 
> > >> Enviado el: lunes, 18 de julio de 2022 23:55
> > >> Para: Apache Royale Development 
> > >> Asunto: Deploy new Royale static site as-is?
> > >>
> > >> Hi all,
> > >>
> > >> I just created a new 11ty branch in the apache/royale-website repo,
> and
> > I
> > >> added the source files for the static site that I built with Eleventy.
> > >>
> > >> https://github.com/apache/royale-website/tree/11ty
> > >>
> > >> I made it so that Github Actions builds the site from source and
> deploys
> > >> the output to the asf-staging branch. In the asf-staging branch, I
> > added an
> > >> .asf.yaml file, which currently deploys every new commit at the
> > following
> > >> staging URL:
> > >>
> > >> https://royale-11ty.staged.apache.org/
> > >>
> > >> It would be a relatively easy change to configure this repo to deploy
> to
> > >> the production royale.apache.org website instead.
> > >>
> > >> I feel that it's better for Royale's future to have an updated website
> > >> working sooner rather than later. I propose that we move forward with
> > what
> > >> we have now, instead of waiting any longer to migrate to Pelican. I
> have
> > >> nothing against Pelican, and I'm totally okay with using it in the
> > future.
> > >> I simply think that it's better to replace the old website with
> > >> **anything** that we can update properly, since the old website
> doesn't
> > >> even mention the newest two Royale SDK releases.
> > >>
> > >> Does anyone object to moving forward with the Elventy-based site for
> > now?
> > >>
> > >> --
> > >> Josh Tynjala
> > >> Bowler Hat LLC <https://bowlerhat.dev>
> > >>
> > >
> > >
> > > --
> > > Andrew Wetmore
> > >
> > > Editor, Moose House Publications <https://moosehousepress.com/>
> > > Editor-Writer, The Apache Software Foundation <https://apache.org/>
> > >
> > >
> > >
> > >
> > >
> >
> > --
> > Andrew Wetmore
> >
> > Editor, Moose House Publications <https://moosehousepress.com/>
> > Editor-Writer, The Apache Software Foundation <https://apache.org/>
> >
>


-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: Deploy new Royale static site as-is?

[Andrew Wetmore]

If we now have a working process to maintain our website, can someone help
me update our documentation about it? This page [1] still gives guidance
for the WordPress site.

a

1. https://github.com/apache/royale-asjs/wiki/Release-Manager-(Web-Site)

On Mon, Aug 1, 2022 at 1:35 PM Andrew Wetmore  wrote:

> The help docs for working with the Pelican website template are now up to
> date. The main page is here [1].
>
> The main changes are on the getting-started page [2] and the page about
> building and testing locally [3]. For the latter, there is now a
> downloadable tool that simplifies the local-build process.
>
> [1] https://infra.apache.org/asf-pelican.html
> [2] https://infra.apache.org/asf-pelican-gettingstarted.html
> [3] https://infra.apache.org/asf-pelican-local.html
>
> On Tue, Jul 19, 2022 at 4:42 AM Maria Jose Esteve 
> wrote:
>
>> +1
>>
>> Hiedra
>>
>> -Mensaje original-
>> De: Josh Tynjala 
>> Enviado el: lunes, 18 de julio de 2022 23:55
>> Para: Apache Royale Development 
>> Asunto: Deploy new Royale static site as-is?
>>
>> Hi all,
>>
>> I just created a new 11ty branch in the apache/royale-website repo, and I
>> added the source files for the static site that I built with Eleventy.
>>
>> https://github.com/apache/royale-website/tree/11ty
>>
>> I made it so that Github Actions builds the site from source and deploys
>> the output to the asf-staging branch. In the asf-staging branch, I added an
>> .asf.yaml file, which currently deploys every new commit at the following
>> staging URL:
>>
>> https://royale-11ty.staged.apache.org/
>>
>> It would be a relatively easy change to configure this repo to deploy to
>> the production royale.apache.org website instead.
>>
>> I feel that it's better for Royale's future to have an updated website
>> working sooner rather than later. I propose that we move forward with what
>> we have now, instead of waiting any longer to migrate to Pelican. I have
>> nothing against Pelican, and I'm totally okay with using it in the future.
>> I simply think that it's better to replace the old website with
>> **anything** that we can update properly, since the old website doesn't
>> even mention the newest two Royale SDK releases.
>>
>> Does anyone object to moving forward with the Elventy-based site for now?
>>
>> --
>> Josh Tynjala
>> Bowler Hat LLC <https://bowlerhat.dev>
>>
>
>
> --
> Andrew Wetmore
>
> Editor, Moose House Publications <https://moosehousepress.com/>
> Editor-Writer, The Apache Software Foundation <https://apache.org/>
>
>
>
>
>

-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Software Bill of Materials

[Andrew Wetmore]

Hi, all.

I was reading today about SBOM [1] ('a kind of nutrition label to reduce
software supply chain risk') and wondered whether it would be very
difficult to add such a document to the Royale release assets. It seems to
be an impending requirement (or 'desirement') for released software, and I
can't imagine it would be too hard to put one together for our product.

If this seems like a good idea, I would be happy to create a draft and get
others to improve it.

[1]
https://develop.secure.software/sbom-facts-know-whats-in-software-fend-off-supply-chain-attacks

-- 
Andrew Wetmore

Editor, Moose House Publications
Editor-Writer, The Apache Software Foundation

Re: Deploy new Royale static site as-is?

[Andrew Wetmore]

The help docs for working with the Pelican website template are now up to
date. The main page is here [1].

The main changes are on the getting-started page [2] and the page about
building and testing locally [3]. For the latter, there is now a
downloadable tool that simplifies the local-build process.

[1] https://infra.apache.org/asf-pelican.html
[2] https://infra.apache.org/asf-pelican-gettingstarted.html
[3] https://infra.apache.org/asf-pelican-local.html

On Tue, Jul 19, 2022 at 4:42 AM Maria Jose Esteve  wrote:

> +1
>
> Hiedra
>
> -Mensaje original-
> De: Josh Tynjala 
> Enviado el: lunes, 18 de julio de 2022 23:55
> Para: Apache Royale Development 
> Asunto: Deploy new Royale static site as-is?
>
> Hi all,
>
> I just created a new 11ty branch in the apache/royale-website repo, and I
> added the source files for the static site that I built with Eleventy.
>
> https://github.com/apache/royale-website/tree/11ty
>
> I made it so that Github Actions builds the site from source and deploys
> the output to the asf-staging branch. In the asf-staging branch, I added an
> .asf.yaml file, which currently deploys every new commit at the following
> staging URL:
>
> https://royale-11ty.staged.apache.org/
>
> It would be a relatively easy change to configure this repo to deploy to
> the production royale.apache.org website instead.
>
> I feel that it's better for Royale's future to have an updated website
> working sooner rather than later. I propose that we move forward with what
> we have now, instead of waiting any longer to migrate to Pelican. I have
> nothing against Pelican, and I'm totally okay with using it in the future.
> I simply think that it's better to replace the old website with
> **anything** that we can update properly, since the old website doesn't
> even mention the newest two Royale SDK releases.
>
> Does anyone object to moving forward with the Elventy-based site for now?
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>


-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: Deploy new Royale static site as-is?

[Andrew Wetmore]

+1 I just have to  update the documentation and the Pelican tools will be
ready, but there is no reason not to take the updated site live right now.

a

On Mon, Jul 18, 2022 at 6:55 PM Josh Tynjala 
wrote:

> Hi all,
>
> I just created a new 11ty branch in the apache/royale-website repo, and I
> added the source files for the static site that I built with Eleventy.
>
> https://github.com/apache/royale-website/tree/11ty
>
> I made it so that Github Actions builds the site from source and deploys
> the output to the asf-staging branch. In the asf-staging branch, I added an
> .asf.yaml file, which currently deploys every new commit at the following
> staging URL:
>
> https://royale-11ty.staged.apache.org/
>
> It would be a relatively easy change to configure this repo to deploy to
> the production royale.apache.org website instead.
>
> I feel that it's better for Royale's future to have an updated website
> working sooner rather than later. I propose that we move forward with what
> we have now, instead of waiting any longer to migrate to Pelican. I have
> nothing against Pelican, and I'm totally okay with using it in the future.
> I simply think that it's better to replace the old website with
> **anything** that we can update properly, since the old website doesn't
> even mention the newest two Royale SDK releases.
>
> Does anyone object to moving forward with the Elventy-based site for now?
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>


-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: ci-builds stuck

[Andrew Wetmore]

The team was discussing it today. I will see what more I can find out

On Wed, Jul 6, 2022 at 4:33 PM ‪Yishay Weiss‬ 
wrote:

> I may be getting the build machine and the relesse or ci machine confused
> I'll try to make sense of it when I have more time. Meanwhile my ticket to
> infra has not been fruitful and maven central snapshots are a week behind.
>
> Amy ideas how to get their attention? I know some users are waiting for a
> solution.
>
> My CLT-L09. On O2.
>
>
>  Original message 
> From: Andrew Wetmore 
> Date: Wed, 6 Jul 2022, 18:47
> To: Apache Royale Development 
> Subject: Re: ci-builds stuck
>
> The details are here, including how a PMC can get access to one of the
> servers: https://cwiki.apache.org/confluence/display/INFRA/Jenkins
>
> On Wed, Jul 6, 2022 at 11:02 AM Andrew Wetmore 
> wrote:
>
> > In fact, why is anybody related to Royale paying for a builds server?
> > Infra has a ton of Jenkins servers available. I will hunt up the
> > documentation in a couple of hours.
> >
> > On Tue, Jul 5, 2022 at 9:51 AM Andrew Wetmore 
> wrote:
> >
> >> Do we all have a way of contributing toward the cost of the Jenkins
> >> server, if we choose to?
> >>
> >> On Tue, Jul 5, 2022 at 5:03 AM Yishay Weiss 
> >> wrote:
> >>
> >>> Hi All,
> >>>
> >>> I believe for 5 days are changes have not been propagated to Maven
> >>> central.
> >>>
> >>> This shows a job  that’s stuck [1] and is preventing new jobs from
> >>> running. I’m not sure if these builds are pushed to Maven central, but
> it’s
> >>> worth looking at this and making sure it’s running. I tried
> terminating the
> >>> blocking job but that did not seem to work. Maybe the CI server needs
> to be
> >>> restarted?
> >>>
> >>> Also, our Microsoft powered Jenkins server [2] seems to be down. It
> >>> could be Alex has run out of credits again. We should really take this
> over
> >>> from him as it’s unfair that he has to pay for the CI credits from him
> own
> >>> money. I have created an Azure subscription for this purpose (Apache
> >>> funded, just like Alex’s), but have not found the time to migrate the
> jobs
> >>> yet. If somebody can help me do that it might speed up this transition.
> >>>
> >>> Thoughts?
> >>>
> >>> Yishay
> >>>
> >>> [1] Royale-asjs [Jenkins] (apache.org)<
> >>> https://ci-builds.apache.org/job/royale/job/Royale-asjs/>
> >>> [2] apacheroyaleci2.westus2.cloudapp.azure.com<
> >>> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/>
> >>>
> >>>
> >>
> >> --
> >> Andrew Wetmore
> >>
> >> Editor, Moose House Publications <https://moosehousepress.com/>
> >> Editor-Writer, The Apache Software Foundation <https://apache.org/>
> >>
> >>
> >>
> >>
> >>
> >
> > --
> > Andrew Wetmore
> >
> > Editor, Moose House Publications <https://moosehousepress.com/>
> > Editor-Writer, The Apache Software Foundation <https://apache.org/>
> >
> >
> >
> >
> >
>
> --
> Andrew Wetmore
>
> Editor, Moose House Publications <https://moosehousepress.com/>
> Editor-Writer, The Apache Software Foundation <https://apache.org/>
>
>

-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: ci-builds stuck

[Andrew Wetmore]

The details are here, including how a PMC can get access to one of the
servers: https://cwiki.apache.org/confluence/display/INFRA/Jenkins

On Wed, Jul 6, 2022 at 11:02 AM Andrew Wetmore  wrote:

> In fact, why is anybody related to Royale paying for a builds server?
> Infra has a ton of Jenkins servers available. I will hunt up the
> documentation in a couple of hours.
>
> On Tue, Jul 5, 2022 at 9:51 AM Andrew Wetmore  wrote:
>
>> Do we all have a way of contributing toward the cost of the Jenkins
>> server, if we choose to?
>>
>> On Tue, Jul 5, 2022 at 5:03 AM Yishay Weiss 
>> wrote:
>>
>>> Hi All,
>>>
>>> I believe for 5 days are changes have not been propagated to Maven
>>> central.
>>>
>>> This shows a job  that’s stuck [1] and is preventing new jobs from
>>> running. I’m not sure if these builds are pushed to Maven central, but it’s
>>> worth looking at this and making sure it’s running. I tried terminating the
>>> blocking job but that did not seem to work. Maybe the CI server needs to be
>>> restarted?
>>>
>>> Also, our Microsoft powered Jenkins server [2] seems to be down. It
>>> could be Alex has run out of credits again. We should really take this over
>>> from him as it’s unfair that he has to pay for the CI credits from him own
>>> money. I have created an Azure subscription for this purpose (Apache
>>> funded, just like Alex’s), but have not found the time to migrate the jobs
>>> yet. If somebody can help me do that it might speed up this transition.
>>>
>>> Thoughts?
>>>
>>> Yishay
>>>
>>> [1] Royale-asjs [Jenkins] (apache.org)<
>>> https://ci-builds.apache.org/job/royale/job/Royale-asjs/>
>>> [2] apacheroyaleci2.westus2.cloudapp.azure.com<
>>> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/>
>>>
>>>
>>
>> --
>> Andrew Wetmore
>>
>> Editor, Moose House Publications <https://moosehousepress.com/>
>> Editor-Writer, The Apache Software Foundation <https://apache.org/>
>>
>>
>>
>>
>>
>
> --
> Andrew Wetmore
>
> Editor, Moose House Publications <https://moosehousepress.com/>
> Editor-Writer, The Apache Software Foundation <https://apache.org/>
>
>
>
>
>

-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: ci-builds stuck

[Andrew Wetmore]

In fact, why is anybody related to Royale paying for a builds server? Infra
has a ton of Jenkins servers available. I will hunt up the documentation in
a couple of hours.

On Tue, Jul 5, 2022 at 9:51 AM Andrew Wetmore  wrote:

> Do we all have a way of contributing toward the cost of the Jenkins
> server, if we choose to?
>
> On Tue, Jul 5, 2022 at 5:03 AM Yishay Weiss 
> wrote:
>
>> Hi All,
>>
>> I believe for 5 days are changes have not been propagated to Maven
>> central.
>>
>> This shows a job  that’s stuck [1] and is preventing new jobs from
>> running. I’m not sure if these builds are pushed to Maven central, but it’s
>> worth looking at this and making sure it’s running. I tried terminating the
>> blocking job but that did not seem to work. Maybe the CI server needs to be
>> restarted?
>>
>> Also, our Microsoft powered Jenkins server [2] seems to be down. It could
>> be Alex has run out of credits again. We should really take this over from
>> him as it’s unfair that he has to pay for the CI credits from him own
>> money. I have created an Azure subscription for this purpose (Apache
>> funded, just like Alex’s), but have not found the time to migrate the jobs
>> yet. If somebody can help me do that it might speed up this transition.
>>
>> Thoughts?
>>
>> Yishay
>>
>> [1] Royale-asjs [Jenkins] (apache.org)<
>> https://ci-builds.apache.org/job/royale/job/Royale-asjs/>
>> [2] apacheroyaleci2.westus2.cloudapp.azure.com<
>> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/>
>>
>>
>
> --
> Andrew Wetmore
>
> Editor, Moose House Publications <https://moosehousepress.com/>
> Editor-Writer, The Apache Software Foundation <https://apache.org/>
>
>
>
>
>

-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: Developing new Royale website with Pelican

[Andrew Wetmore]

Hi, colleagues:

I am happy to tell you that the Infra team has been able to repair and
strengthen the Pelican template, so that it now works for both live and
offline builds. I need to update the documentation a bit, especially the
instructions for building locally, and then I think we will be good to have
Josh add his content for the refreshed website to the template framework
and see what happens.

I should have the documentation ready for that experiment tomorrow, or
Thursday at the latest.

a

On Sun, Jun 26, 2022 at 1:16 PM Harbs  wrote:

> Looks great!
>
> > On Jun 24, 2022, at 6:46 PM, Josh Tynjala 
> wrote:
> >
> > By the way, if anyone is interested in seeing my progress on the
> website, I
> > just uploaded a build here:
> >
> > https://royale.bowlerhat.dev/
> >
> > This is currently using the Eleventy static site generator.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
> >
> > On Thu, Jun 23, 2022 at 9:10 AM Josh Tynjala 
> > wrote:
> >
> >> This is a thread to discuss the conversion of the current site away from
> >> the WordPress setup we've been using to Pelican, a static site generator
> >> recommended by Infra.
> >>
> >> --
> >> Josh Tynjala
> >> Bowler Hat LLC <https://bowlerhat.dev>
> >>
>
>

-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: ci-builds stuck

[Andrew Wetmore]

Do we all have a way of contributing toward the cost of the Jenkins server,
if we choose to?

On Tue, Jul 5, 2022 at 5:03 AM Yishay Weiss  wrote:

> Hi All,
>
> I believe for 5 days are changes have not been propagated to Maven central.
>
> This shows a job  that’s stuck [1] and is preventing new jobs from
> running. I’m not sure if these builds are pushed to Maven central, but it’s
> worth looking at this and making sure it’s running. I tried terminating the
> blocking job but that did not seem to work. Maybe the CI server needs to be
> restarted?
>
> Also, our Microsoft powered Jenkins server [2] seems to be down. It could
> be Alex has run out of credits again. We should really take this over from
> him as it’s unfair that he has to pay for the CI credits from him own
> money. I have created an Azure subscription for this purpose (Apache
> funded, just like Alex’s), but have not found the time to migrate the jobs
> yet. If somebody can help me do that it might speed up this transition.
>
> Thoughts?
>
> Yishay
>
> [1] Royale-asjs [Jenkins] (apache.org)<
> https://ci-builds.apache.org/job/royale/job/Royale-asjs/>
> [2] apacheroyaleci2.westus2.cloudapp.azure.com<
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/>
>
>

-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: Developing new Royale website with Pelican

[Andrew Wetmore]

It looks lovely and resolves quickly.

On Fri, Jun 24, 2022 at 12:46 PM Josh Tynjala 
wrote:

> By the way, if anyone is interested in seeing my progress on the website, I
> just uploaded a build here:
>
> https://royale.bowlerhat.dev/
>
> This is currently using the Eleventy static site generator.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Thu, Jun 23, 2022 at 9:10 AM Josh Tynjala 
> wrote:
>
> > This is a thread to discuss the conversion of the current site away from
> > the WordPress setup we've been using to Pelican, a static site generator
> > recommended by Infra.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
>


-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: Developing new Royale website with Pelican

[Andrew Wetmore]

The problem at the moment is that there is a significant issue in the
Apache build structure. Infra is working to resolve that. Then we will
update both the template and the instructions for using it. THEN everything
will flow again.

We will be able to build and test locally, but not for a long week. In the
meantime Royale can add content to the royale-pelican-website repo and see
what happens in the staging site. Obviously less than ideal, but leading
toward a solution that is tightly integrated with the build process

Royale could, for the duration of this awkward period, let you move ahead
with your work to test out whether Pelican can provide a site we like the
look of, and the rest of us can restrain ourselves from making
contributions. So the staging site would effectively be your local
test site.

Or, as you say, Royale can evaluate other static site creators. Which will
also encounter the current issue in the build system.

a

On Thu, Jun 23, 2022 at 1:19 PM Josh Tynjala 
wrote:

> Continuing a discussion from the private@ thread that doesn't need to be
> private.
>
> I find that working on web pages requires tons of minor tweaks and
> experimentation with styles and things, which will take way more time if I
> need to commit and push it all. Additionally, I'd rather not flood the
> commits mailing list with all of this unnecessary noise when I should be
> able to do my debugging locally. Not to mention that I'll need to figure
> out things like Pelican's way of collecting blog posts to display in
> chronological order (including generating RSS feeds automatically) — which
> I think is safe to predict won't work on my first few tries.
>
> To be clear, if I can't test locally, I'm a strong -1 on using Pelican. If
> Pelican isn't easy to set up and use locally, we can find a better
> static site generator.
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>

Re: Where's the repo where I can checkout the current Royale website?

[Andrew Wetmore]

I THINK this is the git repo:
https://github.com/apache/royale-website/tree/asf-site

On Mon, Jun 20, 2022 at 4:25 PM Andrew Wetmore  wrote:

> This page may have the location:
> https://github.com/apache/royale-asjs/wiki/Release-Manager-(Web-Site)
>
> On Mon, Jun 20, 2022 at 3:59 PM Josh Tynjala 
> wrote:
>
>> Hey guys,
>>
>> I'm working on recreating the website so that we can get out of the
>> current
>> WordPress system. As I understand it, WordPress is not actually deployed
>> to
>> Apache's servers, and it is used only to generate a static version of the
>> site. What is the repo where the current static site gets checked into
>> today? Try as I might, I can't figure that out.
>>
>> Thanks!
>>
>> --
>> Josh Tynjala
>> Bowler Hat LLC <https://bowlerhat.dev>
>>
>
>
> --
> Andrew Wetmore
>
> Editor, Moose House Publications <https://moosehousepress.com/>
> Editor-Writer, The Apache Software Foundation <https://apache.org/>
>
>
>
>
>

-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: Where's the repo where I can checkout the current Royale website?

[Andrew Wetmore]

This page may have the location:
https://github.com/apache/royale-asjs/wiki/Release-Manager-(Web-Site)

On Mon, Jun 20, 2022 at 3:59 PM Josh Tynjala 
wrote:

> Hey guys,
>
> I'm working on recreating the website so that we can get out of the current
> WordPress system. As I understand it, WordPress is not actually deployed to
> Apache's servers, and it is used only to generate a static version of the
> site. What is the repo where the current static site gets checked into
> today? Try as I might, I can't figure that out.
>
> Thanks!
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>


-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: Opinion about adding example project for locales use

[Andrew Wetmore]

Yeah, the key thing for my apps is to be able to switch languages while
working with the app, and having all the text fields display properly.

On Fri, Apr 29, 2022 at 7:44 AM Hugo Ferreira 
wrote:

> I'm also rewriting a Flex app to Royale and there are things that I just
> decided to forget the Flex way and embrace a Royale way.
>
> For localization (you may find a thread about it) I have an interface with
> all localization keys, several "as" files (each one for a specific
> language) that implements the interface and for last a LocaleManager that
> manages everything.
>
> Than I can use something like this:
> 
>
> Also this way the language can be switched at runtime without application
> reboot or refresh.
>
> Soon I will write an operating system utility to insert/update text in the
> several languages and automatically update the several files in the
> project.
>
>
>
>
> Maria Jose Esteve  escreveu no dia sexta, 29/04/2022
> à(s) 11:34:
>
> > I found it useful, I would add it. Let's let other members give their
> > opinion...
> > I can't tell you for sure but I think there have been several discussions
> > on this topic (locale/resourceManager) on the list (Carlos, Alex,
> Josh,...)
> >
> > Hiedra
> >
> > -Mensaje original-
> > De: cont...@cristallium.com 
> > Enviado el: viernes, 29 de abril de 2022 12:01
> > Para: dev@royale.apache.org
> > Asunto: Opinion about adding example project for locales use
> >
> > Hi,
> >
> > I had some difficulty using a Flex-like system for display text
> > translation with Royale.
> > So I made this working example which might be useful for peoples trying
> > this.
> > Could it be added  in the examples ?
> >
> > What do you think ?
> >
> > https://github.com/apache/royale-asjs/pull/1191
> >
> > Could you give me feedback ? (because I'm not sure to use the right
> coding
> > way)
> >
> > Thanks
> >
> > Regards
> >
>


-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

ApacheCon 2022

[Andrew Wetmore]

Hi:

ApacheCon 2022, in New Orleans, USA in October, is requesting suggestions
for presentation tracks. I gather the maximum number of tracks will be more
limited than in the past two years, when the conference was online-only.

We can propose a Royale track, but I was wondering if it is worth bundling
with some other Apache projects to do a 'frameworks' or 'UI" track.

Thoughts?

-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: Update of the royale web site for TDJ

[Andrew Wetmore]

We may have to appeal to Carlos for instructions.

On Sun, Mar 6, 2022 at 8:24 PM Maria Jose Esteve  wrote:

> Hi,
> I have not found explicit instructions for upgrading TDJ, but I have
> deduced from the upgrade instructions on the royale website [1] that you
> manually upgrade with a working release:
> - I compiled TDJ (Maven build).
> - I updated the "tourdejewel" folder in the "royale-website/tree/asf-site"
> repository with the updated TDJ build.
>
> Apparently, I am totally wrong and the TDJ site update is not updated this
> way because I don't see the changes on the website and it has been more
> than 5 hours since I did the last commit.
> How should I update?
>
>
> [1] https://github.com/apache/royale-asjs/wiki/Release-Manager-(Web-Site)
>
> Thx
>
> Hiedra
>
>

-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: [apache/royale-asjs] j:DataGridSort is missing (#1111)

[Andrew Wetmore]

These are the instructions:
https://github.com/apache/royale-asjs/wiki/Release-Manager-(Web-Site).

The complexity of them is part of what makes me want to have a site built
using Royale, rather than relying on WordPress.

a

On Sat, Mar 5, 2022 at 9:05 AM Maria Jose Esteve  wrote:

> Hi,
> Maybe it would be good, for this release, to update the Royale and TDJ
> site.
> The website does not have updated links to the latest versions of the SDK
> and the TDJ is also outdated.
>
> Is there any script I can follow to update it?
>
> Hiedra
>
> -Mensaje original-
> De: Maria Jose Esteve 
> Enviado el: sábado, 5 de marzo de 2022 14:04
> Para: dev@royale.apache.org
> Asunto: RE: [apache/royale-asjs] j:DataGridSort is missing (#)
>
> Hola,
> Tal vez sería bueno, para este lanzamiento, actualizar el sitio de Royale
> y del TDJ.
> El sitio web no tiene actualizados los links a las últimas versiones del
> SDK y el TDJ también está desactualizado.
>
> ¿Existe algún guion que yo pueda seguir para actualizarlo?
>
> Thx.
> Hiedra
>
> De: Nisaba 
> Enviado el: sábado, 5 de marzo de 2022 10:51
> Para: apache/royale-asjs 
> CC: Subscribed 
> Asunto: Re: [apache/royale-asjs] j:DataGridSort is missing (#)
>
>
> Hi,
>
> I use Royale 0.9.9
>
> I've an issue about Datagrid sort that I could reproduce on the example :
> https://royale.apache.org/tourdejewel/#!datagrid_panel
>
> If we click on the "Load Data" button, the sort does'nt work anymore.
>
> Thank you for your help
>
> —
> Reply to this email directly, view it on GitHub<
> https://github.com/apache/royale-asjs/issues/#issuecomment-1059732221>,
> or unsubscribe<
> https://github.com/notifications/unsubscribe-auth/ANJL3UYX3GRIQWCIPKZFHUDU6MU7NANCNFSM45FCJE6Q
> >.
> Triage notifications on the go with GitHub Mobile for iOS<
> https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email=8=524675>
> or Android<
> https://play.google.com/store/apps/details?id=com.github.android=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub
> >.
> You are receiving this because you are subscribed to this thread.Message
> ID: 
>


-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: 0.9.9

[Andrew Wetmore]

No objections here. Going back up the thread, I would be happy to help with
the publicity/marketing efforts around 1.0. If 0.9.9 comes out next week,
what is the target period for 1.0?

<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Fri, Jan 14, 2022 at 10:14 AM Yishay Weiss 
wrote:

> Hi All,
>
> It looks like nobody objects to the next version being 1.0. I will start
> releasing 0.9.9 next week. Any objections to that?
>
> Yishay
>
> From: Yishay Weiss<mailto:yishayj...@hotmail.com>
> Sent: Tuesday, December 7, 2021 5:47 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: 0.9.9
>
> Hi All,
>
> I think there is enough to start a new release. Are there any volunteers?
> If we release 0.9.9 the next version will automatically (I think be set) to
> 1.0.
>
> Are we ready for that?
>
> Appreciate your thoughts.
>
>
>

-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Fwd: [apache/royale-docs] Page build failure

[Andrew Wetmore]

Oops. Fixed now

-- Forwarded message -
From: GitHub 
Date: Mon., Jan. 3, 2022, 6:46 p.m.
Subject: [apache/royale-docs] Page build failure
To: Andrew Wetmore 


The page build failed for the `master` branch with the following error:

There was a YAML syntax error on line 57 column 33 in `_data/toc.json`:
`did not find expected ',' or ']' while parsing a flow sequence`. For more
information, see
https://docs.github.com/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites#invalid-yaml-in-data-file
.

For information on troubleshooting Jekyll see:

  https://docs.github.com/articles/troubleshooting-jekyll-builds

If you have any questions you can submit a request at
https://support.github.com/contact?tags=dotcom-pages_id=105698512_build_id=305042826

page on reflection

[Andrew Wetmore]

@Harbs   in the page on minification you left a
to-do note that we need a page on reflection classes and functions. I can
create a stub for that page if you can tell me where it should be in the
stack. Under 'features'?

a

-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: Why Royale page

[Andrew Wetmore]

It is a jaunty and hopeful document.

I made some minor edits to improve readability.

a

On Mon, Jan 3, 2022 at 12:04 PM Harbs  wrote:

> I just added this page to our docs:
>
> https://apache.github.io/royale-docs/welcome/why-royale
>
> It was kind of fun writing it. Feel free to add to it… ;-)



-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: First Apache Royale App pass all tests in Microsoft Office Store (even support for IE11 and Edge WebView 1) - Urrai !

[Andrew Wetmore]

Oh, I see. The license downloads, rather than displaying in the browser
window that opens when you click the link. I now am the happy owner of six
copies of the license.

On Wed, Dec 15, 2021 at 9:19 AM Andrew Wetmore  wrote:

> Yeah...I will need that tutorial, too!
>
> Could see your privacy policy, but not the license terms when I clicked on
> the link
>
> On Wed, Dec 15, 2021 at 9:07 AM Harbs  wrote:
>
>> FYI, I loaded the add-in, but it’s not clear how to use it. (This is on
>> Mac.)
>>
>>
>>
>>
>> On Dec 15, 2021, at 2:50 PM, Harbs  wrote:
>>
>> Congratulations!
>>
>> On Dec 15, 2021, at 1:07 PM, Hugo Ferreira 
>> wrote:
>>
>> Details
>>
>> Result
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Name
>>
>> Pass
>>
>>
>>
>>
>>
>> GC - Gestão de Condomínios
>>
>>
>>
>>
>>
>> *Congratulations! Your submission has been approved for publishing to
>> AppSource and other relevant Microsoft storefronts as per your specified
>> schedule.*
>>
>> *Microsoft will continue testing your offer and may reach out to you with
>> any issues that are observed later.*
>>
>>
>>
>>
>>
>> Publisher
>>
>>
>>
>>
>>
>> SolidSoft, Unipessoal LDA
>>
>>
>>
>>
>
> --
> Andrew Wetmore
>
> Editor, Moose House Publications <https://moosehousepress.com/>
> Editor-Writer, The Apache Software Foundation <https://apache.org/>
>
>
>
>
>

-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: First Apache Royale App pass all tests in Microsoft Office Store (even support for IE11 and Edge WebView 1) - Urrai !

[Andrew Wetmore]

Yeah...I will need that tutorial, too!

Could see your privacy policy, but not the license terms when I clicked on
the link

On Wed, Dec 15, 2021 at 9:07 AM Harbs  wrote:

> FYI, I loaded the add-in, but it’s not clear how to use it. (This is on
> Mac.)
>
>
>
>
> On Dec 15, 2021, at 2:50 PM, Harbs  wrote:
>
> Congratulations!
>
> On Dec 15, 2021, at 1:07 PM, Hugo Ferreira  wrote:
>
> Details
>
> Result
>
>
>
>
>
>
>
>
>
> Name
>
> Pass
>
>
>
>
>
> GC - Gestão de Condomínios
>
>
>
>
>
> *Congratulations! Your submission has been approved for publishing to
> AppSource and other relevant Microsoft storefronts as per your specified
> schedule.*
>
> *Microsoft will continue testing your offer and may reach out to you with
> any issues that are observed later.*
>
>
>
>
>
> Publisher
>
>
>
>
>
> SolidSoft, Unipessoal LDA
>
>
>
>

-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: [royale-asjs] 01/01: Added sanitizeUrl and sanitizeHtml

[Andrew Wetmore]

;>   public var stringUtilsTest:StringUtilsTest;
> >>> +public var sanitizerTest:SanitizeTest;
> >>>   }
> >>> }
> >>> diff --git
> a/frameworks/projects/Core/src/test/royale/flexUnitTests/CoreTester.as
> b/frameworks/projects/Core/src/test/royale/flexUnitTests/SanitizeTest.as
> >>> similarity index 50%
> >>> copy from
> frameworks/projects/Core/src/test/royale/flexUnitTests/CoreTester.as
> >>> copy to
> frameworks/projects/Core/src/test/royale/flexUnitTests/SanitizeTest.as
> >>> index c8adc02..7173f52 100644
> >>> ---
> a/frameworks/projects/Core/src/test/royale/flexUnitTests/CoreTester.as
> >>> +++
> b/frameworks/projects/Core/src/test/royale/flexUnitTests/SanitizeTest.as
> >>> @@ -18,29 +18,46 @@
> >>>
> 
> >>> package flexUnitTests
> >>> {
> >>> -import flexUnitTests.language.*
> >>> +import org.apache.royale.utils.string.*;
> >>> +import org.apache.royale.test.asserts.*;
> >>>
> >>> -[Suite]
> >>> -[RunWith("org.apache.royale.test.runners.SuiteRunner")]
> >>> -public class CoreTester
> >>> -{
> >>> +public class SanitizeTest
> >>> +{
> >>> +[Before]
> >>> +public function setUp():void
> >>> +{
> >>> +}
> >>>
> >>> -//language tests
> >>> -public var languageTestIs:LanguageTesterTestIs;
> >>> -public var languageTestIntUint:LanguageTesterIntUint;
> >>> -public var languageTestVector:LanguageTesterTestVector;
> >>> -public var languageTestClass:LanguageTesterTestClass;
> >>> -public var
> languageTestLoopVariants:LanguageTesterTestLoopVariants;
> >>> -public var languageTestArraySort:LanguageTesterArraySort;
> >>> -public var languageTesttryCatch:LanguageTesterTestTryCatch;
> >>> +[After]
> >>> +public function tearDown():void
> >>> +{
> >>> +}
> >>>
> >>> -//core tests
> >>> -public var strandTesterTest:StrandTesterTest;
> >>> -   public var binaryDataTesterTest:BinaryDataTesterTest;
> >>> -   public var arrayUtilsTest:ArrayUtilsTest;
> >>> -   public var dateUtilsTest:DateUtilsTest;
> >>> -public var keyConverterTest:KeyConverterTest;
> >>> -public var
> keyboardEventConverterTest:KeyboardEventConverterTest;
> >>> -public var stringUtilsTest:StringUtilsTest;
> >>> +[BeforeClass]
> >>> +public static function setUpBeforeClass():void
> >>> +{
> >>> +}
> >>> +
> >>> +[AfterClass]
> >>> +public static function tearDownAfterClass():void
> >>> +{
> >>> +}
> >>> +
> >>> +[Test]
> >>> +public function testHTML():void
> >>> +{
> >>> +var safeHtml:String = 'Hello World';
> >>> +assertEquals(safeHtml, sanitizeHtml(safeHtml));
> >>> +}
> >>> +
> >>> +[Test]
> >>> +public function testUrl():void
> >>> +{
> >>> +var safeUrl:String = "https://foobaz.com;
> >>> +assertEquals(safeUrl, sanitizeUrl(safeUrl));
> >>> +}
> >>> +
> >>> +
> >>> +
> >>>   }
> >>> }
> >>
> >
>
>

-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: Sanitizing HTML (was Re: 0.9.9)

[Andrew Wetmore]

I would think that styling text in buttons would be pretty common
across the Flex universe.

Does there need to be documentation about this threat and our steps to
secure Royale from it?

On Sun, Dec 12, 2021 at 9:44 AM Harbs  wrote:

> At the expense of performance? How common was setting styled text in
> buttons?
>
> I could go either way on this.
>
> > On Dec 12, 2021, at 2:57 PM, Yishay Weiss 
> wrote:
> >
> > Haven’t been following this closely enough to understand the overhead
> involved, but if it’s not big then retaining backwards compatibility in
> emulation should take priority IMO. For other component sets I wouldn’t say
> that.
>
>

-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: Apache Royale Add-In publish to Microsoft Office Store

[Andrew Wetmore]

This is very good news

On Fri, Dec 10, 2021 at 8:47 AM Hugo Ferreira 
wrote:

> Piotr,
>
> Of course I will.
> I'm now waiting for the approval process like if it was a normal App
> Mobile.
> It's the first time and with a Royale App so I don't know what will happen.
> Let's find out on the next few days.
>
> Piotr Zarzycki  escreveu no dia sexta,
> 10/12/2021 à(s) 11:22:
>
> > Hugo,
> >
> > Please post link to it! :) Congrats!
> >
> > pt., 10 gru 2021 o 06:39 Yishay Weiss 
> napisał(a):
> >
> > > Congrats! Were any of the failures Royale related?
> > >
> > > From: Hugo Ferreira<mailto:hferreira...@gmail.com>
> > > Sent: Friday, December 10, 2021 4:22 AM
> > > To: Apache Royale Development<mailto:dev@royale.apache.org>
> > > Subject: Apache Royale Add-In publish to Microsoft Office Store
> > >
> > > Hi,
> > >
> > > My Add-In was just successful publish to the Microsoft Office Store for
> > > evaluation (after pass for a long process of failure over failure).
> > > Let's see if they approve.
> > >
> > >
> >
> > --
> >
> > Piotr Zarzycki
> >
>


-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: Use Royale to build the Royale website?

[Andrew Wetmore]

Let's use the existing wiki page [1] as a sort of status-update page, if
that works for you.


1.
https://github.com/apache/royale-asjs/wiki/Royale-project-site-built-with-Royale

On Sun, Dec 5, 2021 at 9:23 AM Harbs  wrote:

> OK. I’ll hopefully start on this sometime this week.
>
> Once I make some progress I’ll probably try and coordinate with you on how
> to best document it.
>
> If anyone has further thoughts, please let me know.
>
> Harbs
>
> > On Dec 5, 2021, at 2:57 PM, Andrew Wetmore  wrote:
> >
> > Excellent. We will need both maintenance and user-facing documentation,
> but
> > once we have this in place Royale will be much stronger and more suitable
> > to many more uses.
> >
> > On Sun, Dec 5, 2021 at 8:54 AM Harbs  harbs.li...@gmail.com>> wrote:
> >
> >> Great.
> >>
> >> After spending some time looking at existing implementations, I think
> I’m
> >> going to port the parsing code from
> >> https://github.com/jonschlinkert/remarkable <
> https://github.com/jonschlinkert/remarkable> <
> >> https://github.com/jonschlinkert/remarkable <
> https://github.com/jonschlinkert/remarkable>>
> >>
> >> It’s well organized and the performance is very good.
> >>
> >>
> >>
> https://www.measurethat.net/Benchmarks/Show/8434/0/markdown-performance-comparison#latest_results_block
> <
> https://www.measurethat.net/Benchmarks/Show/8434/0/markdown-performance-comparison#latest_results_block
> >
> >> <
> >>
> https://www.measurethat.net/Benchmarks/Show/8434/0/markdown-performance-comparison#latest_results_block
> <
> https://www.measurethat.net/Benchmarks/Show/8434/0/markdown-performance-comparison#latest_results_block
> >
> >>>
> >>
> >> Only Snarkdown is faster, but that implementation seems very bare-bones
> >> and outputs directly to html.
> >>
> >> Here’s the approach that I’m considering:
> >>
> >> 1. Markdown gets parsed into nodes.
> >> 2. We have a mapper class which maps nodes to corresponding
> IParentUIBase
> >> components. This map will be customizable.
> >> 3. We walk down the node tree and create and populate the components.
> >> 4. I’d like to hook this into a Router for navigation.
> >>
> >> I’m probably going to do this with my daughter who is in school to serve
> >> as a practice lesson in generating and using document trees. B-)
> >>
> >>> On Dec 5, 2021, at 1:17 AM, Andrew Wetmore 
> wrote:
> >>>
> >>> I would be happy to help with this. I started to build such a parser
> >> myself
> >>> a few months back, but got swamped with work. It would be an excellent
> >>> demonstration of how adaptable Royale is.
> >>>
> >>> On Sat, Dec 4, 2021 at 7:07 PM Harbs  wrote:
> >>>
> >>>> I’ve been thinking about the website and I had an idea.
> >>>>
> >>>> The problems we have with the website currently:
> >>>>
> >>>> 1. You need to loging to Wordpress to make changes.
> >>>> 2. It relies on external resources.
> >>>> 3. There’s no way to make pull requests to improve the website.
> >>>> 4. It doesn’t showcase Royale. If we could "eat our own dogfood”, that
> >>>> would be great.
> >>>>
> >>>> Royale *can* be used to generate a website, but it’s not really great
> >> for
> >>>> writing or updating content.
> >>>>
> >>>> The best way (IMO) to write content is using markdown. We can create a
> >>>> Royale app which loads markdown files to populate content. We can
> route
> >>>> based on the URL to specific markdown files to determine which content
> >> to
> >>>> load.
> >>>>
> >>>> The content can be formatted by mapping markdown nodes to Royale
> >>>> components. You could have multiple mappings in a single document so
> >>>> multiple markdown files can be used to populate content in different
> >> areas
> >>>> (i.e. sidebar, footer, main content, etc.)
> >>>>
> >>>> I’m willing to volunteer to write the parser and mapper if others like
> >> the
> >>>> idea and are willing to participate in other aspects. There’s a couple
> >> of
> >>>> appropriately licensed projects that I can borrow code from for the
> >> parsing
> >>>> logic. 

Re: Use Royale to build the Royale website?

[Andrew Wetmore]

Excellent. We will need both maintenance and user-facing documentation, but
once we have this in place Royale will be much stronger and more suitable
to many more uses.

On Sun, Dec 5, 2021 at 8:54 AM Harbs  wrote:

> Great.
>
> After spending some time looking at existing implementations, I think I’m
> going to port the parsing code from
> https://github.com/jonschlinkert/remarkable <
> https://github.com/jonschlinkert/remarkable>
>
> It’s well organized and the performance is very good.
>
>
> https://www.measurethat.net/Benchmarks/Show/8434/0/markdown-performance-comparison#latest_results_block
> <
> https://www.measurethat.net/Benchmarks/Show/8434/0/markdown-performance-comparison#latest_results_block
> >
>
> Only Snarkdown is faster, but that implementation seems very bare-bones
> and outputs directly to html.
>
> Here’s the approach that I’m considering:
>
> 1. Markdown gets parsed into nodes.
> 2. We have a mapper class which maps nodes to corresponding IParentUIBase
> components. This map will be customizable.
> 3. We walk down the node tree and create and populate the components.
> 4. I’d like to hook this into a Router for navigation.
>
> I’m probably going to do this with my daughter who is in school to serve
> as a practice lesson in generating and using document trees. B-)
>
> > On Dec 5, 2021, at 1:17 AM, Andrew Wetmore  wrote:
> >
> > I would be happy to help with this. I started to build such a parser
> myself
> > a few months back, but got swamped with work. It would be an excellent
> > demonstration of how adaptable Royale is.
> >
> > On Sat, Dec 4, 2021 at 7:07 PM Harbs  wrote:
> >
> >> I’ve been thinking about the website and I had an idea.
> >>
> >> The problems we have with the website currently:
> >>
> >> 1. You need to loging to Wordpress to make changes.
> >> 2. It relies on external resources.
> >> 3. There’s no way to make pull requests to improve the website.
> >> 4. It doesn’t showcase Royale. If we could "eat our own dogfood”, that
> >> would be great.
> >>
> >> Royale *can* be used to generate a website, but it’s not really great
> for
> >> writing or updating content.
> >>
> >> The best way (IMO) to write content is using markdown. We can create a
> >> Royale app which loads markdown files to populate content. We can route
> >> based on the URL to specific markdown files to determine which content
> to
> >> load.
> >>
> >> The content can be formatted by mapping markdown nodes to Royale
> >> components. You could have multiple mappings in a single document so
> >> multiple markdown files can be used to populate content in different
> areas
> >> (i.e. sidebar, footer, main content, etc.)
> >>
> >> I’m willing to volunteer to write the parser and mapper if others like
> the
> >> idea and are willing to participate in other aspects. There’s a couple
> of
> >> appropriately licensed projects that I can borrow code from for the
> parsing
> >> logic. https://github.com/markdown-it/markdown-it
> >> https://github.com/showdownjs/showdown
> >>
> >> Thoughts?
> >>
> >>> On Apr 18, 2021, at 2:52 PM, Andrew Wetmore 
> wrote:
> >>>
> >>> Hi, all:
> >>>
> >>> I have created a wiki page [1] where we can scope out developing the
> >> Royale
> >>> website as built using Royale. I have suggested some requirements, some
> >>> "nice to have" things and some things that are not required; however
> >> these
> >>> are just my ideas. Input from others until we reach consensus would be
> >>> useful.
> >>>
> >>> Here is one specific point: there are a couple of abandoned efforts to
> >>> build the Royale site using Royale. Do we use these repositories, or
> >> create
> >>> a new one for this effort?
> >>>
> >>> a
> >>>
> >>> 1.
> >>>
> >>
> https://github.com/apache/royale-asjs/wiki/Royale-project-site-built-with-Royale
> >>>
> >>> On Fri, Apr 16, 2021 at 12:29 PM Alina Kazi 
> >> wrote:
> >>>
> >>>> Congrats Andrew.
> >>>>
> >>>> Yes we can add viewstates (includeIn), phone/tablet/desktop Numerator
> >>>> denominator to adjust the view on different devices, common header and
> >>>> footer and much more.
> >>>> We'll be waiting for the wiki page tomorrow 

Re: Use Royale to build the Royale website?

[Andrew Wetmore]

I would be happy to help with this. I started to build such a parser myself
a few months back, but got swamped with work. It would be an excellent
demonstration of how adaptable Royale is.

On Sat, Dec 4, 2021 at 7:07 PM Harbs  wrote:

> I’ve been thinking about the website and I had an idea.
>
> The problems we have with the website currently:
>
> 1. You need to loging to Wordpress to make changes.
> 2. It relies on external resources.
> 3. There’s no way to make pull requests to improve the website.
> 4. It doesn’t showcase Royale. If we could "eat our own dogfood”, that
> would be great.
>
> Royale *can* be used to generate a website, but it’s not really great for
> writing or updating content.
>
> The best way (IMO) to write content is using markdown. We can create a
> Royale app which loads markdown files to populate content. We can route
> based on the URL to specific markdown files to determine which content to
> load.
>
> The content can be formatted by mapping markdown nodes to Royale
> components. You could have multiple mappings in a single document so
> multiple markdown files can be used to populate content in different areas
> (i.e. sidebar, footer, main content, etc.)
>
> I’m willing to volunteer to write the parser and mapper if others like the
> idea and are willing to participate in other aspects. There’s a couple of
> appropriately licensed projects that I can borrow code from for the parsing
> logic. https://github.com/markdown-it/markdown-it
> https://github.com/showdownjs/showdown
>
> Thoughts?
>
> > On Apr 18, 2021, at 2:52 PM, Andrew Wetmore  wrote:
> >
> > Hi, all:
> >
> > I have created a wiki page [1] where we can scope out developing the
> Royale
> > website as built using Royale. I have suggested some requirements, some
> > "nice to have" things and some things that are not required; however
> these
> > are just my ideas. Input from others until we reach consensus would be
> > useful.
> >
> > Here is one specific point: there are a couple of abandoned efforts to
> > build the Royale site using Royale. Do we use these repositories, or
> create
> > a new one for this effort?
> >
> > a
> >
> > 1.
> >
> https://github.com/apache/royale-asjs/wiki/Royale-project-site-built-with-Royale
> >
> > On Fri, Apr 16, 2021 at 12:29 PM Alina Kazi 
> wrote:
> >
> >> Congrats Andrew.
> >>
> >> Yes we can add viewstates (includeIn), phone/tablet/desktop Numerator
> >> denominator to adjust the view on different devices, common header and
> >> footer and much more.
> >> We'll be waiting for the wiki page tomorrow to get started.
> >>
> >> Thanks,
> >> Alina Kazi
> >>
> >> On Fri, 16 Apr 2021, 7:29 PM Piotr Zarzycki,  >
> >> wrote:
> >>
> >>> Congrats Andrew!
> >>>
> >>> pt., 16 kwi 2021 o 13:31 Andrew Wetmore 
> >> napisał(a):
> >>>
> >>>> Today my wife and I have appointments, a long drive from home, to get
> >> our
> >>>> first COVID-19 injections. This will probably use up most of the day,
> >>>> leaving aside possible side-effects, so I likely will not have the
> wiki
> >>>> page about the web site ready to receive ideas and concerns until
> >>> tomorrow
> >>>> at the earliest.
> >>>>
> >>>> a
> >>>>
> >>>> On Thu, Apr 15, 2021 at 8:33 PM Maria Jose Esteve 
> >>>> wrote:
> >>>>
> >>>>> What dizziness! jajajaja
> >>>>>
> >>>>> Hiedra
> >>>>>
> >>>>> -Mensaje original-
> >>>>> De: Andrew Wetmore 
> >>>>> Enviado el: viernes, 16 de abril de 2021 1:29
> >>>>> Para: Apache Royale Development 
> >>>>> Asunto: Re: Use Royale to build the Royale website?
> >>>>>
> >>>>> This is great.
> >>>>>
> >>>>> To start, I think I will create a wiki page so we can capture what we
> >>>> must
> >>>>> have and what we would like to have in the website. For me, our
> >> website
> >>>>> must communicate useful and engaging information about our project
> >> and
> >>>> what
> >>>>> one can do with Royale. I would also like to include some features to
> >>>>> demonstrate a little bit of what Royale can do--maybe viewstates to
> >>>> manage
>

Re: ASDoc

[Andrew Wetmore]

@Alex Harui  is what you noted in the wiki somewhere? If
not, may I add it so we don't have to repeat this snipe hunt in a few
months?

a

On Mon, Nov 29, 2021 at 3:22 AM Alex Harui  wrote:

> IIRC, the "asdoc" target in the top-level build.xml does not work and is
> kept around in case we try to make it work the way Flex did.
>
> Flex ASDoc used DITA and XSLT which I did not want to learn and figured
> most others didn't want to learn either, so I put together
> examples/royale/ASDoc.  Make sure you run the "clean" target otherwise it
> might not rebuild the "json" target which asks the Royale compiler to
> generate JSON from the ASDoc encountered while compiling the SWCs.
>
> Looks like the Jenkins server hasn't built ASDoc in a long time because it
> was configured to be triggered by a build from another committer's Jenkins
> server which we never got working.  But the build currently fails locally
> as happens from time to time probably from unexpected or improperly
> formatted ASDoc comments.  Wade through the output, find the problem
> comments and either fix the compiler or adjust the comments.
>
> The net result is a Royale app for Royale documentation, showcasing what
> Royale can do.
>
> FWIW, I also put together examples/royale/RoyaleWebsite.  It might be
> worth considering again.  Past discussion concluded that Royale was more
> for webapps than websites, but it might be worth leaving behind WP and the
> custom theme and proving that either Royale can be the base for a site or
> that Royale integrates well into a standard website.  Maybe abandon that
> example as well and rebuild the site out of some popular non-WP thing (GH
> Pages?) and plug Royale applets into the html files to showcase a weather
> reporter or for the contactUs form.
>
> HTH,
> -Alex
>
> On 11/28/21, 8:26 AM, "Yishay Weiss"  wrote:
>
> Unfortunately it isn’t building now [1] (last successful build was a
> year and a half ago). I may be looking at the wrong thing because part of
> 0.9.8 release was to check ASDocs so it would have passed then…
>
> [1] Royale_ASDoc_Example #956 Console [Jenkins] (azure.com)<
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_ASDoc_Example%2F956%2FconsoleFulldata=04%7C01%7Caharui%40adobe.com%7C766e6d97e81242f67ec508d9b28b9dc8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637737135866922696%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=dFFYN%2Fp7hUDJ%2B8rEIg%2BrrtI6TFlj%2BE4JLZz9qHi2q1g%3Dreserved=0
> >
>
> From: Yishay Weiss<mailto:yishayj...@hotmail.com>
> Sent: Sunday, November 28, 2021 6:06 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: RE: ASDoc
>
> I see the following file being used
>
> examples/royale/ASDoc/build.xml
>
> From: Yishay Weiss<mailto:yishayj...@hotmail.com>
> Sent: Sunday, November 28, 2021 6:00 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: RE: ASDoc
>
> It’s built in CI server so I can have a look there at the config later
> if nobody else beats me to it.
>
> From: Harbs<mailto:harbs.li...@gmail.com>
> Sent: Sunday, November 28, 2021 3:51 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Re: ASDoc
>
> I managed to generate compiler-royaleTasks.jar and I tried copying
> that manually and renaming it to royaleTasks.jar, but that didn’t help.
>
> I’m groping in the dark here…
>
> I think I’m going to have to wait for Alex...
>
> > On Nov 28, 2021, at 3:33 PM, Harbs  wrote:
> >
> > It’s defined in the top level here:
> >
> > 
> > 
> > 
> >  classpath="${basedir}/js/lib/compiler-royaleTasks.jar"/>
> > 
> >
> >
> > and in asdocs here:
> >
> > 
> > 
> > 
> > 
> > 
> > 
> >  classpathref="flexTasks.path"/>
> >
> > but for some reason flexTasks.path has no value.
> >
> > well, maybe it’s because royaleTasks.jar does not exist…
> >
> > I’ll have to see if I can figure out what creates that.
> >
> >> On Nov 28, 2021, at 3:26 PM, Andrew Wetmore  <mailto:cottag...@gmail.com>> wrote:
> >>
> >> We have a resource file called flexTasks? Or did it get renamed to
&

Re: ASDoc

[Andrew Wetmore]

We have a resource file called flexTasks? Or did it get renamed to
something like royaleTasks and the script was not updated?

On Sun, Nov 28, 2021 at 9:10 AM Harbs  wrote:

> Yeah…
>
> Harbss-Mac-mini:royale-asjs harbs$ ant asdoc
> Buildfile: /Apache/royale-asjs/build.xml
>
> asdoc:
>  [echo] ROYALE_HOME = /Apache/royale-asjs
>  [echo] royalelib = /Apache/royale-asjs/frameworks
>  [echo] doc_output = /Apache/royale-asjs/asdoc-output
>  [echo] compiler.source-path =
> /Apache/royale-asjs/frameworks/projects/*/src/main/royale
>
> clean:
>
> doc:
>   [taskdef] Could not load definitions from resource flexTasks.tasks. It
> could not be found.
>
> BUILD FAILED
> /Apache/royale-asjs/build.xml:815: The following error occurred while
> executing this line:
> /Apache/royale-asjs/asdoc/build.xml:73: Problem: failed to create task or
> type asdoc
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any / declarations have taken
> place.
>
> > On Nov 28, 2021, at 2:29 PM, Andrew Wetmore  wrote:
> >
> > I see the build script here [1]. I presume you update the ASDoc files and
> > then run this script. HOW you run this script, I do not know.
> >
> > a
> >
> > [1] https://github.com/apache/royale-asjs/blob/develop/asdoc/build.xml
> >
> > On Sun, Nov 28, 2021 at 5:47 AM Harbs  wrote:
> >
> >> I don’t see any docs on the docs… ;-)
> >>
> >> I’d really like to work on this, but I’m not sure where to start.
> >>
> >>> On Nov 15, 2021, at 4:03 PM, Andrew Wetmore 
> wrote:
> >>>
> >>> I think there is some, um, documentation on building ASDoc on the
> wiki. I
> >>> will go look.
> >>>
> >>> a
> >>>
> >>> On Mon, Nov 15, 2021 at 8:59 AM Harbs  wrote:
> >>>
> >>>> I’m interested in improving the ASDoc app and info.
> >>>>
> >>>> Some things I’m interested in (besides improving the look) is:
> >>>> 1. Adding utility functions. Those seem to be missing.
> >>>> 2. Release versioning.
> >>>> 3. Add some top level info like XML.
> >>>>
> >>>> Who understands how ASDoc builds work?
> >>>>
> >>>> Thanks,
> >>>> Harbs
> >>>
> >>>
> >>>
> >>> --
> >>> Andrew Wetmore
> >>>
> >>> http://cottage14.blogspot.com/
> >>
> >>
> >
> > --
> > Andrew Wetmore
> >
> > Editor, Moose House Publications <https://moosehousepress.com/>
> > Editor-Writer, The Apache Software Foundation <https://apache.org/>
>
>

-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: ASDoc

[Andrew Wetmore]

I see the build script here [1]. I presume you update the ASDoc files and
then run this script. HOW you run this script, I do not know.

a

[1] https://github.com/apache/royale-asjs/blob/develop/asdoc/build.xml

On Sun, Nov 28, 2021 at 5:47 AM Harbs  wrote:

> I don’t see any docs on the docs… ;-)
>
> I’d really like to work on this, but I’m not sure where to start.
>
> > On Nov 15, 2021, at 4:03 PM, Andrew Wetmore  wrote:
> >
> > I think there is some, um, documentation on building ASDoc on the wiki. I
> > will go look.
> >
> > a
> >
> > On Mon, Nov 15, 2021 at 8:59 AM Harbs  wrote:
> >
> >> I’m interested in improving the ASDoc app and info.
> >>
> >> Some things I’m interested in (besides improving the look) is:
> >> 1. Adding utility functions. Those seem to be missing.
> >> 2. Release versioning.
> >> 3. Add some top level info like XML.
> >>
> >> Who understands how ASDoc builds work?
> >>
> >> Thanks,
> >> Harbs
> >
> >
> >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/
>
>

-- 
Andrew Wetmore

Editor, Moose House Publications <https://moosehousepress.com/>
Editor-Writer, The Apache Software Foundation <https://apache.org/>

Re: ASDoc

[Andrew Wetmore]

I think there is some, um, documentation on building ASDoc on the wiki. I
will go look.

a

On Mon, Nov 15, 2021 at 8:59 AM Harbs  wrote:

> I’m interested in improving the ASDoc app and info.
>
> Some things I’m interested in (besides improving the look) is:
> 1. Adding utility functions. Those seem to be missing.
> 2. Release versioning.
> 3. Add some top level info like XML.
>
> Who understands how ASDoc builds work?
>
> Thanks,
> Harbs



-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Dictionary

[Andrew Wetmore]

Greg, can I throw that into documentation as a workaround?

On Sat., Nov. 13, 2021, 4:45 p.m. Greg Dove,  wrote:

> Hi Hugo,
>
> I might change this in the near future. But for now, here is the general
> 'rule of thumb' that I use:
>
> If the instance only has string keys (or int/uint/Number/Boolean keys
> should be ok too) then use a plain Object. All code can pretty much then
> remain unchanged.
>
> If it is using object instances (any complex object like functions or class
> instances, or generic object instances) as keys, then
>
> a) use native js Map if the original constructor argument does not have
> weakKeys=true, or if it has weakKeys= true and there is any form of
> iteration over keys (you cannot iterate over keys in a WeakMap in
> javascript)
>
> b) otherwise use WeakMap.
>
> Both (a) and (b) require you to change code for get/set ([]
> access/assignment in as3) or delete operator, and also code related to
> iteration (use map.forEach in js).
> see docs for those:
>
> https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map
>
> https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakMap
>
>
>
>
> On Sun, Nov 14, 2021 at 9:34 AM Hugo Ferreira 
> wrote:
>
> > Hi,
> >
> > I see that there is no Dictionary on Royale, probably because there is a
> > better method.
> > What the approach in Royale for a Dictionary ?
> >
>

Re: [royale-asjs] 01/02: Merge branch 'ChildResize' into develop

[Andrew Wetmore]

Should I add a description of what we now expect the behaviour to be,
somewhere in the docs on containers?

On Mon, Nov 1, 2021 at 6:59 AM Yishay Weiss  wrote:

> Hi,
>
> I finally decided to merge ChildResize branch into develop which should
> improve layout in emulation layer for containers that include children
> added post-creation. Most of the changes were done by Alex over a year ago.
> I tested this branch on a project about a year ago and found that it solved
> many layout issues, though not all of them. Hopefully, when we resolve the
> conflicts with PR #1135 and merge, even more layout issues will be resolved.
>
> As I understand it, the basic idea is that container layouts listen on
> children’s ‘sizeChanged’ events and run layouts and measuremnts in
> response. In addition, if adding a child has resulted in the container
> changing its measured size then the container parent’s size is invalidated
> as well. This should allow size invalidation to bubble up if necessary,
> setting the stage for further measurements in the next layout cycle.
>
> There are additional commits that were made on this branch which should
> fix other issues unrelated to layout.
>
> Please let me know if this merge breaks anything, or if you object to them
> for other reasons. We can discuss what needs to be reverted in such a case.
>
> Thanks,
> Yishay
>
> From: yish...@apache.org<mailto:yish...@apache.org>
> Sent: Monday, November 1, 2021 10:42 AM
> To: comm...@royale.apache.org<mailto:comm...@royale.apache.org>
> Subject: [royale-asjs] 01/02: Merge branch 'ChildResize' into develop
>
> This is an automated email from the ASF dual-hosted git repository.
>
> yishayw pushed a commit to branch develop
> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
>
> commit d8a61862dfa751f762a1f699b5c1016729027409
> Merge: fbf8fcb 0d781be
> Author: Yishay Weiss 
> AuthorDate: Sun Oct 31 20:16:56 2021 +0200
>
> Merge branch 'ChildResize' into develop
>
>  .../MXRoyale/src/main/resources/defaults.css   |  2 -
>  .../main/royale/mx/containers/beads/BoxLayout.as   | 43 +-
>  .../MXRoyale/src/main/royale/mx/core/Container.as  | 46
> ++-
>  .../royale/spark/components/SkinnableContainer.as  | 41 +
>  .../royale/spark/components/beads/GroupView.as | 21 +++--
>  .../components/beads/SkinnableContainerView.as | 14 ++++--
>  .../layouts/supportClasses/SparkLayoutBead.as  | 52
> +-
>  7 files changed, 207 insertions(+), 12 deletions(-)
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Two-way databinding

[Andrew Wetmore]

If this is so, I should update the docs to be more clear. If I get a chance
later today I will field-test methods one and two.

a

On Sun, Oct 31, 2021 at 8:51 AM Edward Stangler 
wrote:

>
> In Flex, two-way binding can be done in several ways:
>
> 1.  
>
> 2.  
> 
>
> 3.  value="@{comp.A}"
>
> As you said, Royale does not support #3 (in fact, it breaks one-way
> binding;  see Issue #1162).
>
> And, there are various bugs (see Issues #1159, #1160, #1161, and
> probably more).
>
> But two-way binding does work.
>
>
>
> On 10/30/2021 11:11 AM, Hugo Ferreira wrote:
> > It doesn't work for me either.
> > In a search, I don't think that is implemented yet.
> >
> > Maria Jose Esteve escreveu no dia sábado, 30/10/2021
> > à(s) 17:03:
> >
> >> I don't think so Hugo.
> >> Binding with "@" hasn't worked for me so far. Perhaps someone more
> >> experienced can give us more information.
> >>
> >> Hiedra
> >>
> >> -Mensaje original-
> >> De: Hugo Ferreira
> >> Enviado el: sábado, 30 de octubre de 2021 17:49
> >> Para: Apache Royale Development 
> >> Asunto: Two-way databinding
> >>
> >> Hi,
> >>
> >> Just to confirm, two-way databinding is not supported at the moment,
> >> correct, or did I miss something on my search ?
> >>
> >> Regards,
> >> Hugo.
> >>
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: MXRoyale splitting to two libs - please provide your feedback.

[Andrew Wetmore]

Yes. I would love to help update the documentation to reflect this advance.
First step would be a clear example app or two. Then I would try to update
our getting-started material. THEN I would have to tackle the tutorials
that Carlos wrote.

a

On Wed, Oct 6, 2021 at 7:17 PM Alina Kazi  wrote:

> +1 for two libs
>
> On Thu, 7 Oct 2021, 2:42 am Piotr Zarzycki, 
> wrote:
>
> > +1 for that.
> >
> > Could you share for application which is being build by Maven how would
> > look like dependencies if someone would like to use both libraries.
> >
> > It’s just for the documentation purposes here.
> >
> > Thanks,
> > Piotr
> >
> > On Wed, 6 Oct 2021 at 22:59, Greg Dove  wrote:
> >
> > > I have had at least two requests for it, and others still express
> support
> > > for it, and it has been said in past discussions that if someone is
> > willing
> > > to 'put in the work' that it's welcome... so I wanted to signal my
> > > intention to split MXRoyale up into two libraries - the first being
> most
> > of
> > > the non-UI classes "MXRoyaleBase", and the second being the same as the
> > > current "MXRoyale" lib is now.
> > >
> > > I already have this working locally, so this is really just a check-in
> to
> > > make sure everyone is comfortable with it before I push any changes
> > related
> > > to this.
> > > If, after reading this post, you have any concerns, can you please
> share
> > > them in reply to this thread.
> > >
> > > The change will make it easier for people who want to use (for example)
> > the
> > > mx services/remoting support with a non-emulation component set (e.g.
> > > Jewel). It may also make it easier for any Royale developer who wants
> to
> > > take a shot at an alternate version of the mx emulation set (if anyone
> is
> > > so inclined) because the non-UI parts and likely some of the UI
> > interfaces
> > > only will be in the MXRoyaleBase library. As an example, someone might
> > want
> > > to create a new emulation set that more closely mirrors (assuming it is
> > > possible to do so) the original measurement and layout aspects of the
> > Flex
> > > lifecycle, or which takes advantage of more modern browser APIs because
> > > they don't care about support for older browsers, or simply for
> whatever
> > > other reasons they might have.
> > >
> > > What impact will it have on me?
> > > *Royale User:*
> > > No change for emulation users: If you are using MXRoyale currently, it
> > will
> > > continue to work as it has before.
> > > Non-emulation users: If you want to use mx service classes (for
> example)
> > in
> > > some non-emulation component set (e.g. Jewel or Basic), it will make
> > things
> > > easier for you because you can switch to MXRoyaleBase.swc and won't
> have
> > to
> > > exclude the css from the MXRoyale.swc. At the same time, the current
> > > approach for excluding css will continue to work as before.
> > >
> > > *Royale Developer:*
> > > The source code from the current MXRoyale codebase will be split into
> two
> > > libraries- MXRoyaleBase for mostly non-UI code and MXRoyale which will
> be
> > > mostly the UI implementation code. MXRoyale swc build will include the
> > > MXRoyaleBase source code and its mxml component definitions so that the
> > > code from the other swc gets included, resulting in the same swc build
> as
> > > before for MXRoyale (this avoids breaking any builds for folks using
> > > MXRoyale). The biggest impact from an emulation developer's perspective
> > is
> > > that potentially you might need to look in two library codebases (e.g.
> if
> > > you are making changes to IUIComponent which is in MXRoyaleBase and
> > > UIComponent which is in MXRoyale). If you are working on non-UI code,
> it
> > > should mainly be in MXRoyaleBase. If you are mainly working mainly on
> the
> > > UI code, which I think is very often the case, it will continue to be
> in
> > > MXRoyale.
> > >
> > >
> > > Thanks,
> > > Greg
> > >
> > --
> >
> > Piotr Zarzycki
> >
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.8 released

[Andrew Wetmore]

The release announcement looks good, but I would suggest one small change.

This passage has two URLs that point to the same place, our website:

===
Additional documentation is here: https://apache.github.io/royale-docs/

The documentation is still a work in progress. Volunteers are welcome to
help improve it. Visit https://royale.apache.org/ for links to other
resources.

===

I would change this to

===

Documentation and links to other resources are at
https://royale.apache.org/ . The documentation is a work in progress, and
volunteers are welcome to help improve it.

===

On Tue, Aug 31, 2021 at 5:21 AM Yishay Weiss  wrote:

> The Apache Royale community is pleased to announce the release of Apache
> Royale 0.9.8.
>
> The Apache Royale project is the next generation of the Apache Flex SDK. It
> lets developers use MXML and ActionScript 3 to generate HTML/JS/CSS
> applications which can run natively in browsers. The cross-compiled code
> can also run on platforms like Electron or Apache Cordova (Adobe PhoneGap)
> to build mobile applications.
>
> This release should be considered ‘beta’ quality, although we’re very close
> to a 1.0 release and we have many applications in production at this point.
> The purpose of this release is to continue to gather feedback about
> Royale’s features and the project’s 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, however, may
> not handle all production needs.
>
> Changes in 0.9.8:
>
> Apache Royale Framework 0.9.8:
>
> https://github.com/apache/royale-asjs/blob/apache-royale-0.9.8/RELEASE_NOTES.md
> Apache Royale Compiler 0.9.8:
>
> https://github.com/apache/royale-compiler/blob/apache-royale-0.9.8/RELEASE_NOTES.md
>
> 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 [hidden email].
> For questions and feedback on the development of the source code in the
> release, send email to [hidden email].
>
> Apache Royale is available in source and binary form from the Apache
> mirrors:
>
> Source:
>
> https://www.apache.org/dyn/closer.lua/royale/0.9.8/apache-royale-0.9.8-src.tar.gz
>
>
> https://www.apache.org/dyn/closer.lua/royale/0.9.8/apache-royale-0.9.8-src.zip
>
> Binary:
>
> https://www.apache.org/dyn/closer.lua/royale/0.9.8/binaries/apache-royale-0.9.8-bin-js.tar.gz
>
> https://www.apache.org/dyn/closer.lua/royale/0.9.8/binaries/apache-royale-0.9.8-bin-js.zip
>
> Binary with SWF support:
>
> https://www.apache.org/dyn/closer.lua/royale/0.9.8/binaries/apache-royale-0.9.8-bin-js-swf.tar.gz
>
> https://www.apache.org/dyn/closer.lua/royale/0.9.8/binaries/apache-royale-0.9.8-bin-js-swf.zip
>
> When downloading from a mirror site, please remember to verify the
> downloads using signatures or MD5 hashes.
>
> The binary packages can also be installed via NPM.
>
> Mac:
>   sudo npm install @apache-royale/royale-js -g
>
> Or for SWF Support:
>   sudo npm install @apache-royale/royale-js-swf -g
>
> Windows:
>   npm install @apache-royale/royale-js -g
>
> Or for SWF Support:
>   npm install @apache-royale/royale-js-swf -g
>
> See the README for more information. The language reference (ASDoc) is
> here: https://royale.apache.org/asdoc/
>
> Additional documentation is here: https://apache.github.io/royale-docs/
>
> The documentation is still a work in progress. Volunteers are welcome to
> help improve it. Visit https://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
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.8 released

[Andrew Wetmore]

Hi:

Carlos left extensive, multi-step instructions for updating the website. I
have never tried them(!) but will start on them. The site needs an update
anyhow as our link to the Apache license does not appear where the ASF
guidelines want it.

a

On Tue, Aug 31, 2021 at 5:26 AM Yishay Weiss  wrote:

> I'll wait a few days before the official announcement.
>
> Andrew, do you think you could update the Royale site [1] in the meantime?
>
> Also, can anyone think of special release notes [2], like we had for
> previous versions?
>
> Thanks.
>
> [1] https://royale.apache.org/download/
> [2] https://github.com/apache/royale-asjs/wiki/Release-Notes-0.9.7
>
> On 2021/08/31 08:20:49, Yishay Weiss  wrote:
> > The Apache Royale community is pleased to announce the release of Apache
> > Royale 0.9.8.
> >
> > The Apache Royale project is the next generation of the Apache Flex SDK.
> It
> > lets developers use MXML and ActionScript 3 to generate HTML/JS/CSS
> > applications which can run natively in browsers. The cross-compiled code
> > can also run on platforms like Electron or Apache Cordova (Adobe
> PhoneGap)
> > to build mobile applications.
> >
> > This release should be considered ‘beta’ quality, although we’re very
> close
> > to a 1.0 release and we have many applications in production at this
> point.
> > The purpose of this release is to continue to gather feedback about
> > Royale’s features and the project’s 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, however, may
> > not handle all production needs.
> >
> > Changes in 0.9.8:
> >
> > Apache Royale Framework 0.9.8:
> >
> https://github.com/apache/royale-asjs/blob/apache-royale-0.9.8/RELEASE_NOTES.md
> > Apache Royale Compiler 0.9.8:
> >
> https://github.com/apache/royale-compiler/blob/apache-royale-0.9.8/RELEASE_NOTES.md
> >
> > 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 [hidden email].
> > For questions and feedback on the development of the source code in the
> > release, send email to [hidden email].
> >
> > Apache Royale is available in source and binary form from the Apache
> > mirrors:
> >
> > Source:
> >
> https://www.apache.org/dyn/closer.lua/royale/0.9.8/apache-royale-0.9.8-src.tar.gz
> >
> >
> https://www.apache.org/dyn/closer.lua/royale/0.9.8/apache-royale-0.9.8-src.zip
> >
> > Binary:
> >
> https://www.apache.org/dyn/closer.lua/royale/0.9.8/binaries/apache-royale-0.9.8-bin-js.tar.gz
> >
> https://www.apache.org/dyn/closer.lua/royale/0.9.8/binaries/apache-royale-0.9.8-bin-js.zip
> >
> > Binary with SWF support:
> >
> https://www.apache.org/dyn/closer.lua/royale/0.9.8/binaries/apache-royale-0.9.8-bin-js-swf.tar.gz
> >
> https://www.apache.org/dyn/closer.lua/royale/0.9.8/binaries/apache-royale-0.9.8-bin-js-swf.zip
> >
> > When downloading from a mirror site, please remember to verify the
> > downloads using signatures or MD5 hashes.
> >
> > The binary packages can also be installed via NPM.
> >
> > Mac:
> >   sudo npm install @apache-royale/royale-js -g
> >
> > Or for SWF Support:
> >   sudo npm install @apache-royale/royale-js-swf -g
> >
> > Windows:
> >   npm install @apache-royale/royale-js -g
> >
> > Or for SWF Support:
> >   npm install @apache-royale/royale-js-swf -g
> >
> > See the README for more information. The language reference (ASDoc) is
> > here: https://royale.apache.org/asdoc/
> >
> > Additional documentation is here: https://apache.github.io/royale-docs/
> >
> > The documentation is still a work in progress. Volunteers are welcome to
> > help improve it. Visit https://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
> >
> >
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: [DISCUSS] Discuss Release Apache Royale 0.9.8 RC6

[Andrew Wetmore]

This is great news

On Mon., Aug. 16, 2021, 3:22 p.m. Josh Tynjala, 
wrote:

> Thanks again for the hard work, Yishay!
>
> I ran the approval script successfully, I confirmed that the royale-asjs
> works correctly for powering code intelligence in vscode-as3mxml, and I can
> compile and run asconfigc for Node.js. Looks good to me.
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Mon, Aug 16, 2021 at 1:15 AM  wrote:
>
> > This is the discussion thread.
> >
> > Thanks,
> > Yishay Weiss
>

ApacheCon 2021 presentations

[Andrew Wetmore]

Hi, all:

I must submit the titles of our talks today. Have heard some input, and
this is my best guess at what would make a good presentation track:

* Build the project website with Apache Royale - (Alina Kazi)
* Using external JS libraries in an Apache Royale app - (Yishay Weiss)
* Beads: what they do, where they are, and how to use them in Apache Royale
- (Andrew Wetmore)
* Charts, dashboards, data display in Royale (focus on using eCharts?) -
(Andrew Wetmore)
* Localizing your Royale app - (Andrew Wetmore)

I am the placeholder presenter for three of the talks. Would be nice for
someone to take one of them on. If not, I will be asking for help over the
summer as I develop the presentations. All of you are smarter than I am on
this stuff, but I am willing to be glib on behalf of the project.

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Apache Royale official Website Development in Royale

[Andrew Wetmore]

I have created a repo for the proof of concept of the Royale official site:
https://github.com/apache/royale-official-site

On Sat, Apr 24, 2021 at 1:36 PM Andrew Wetmore  wrote:

> I will get to this on Sunday, I hope. Heavey schedule today!
>
> a
>
> On Sat, Apr 24, 2021 at 1:26 PM Alina Kazi  wrote:
>
>> Hi Andrew,
>>
>> I tried to create a repo for official website source code but i guess i
>> don't have access to create a repo on apache project. Can you create
>> github
>> repository for getting started for apache official website?
>>
>> Best Regards,
>> Alina Kazi
>>
>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>
>
>
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Apache Royale official Website Development in Royale

[Andrew Wetmore]

I will get to this on Sunday, I hope. Heavey schedule today!

a

On Sat, Apr 24, 2021 at 1:26 PM Alina Kazi  wrote:

> Hi Andrew,
>
> I tried to create a repo for official website source code but i guess i
> don't have access to create a repo on apache project. Can you create github
> repository for getting started for apache official website?
>
> Best Regards,
> Alina Kazi
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Casting workarounds

[Andrew Wetmore]

Where in the docs should I capture this wisdom?

On Wed., Apr. 21, 2021, 12:57 p.m. Josh Tynjala, 
wrote:

> Just like how things worked in Flash, you can't just cast a random `var
> obj:Object = {}` to a class. It needs to be a real instance of that class.
> The basic rule to keep in mind is this: You can use `as CustomVO` with
> something that was created with `new CustomVO()`. For any other type, an as
> cast returns null.
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Tue, Apr 20, 2021 at 4:24 PM gbarbosa  wrote:
>
> > Hi Royale,
> >
> > I was recently trying to cast an Object
> >
> > obj as CustomVO
> >
> > but it would always turn to null. The as operator kept thinking CustomVO
> > was
> > type Function() why would this be?
> >
> > The workaround ending up being to set the prototype.
> >
> > Object.setPrototypeOf(obj, CustomVO.prototype);
> >
> > and this successfully casted correctly. Is there a better way to do this?
> > Most likely something something to do with the structure of CustomVO? the
> > classes it extends?
> >
> > Thanks for your time.
> >
> > -Gabriel Barbosa
> >
> >
> >
> > --
> > Sent from: http://apache-royale-development.20373.n8.nabble.com/
> >
>

Re: Getting to 1.0

[Andrew Wetmore]

Good stuff. Should I start a Jira ticket and dump all this information into
it, so we don't lose our minds trying to find it again?

On Tue, Apr 20, 2021 at 4:40 PM GAbe Barbosa  wrote:

> Apologies for posting images. Console dump.  url:
>
> https://royale.apache.org/asdoc/#!mx.controls.advancedDataGridClasses/AdvancedDataGridColumn
>
> Mixed Content: The page at 'https://royale.apache.org/asdoc/' was loaded
> over HTTPS, but requested an insecure stylesheet '
> http://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css
> '.
> This request has been blocked; the content must be served over HTTPS.
> ASDoc.js:94 Mixed Content: The page at 'https://royale.apache.org/asdoc/'
> was loaded over HTTPS, but requested an insecure element '
>
> http://royale.codeoscopic.com/wp-content/uploads/2017/10/page-bg-1-1920x300.png
> '.
> This request was automatically upgraded to HTTPS, For more information see
> https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html
> G.fc @ ASDoc.js:94
> (index):1 Mixed Content: The page at 'https://royale.apache.org/asdoc/'
> was
> loaded over HTTPS, but requested an insecure element '
>
> http://royale.codeoscopic.com/wp-content/uploads/2018/01/apache-royale-tm-logo-light.svg
> '.
> This request was automatically upgraded to HTTPS, For more information see
> https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html
> ASDoc.js:60 Uncaught SyntaxError: Unexpected token t in JSON at position
> 8140
> at JSON.parse ()
> at uo.parse (ASDoc.js:392)
> at Kn.G.ed (ASDoc.js:320)
> at Hj (ASDoc.js:56)
> at Gj (ASDoc.js:57)
> at dp.G.dispatchEvent (ASDoc.js:55)
> at dp.J.dispatchEvent (ASDoc.js:60)
> at dp.Yn.dispatchEvent (ASDoc.js:353)
> at dp.G.Ln (ASDoc.js:471)
> (index):1 Mixed Content: The page at '
>
> https://royale.apache.org/asdoc/#!mx.controls.advancedDataGridClasses/AdvancedDataGridColumn
> '
> was loaded over HTTPS, but requested an insecure stylesheet '
> http://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css
> '.
> This request has been blocked; the content must be served over HTTPS.
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Getting to 1.0

[Andrew Wetmore]

This is very helpful.

a

On Tue, Apr 20, 2021 at 4:40 PM GAbe Barbosa  wrote:

> Apologies for posting images. Console dump.  url:
>
> https://royale.apache.org/asdoc/#!mx.controls.advancedDataGridClasses/AdvancedDataGridColumn
>
> Mixed Content: The page at 'https://royale.apache.org/asdoc/' was loaded
> over HTTPS, but requested an insecure stylesheet '
> http://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css
> '.
> This request has been blocked; the content must be served over HTTPS.
> ASDoc.js:94 Mixed Content: The page at 'https://royale.apache.org/asdoc/'
> was loaded over HTTPS, but requested an insecure element '
>
> http://royale.codeoscopic.com/wp-content/uploads/2017/10/page-bg-1-1920x300.png
> '.
> This request was automatically upgraded to HTTPS, For more information see
> https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html
> G.fc @ ASDoc.js:94
> (index):1 Mixed Content: The page at 'https://royale.apache.org/asdoc/'
> was
> loaded over HTTPS, but requested an insecure element '
>
> http://royale.codeoscopic.com/wp-content/uploads/2018/01/apache-royale-tm-logo-light.svg
> '.
> This request was automatically upgraded to HTTPS, For more information see
> https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html
> ASDoc.js:60 Uncaught SyntaxError: Unexpected token t in JSON at position
> 8140
> at JSON.parse ()
> at uo.parse (ASDoc.js:392)
> at Kn.G.ed (ASDoc.js:320)
> at Hj (ASDoc.js:56)
> at Gj (ASDoc.js:57)
> at dp.G.dispatchEvent (ASDoc.js:55)
> at dp.J.dispatchEvent (ASDoc.js:60)
> at dp.Yn.dispatchEvent (ASDoc.js:353)
> at dp.G.Ln (ASDoc.js:471)
> (index):1 Mixed Content: The page at '
>
> https://royale.apache.org/asdoc/#!mx.controls.advancedDataGridClasses/AdvancedDataGridColumn
> '
> was loaded over HTTPS, but requested an insecure stylesheet '
> http://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css
> '.
> This request has been blocked; the content must be served over HTTPS.
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Getting to 1.0

[Andrew Wetmore]

I have not done any work on the ASDocs section. We would be glad of any
help we can get to make it more useful. Does it need a color guide at the
top to indicate what blue, red, green mean...and then I guess we would have
to check that that is implemented consistently.

I cannot see the two images you attached, as the email system is for
plain-text messages only. If you can find those issues again and drop them
into paste.apache.org, I believe you could share the links in a message.

@Alex Harui  do you have any thoughts about why the
ASDocs might not display on occasion? I have run into that too, and have
had to basically refresh the browser window and try mys search again.

a



On Tue, Apr 20, 2021 at 2:59 PM GAbe Barbosa  wrote:

> I'm specifically talking about the https://royale.apache.org/asdoc and
> I'm using mostly emulation components. This is on the latest chrome browser
> on desktop and mobile (android). If there's another browser I should be
> using please let me know. Here's the errors I see all the time. Honestly
> never checked the console till now, that's on me.
> [image: asdoc_royale.PNG]
>
> [image: asdoc_royale_console.PNG]
> From my perspective the docs are what should keep a developer from having
> to dig into the source code. One should be able to always trust the docs.
> Right now I don't. Here are my assumptions.
> Blue properties/methods are implemented
> Red properties/methods are NOT implemented
> Green properties/methods added specifically for Royale?
>
> An example:
> mx:UIComponent the docs show the public function of
> "invalidateParentSizeAndDisplayList()" as blue
> which I'm assuming means implemented. When I dig into the source code I
> see that this is actually a protected function and a trace indicating this
> is not implemented.
>
> All that to say, I'm very willing to help with documentation and be the
> change I wish to see. I guess I'm just stressing the importance of this.
>
>
>
> On Tue, Apr 20, 2021 at 9:30 AM Andrew Wetmore 
> wrote:
>
>> This is very important feedback. I have never had the docs fail to load,
>> so
>> could you give more details? On a particular browser? on a particular
>> device?
>>
>> As to content, aside from performance, what would you like to see more of
>> in the docs?
>>
>> Andrew
>>
>> On Tue, Apr 20, 2021 at 1:27 PM GAbe Barbosa 
>> wrote:
>>
>> > From a new developer perspective the documentation is awful. Half the
>> time
>> > the docs won't even load and the other half you have to go searching
>> > through the source code anyway to see if that method is commented out. I
>> > use the flex as3 doc and go straight to the source code now. Not a fun
>> way
>> > to develop.
>> >
>> > On Mon, Apr 19, 2021 at 6:44 AM Andrew Wetmore 
>> > wrote:
>> >
>> > > I agree about the documentation. If, indeed, that is the weak point, I
>> > will
>> > > see what I can do to improve it over the coming months. First stop
>> will
>> > be
>> > > to ask folks to indicate what additional doc they would like to
>> see...ah,
>> > > maybe another wiki page for capturing suggestions.
>> > >
>> > > If 0.98 actually happens in the next couple of months, might we dare
>> to
>> > > think of 1.0 before the end of the year??
>> > >
>> > > a
>> > >
>> > > On Mon, Apr 19, 2021 at 6:36 AM Harbs  wrote:
>> > >
>> > > > I agree with this.
>> > > >
>> > > > I personally think that the strongest reason to not call it “1.0” is
>> > gaps
>> > > > in documentation. I wish I was better on that front, and we’d be in
>> big
>> > > > trouble without Andrew… ;)
>> > > >
>> > > > Harbs
>> > > >
>> > > > > On Apr 19, 2021, at 11:23 AM, Yishay Weiss <
>> yishayj...@hotmail.com>
>> > > > wrote:
>> > > > >
>> > > > > There are already some Royale apps in production so I think we are
>> > > ready
>> > > > for 1.0 in terms of code. Whether to call it 1.0 is probably a
>> > marketing
>> > > > decision at this stage. There will be announcements and (hopefully)
>> > > > feedback to take care of.
>> > > > >
>> > > > > At least that’s how I think of it.
>> > > > >
>> > > > >
>> > > > >
>> > > > > From: Andrew Wetmore&l

Re: Getting to 1.0

[Andrew Wetmore]

This is very important feedback. I have never had the docs fail to load, so
could you give more details? On a particular browser? on a particular
device?

As to content, aside from performance, what would you like to see more of
in the docs?

Andrew

On Tue, Apr 20, 2021 at 1:27 PM GAbe Barbosa  wrote:

> From a new developer perspective the documentation is awful. Half the time
> the docs won't even load and the other half you have to go searching
> through the source code anyway to see if that method is commented out. I
> use the flex as3 doc and go straight to the source code now. Not a fun way
> to develop.
>
> On Mon, Apr 19, 2021 at 6:44 AM Andrew Wetmore 
> wrote:
>
> > I agree about the documentation. If, indeed, that is the weak point, I
> will
> > see what I can do to improve it over the coming months. First stop will
> be
> > to ask folks to indicate what additional doc they would like to see...ah,
> > maybe another wiki page for capturing suggestions.
> >
> > If 0.98 actually happens in the next couple of months, might we dare to
> > think of 1.0 before the end of the year??
> >
> > a
> >
> > On Mon, Apr 19, 2021 at 6:36 AM Harbs  wrote:
> >
> > > I agree with this.
> > >
> > > I personally think that the strongest reason to not call it “1.0” is
> gaps
> > > in documentation. I wish I was better on that front, and we’d be in big
> > > trouble without Andrew… ;)
> > >
> > > Harbs
> > >
> > > > On Apr 19, 2021, at 11:23 AM, Yishay Weiss 
> > > wrote:
> > > >
> > > > There are already some Royale apps in production so I think we are
> > ready
> > > for 1.0 in terms of code. Whether to call it 1.0 is probably a
> marketing
> > > decision at this stage. There will be announcements and (hopefully)
> > > feedback to take care of.
> > > >
> > > > At least that’s how I think of it.
> > > >
> > > >
> > > >
> > > > From: Andrew Wetmore<mailto:cottag...@gmail.com>
> > > > Sent: Sunday, April 18, 2021 3:42 PM
> > > > To: Apache Royale Development<mailto:dev@royale.apache.org>
> > > > Subject: Getting to 1.0
> > > >
> > > > I know it is not in the nature of Apache projects to have timelines,
> > > since
> > > > each volunteer chooses to work on the task that attracts them.
> > > However...do
> > > > we know what we need to do to get from now (almost 0.9.8) to a 1.0
> > > release?
> > > > What critical elements are lacking?
> > > >
> > > > For me, there are big gaps in documentation, and I will try to attend
> > to
> > > > some of them.
> > > >
> > > > The release-build process still seems slow and painful, but I don't
> > know
> > > > that that is a blocker to 1.0.
> > > >
> > > > Anything else?
> > > >
> > > > a
> > > >
> > > > --
> > > > Andrew Wetmore
> > > >
> > >
> > >
> >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/
> >
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Getting to 1.0

[Andrew Wetmore]

I agree about the documentation. If, indeed, that is the weak point, I will
see what I can do to improve it over the coming months. First stop will be
to ask folks to indicate what additional doc they would like to see...ah,
maybe another wiki page for capturing suggestions.

If 0.98 actually happens in the next couple of months, might we dare to
think of 1.0 before the end of the year??

a

On Mon, Apr 19, 2021 at 6:36 AM Harbs  wrote:

> I agree with this.
>
> I personally think that the strongest reason to not call it “1.0” is gaps
> in documentation. I wish I was better on that front, and we’d be in big
> trouble without Andrew… ;)
>
> Harbs
>
> > On Apr 19, 2021, at 11:23 AM, Yishay Weiss 
> wrote:
> >
> > There are already some Royale apps in production so I think we are ready
> for 1.0 in terms of code. Whether to call it 1.0 is probably a marketing
> decision at this stage. There will be announcements and (hopefully)
> feedback to take care of.
> >
> > At least that’s how I think of it.
> >
> >
> >
> > From: Andrew Wetmore<mailto:cottag...@gmail.com>
> > Sent: Sunday, April 18, 2021 3:42 PM
> > To: Apache Royale Development<mailto:dev@royale.apache.org>
> > Subject: Getting to 1.0
> >
> > I know it is not in the nature of Apache projects to have timelines,
> since
> > each volunteer chooses to work on the task that attracts them.
> However...do
> > we know what we need to do to get from now (almost 0.9.8) to a 1.0
> release?
> > What critical elements are lacking?
> >
> > For me, there are big gaps in documentation, and I will try to attend to
> > some of them.
> >
> > The release-build process still seems slow and painful, but I don't know
> > that that is a blocker to 1.0.
> >
> > Anything else?
> >
> > a
> >
> > --
> > Andrew Wetmore
> >
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Getting to 1.0

[Andrew Wetmore]

I know it is not in the nature of Apache projects to have timelines, since
each volunteer chooses to work on the task that attracts them. However...do
we know what we need to do to get from now (almost 0.9.8) to a 1.0 release?
What critical elements are lacking?

For me, there are big gaps in documentation, and I will try to attend to
some of them.

The release-build process still seems slow and painful, but I don't know
that that is a blocker to 1.0.

Anything else?

a

-- 
Andrew Wetmore

Royale at ApacheCon 2021 - topics

[Andrew Wetmore]

Hi, all:

I have edited the wiki page [1] about Royale at ApacheCon 2021, creating a
short-list of titles for presentations and a second list of other ideas. I
have to submit our list within two weeks, so we need to lock down both what
the topics are and who is presenting them fairly soon.

As a reminder, each presentation slot is only 45 minutes, and it is nice if
we can leave the last ten or even fifteen minutes for questions, comments,
and chat, so really the presenter is only in the spotlight for about 30
minutes.

As coordinator, I will at least co-present each session, so nobody has to
do a presentation on their own.

-- 
Andrew Wetmore


1. https://github.com/apache/royale-asjs/wiki/Royale-at-ApacheCon-2021

Re: Use Royale to build the Royale website?

[Andrew Wetmore]

Hi, all:

I have created a wiki page [1] where we can scope out developing the Royale
website as built using Royale. I have suggested some requirements, some
"nice to have" things and some things that are not required; however these
are just my ideas. Input from others until we reach consensus would be
useful.

Here is one specific point: there are a couple of abandoned efforts to
build the Royale site using Royale. Do we use these repositories, or create
a new one for this effort?

a

1.
https://github.com/apache/royale-asjs/wiki/Royale-project-site-built-with-Royale

On Fri, Apr 16, 2021 at 12:29 PM Alina Kazi  wrote:

> Congrats Andrew.
>
> Yes we can add viewstates (includeIn), phone/tablet/desktop Numerator
> denominator to adjust the view on different devices, common header and
> footer and much more.
> We'll be waiting for the wiki page tomorrow to get started.
>
> Thanks,
> Alina Kazi
>
> On Fri, 16 Apr 2021, 7:29 PM Piotr Zarzycki, 
> wrote:
>
> > Congrats Andrew!
> >
> > pt., 16 kwi 2021 o 13:31 Andrew Wetmore 
> napisał(a):
> >
> > > Today my wife and I have appointments, a long drive from home, to get
> our
> > > first COVID-19 injections. This will probably use up most of the day,
> > > leaving aside possible side-effects, so I likely will not have the wiki
> > > page about the web site ready to receive ideas and concerns until
> > tomorrow
> > > at the earliest.
> > >
> > > a
> > >
> > > On Thu, Apr 15, 2021 at 8:33 PM Maria Jose Esteve 
> > > wrote:
> > >
> > > > What dizziness! jajajaja
> > > >
> > > > Hiedra
> > > >
> > > > -Mensaje original-
> > > > De: Andrew Wetmore 
> > > > Enviado el: viernes, 16 de abril de 2021 1:29
> > > > Para: Apache Royale Development 
> > > > Asunto: Re: Use Royale to build the Royale website?
> > > >
> > > > This is great.
> > > >
> > > > To start, I think I will create a wiki page so we can capture what we
> > > must
> > > > have and what we would like to have in the website. For me, our
> website
> > > > must communicate useful and engaging information about our project
> and
> > > what
> > > > one can do with Royale. I would also like to include some features to
> > > > demonstrate a little bit of what Royale can do--maybe viewstates to
> > > manage
> > > > what displays when, localization (at least some of the site),
> > responsive
> > > so
> > > > it appears well on laptops and mobile devices, use of CSS, and other
> > > > stuff...and then we can use the website itself as a demonstration of
> > > > Royale's versatility.
> > > >
> > > > The Infra guidelines say a project's site should not be dynamic, in
> the
> > > > sense of using HTTP calls to get data that it then displays: the site
> > > > should be "flat".  But we may find that Royale code compiled to
> > > JavaScript
> > > > can do lots of interestng things wiithout breaking the Infra rules.
> > > >
> > > > I will set up the wiki page tomorrow and let you all know that it is
> > > > available for adding ideas.
> > > >
> > > > Andrew
> > > >
> > > > On Thu, Apr 15, 2021 at 5:42 PM Alina Kazi 
> > > > wrote:
> > > >
> > > > > Hi,
> > > > > Great Maria and really its very good to show it in ApacheCon 2021.
> > > > >
> > > > > Great Idea Andrew, I would also love to contribute in any way I
> can.
> > > > > Also, If you have some design in mind. Share with us.
> > > > > Create a source repository,so we can start with jewel basic flat
> > theme
> > > > > or any other option that community suggests. We start migrating
> > > > > wordpress website step by step. Until we have virtual machine or
> > other
> > > > stuff ready.
> > > > >
> > > > > Alina Kazi
> > > > >
> > > > >
> > > > > On Thu, 15 Apr 2021, 10:03 PM Maria Jose Esteve, <
> mjest...@iest.com>
> > > > > wrote:
> > > > >
> > > > > > Hi guys,
> > > > > >
> > > > > > Andrew, I can help, I think the community has to make an effort
> if
> > > > > > we
> > > > > want
> > > > > > to get to ApacheCon 2021 
> >

Re: MD parser

[Andrew Wetmore]

Thank you! I will look into it. I found a couple of other projects and
tutorials, like this porting of an md parser to AS:
https://gist.github.com/cstrahan/648771.

Many good resources...so little time.

a

On Fri, Apr 16, 2021 at 2:35 AM Alex Harui  wrote:

> Maybe this: https://github.com/showdownjs/showdown
>
> HTH,
> -Alex
>
> On 4/15/21, 4:34 PM, "Andrew Wetmore"  wrote:
>
> I am playing with building a parser to convert markdown to HTML as an
> ActionScript component for Royale. I looked around a bit and could not
> see
> an existing one. Stop me now if there is one!
>
> A
>
> --
> Andrew Wetmore
>
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2Fdata=04%7C01%7Caharui%40adobe.com%7Cfdfca35ef9684b77876808d90066f406%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637541264446507892%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=GFtxr6MpkB%2Fnsx2f%2F%2FzZAAgueCHvumO4AM%2F%2F84lXHRQ%3Dreserved=0
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Use Royale to build the Royale website?

[Andrew Wetmore]

Today my wife and I have appointments, a long drive from home, to get our
first COVID-19 injections. This will probably use up most of the day,
leaving aside possible side-effects, so I likely will not have the wiki
page about the web site ready to receive ideas and concerns until tomorrow
at the earliest.

a

On Thu, Apr 15, 2021 at 8:33 PM Maria Jose Esteve  wrote:

> What dizziness! jajajaja
>
> Hiedra
>
> -Mensaje original-----
> De: Andrew Wetmore 
> Enviado el: viernes, 16 de abril de 2021 1:29
> Para: Apache Royale Development 
> Asunto: Re: Use Royale to build the Royale website?
>
> This is great.
>
> To start, I think I will create a wiki page so we can capture what we must
> have and what we would like to have in the website. For me, our website
> must communicate useful and engaging information about our project and what
> one can do with Royale. I would also like to include some features to
> demonstrate a little bit of what Royale can do--maybe viewstates to manage
> what displays when, localization (at least some of the site), responsive so
> it appears well on laptops and mobile devices, use of CSS, and other
> stuff...and then we can use the website itself as a demonstration of
> Royale's versatility.
>
> The Infra guidelines say a project's site should not be dynamic, in the
> sense of using HTTP calls to get data that it then displays: the site
> should be "flat".  But we may find that Royale code compiled to JavaScript
> can do lots of interestng things wiithout breaking the Infra rules.
>
> I will set up the wiki page tomorrow and let you all know that it is
> available for adding ideas.
>
> Andrew
>
> On Thu, Apr 15, 2021 at 5:42 PM Alina Kazi 
> wrote:
>
> > Hi,
> > Great Maria and really its very good to show it in ApacheCon 2021.
> >
> > Great Idea Andrew, I would also love to contribute in any way I can.
> > Also, If you have some design in mind. Share with us.
> > Create a source repository,so we can start with jewel basic flat theme
> > or any other option that community suggests. We start migrating
> > wordpress website step by step. Until we have virtual machine or other
> stuff ready.
> >
> > Alina Kazi
> >
> >
> > On Thu, 15 Apr 2021, 10:03 PM Maria Jose Esteve, 
> > wrote:
> >
> > > Hi guys,
> > >
> > > Andrew, I can help, I think the community has to make an effort if
> > > we
> > want
> > > to get to ApacheCon 2021 
> > >
> > > Have you thought about a redesign of the website or a "translation"?
> > >
> > > How could I contribute?
> > >
> > >
> > >
> > > Hiedra
> > >
> > >
> > >
> > > -Mensaje original-
> > > De: Andrew Wetmore  Enviado el: jueves, 15 de
> > > abril de 2021 1:51
> > > Para: Apache Royale Development 
> > > Asunto: Use Royale to build the Royale website?
> > >
> > >
> > >
> > > Hi:
> > >
> > >
> > >
> > > At the moment the Royale website depends on a private server running
> > > WordPress. I wonder if it is time to build and deploy it using
> > > Royale itself.
> > >
> > >
> > >
> > > We don't need the great strengths of Royale--dynamic display, subtle
> > > data-processing, and so on--to support the site. It is (as all
> > > projects sites are intended to be) a flat, relatively static
> > > website. That should mean that running our own website with the aid
> > > of our own tool should be far from impossible.
> > >
> > >
> > >
> > > What is required? If I understand correctly, we would need Infra to
> > > provide a virtual machine on which we could install and run a stable
> > > instance of Royale, and a repository of the site's source code in
> > > MXML
> > and
> > > AS files, just like a real Royale application.. Each time we updated
> > > a
> > page
> > > or a file in the website repository, Infra's automated tools would
> > > set
> > off
> > > a build and deployment of the updated site.
> > >
> > >
> > >
> > > Some time ago a proof-of-concept was partly built to do this very
> > > thing, so we have some resources to start from.
> > >
> > >
> > >
> > > Benefits:
> > >
> > >
> > >
> > > -- Since it is a simple website, it should probably be an exercise
> > > contributors and committers at many skill levels could help work on.
> > >
> > > -- It would give us a "brag" to point to.
> > >
> > > -- We would move over to open-source resources, rather than those of
> > > WordPress..
> > >
> > > -- Infra has an efficient and stable CI process in place that can
> > > work with Royale's command-line to trigger builds and deployment.
> > >
> > > -- Other
> > >
> > >
> > >
> > > Costs:
> > >
> > >
> > >
> > > -- Time to migrate the existing site into Royale assets.
> > >
> > > -- Other?
> > >
> > >
> > >
> > > What do you all think of such a proposal?
> > >
> > >
> > >
> > > a
> > >
> > >
> > >
> > > --
> > >
> > > Andrew Wetmore
> > >
> >
>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

MD parser

[Andrew Wetmore]

I am playing with building a parser to convert markdown to HTML as an
ActionScript component for Royale. I looked around a bit and could not see
an existing one. Stop me now if there is one!

A

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Use Royale to build the Royale website?

[Andrew Wetmore]

This is great.

To start, I think I will create a wiki page so we can capture what we must
have and what we would like to have in the website. For me, our website
must communicate useful and engaging information about our project and what
one can do with Royale. I would also like to include some features to
demonstrate a little bit of what Royale can do--maybe viewstates to manage
what displays when, localization (at least some of the site), responsive so
it appears well on laptops and mobile devices, use of CSS, and other
stuff...and then we can use the website itself as a demonstration of
Royale's versatility.

The Infra guidelines say a project's site should not be dynamic, in the
sense of using HTTP calls to get data that it then displays: the site
should be "flat".  But we may find that Royale code compiled to JavaScript
can do lots of interestng things wiithout breaking the Infra rules.

I will set up the wiki page tomorrow and let you all know that it is
available for adding ideas.

Andrew

On Thu, Apr 15, 2021 at 5:42 PM Alina Kazi  wrote:

> Hi,
> Great Maria and really its very good to show it in ApacheCon 2021.
>
> Great Idea Andrew, I would also love to contribute in any way I can.
> Also, If you have some design in mind. Share with us.
> Create a source repository,so we can start with jewel basic flat theme or
> any other option that community suggests. We start migrating wordpress
> website step by step. Until we have virtual machine or other stuff ready.
>
> Alina Kazi
>
>
> On Thu, 15 Apr 2021, 10:03 PM Maria Jose Esteve, 
> wrote:
>
> > Hi guys,
> >
> > Andrew, I can help, I think the community has to make an effort if we
> want
> > to get to ApacheCon 2021 
> >
> > Have you thought about a redesign of the website or a "translation"?
> >
> > How could I contribute?
> >
> >
> >
> > Hiedra
> >
> >
> >
> > -Mensaje original-
> > De: Andrew Wetmore 
> > Enviado el: jueves, 15 de abril de 2021 1:51
> > Para: Apache Royale Development 
> > Asunto: Use Royale to build the Royale website?
> >
> >
> >
> > Hi:
> >
> >
> >
> > At the moment the Royale website depends on a private server running
> > WordPress. I wonder if it is time to build and deploy it using Royale
> > itself.
> >
> >
> >
> > We don't need the great strengths of Royale--dynamic display, subtle
> > data-processing, and so on--to support the site. It is (as all projects
> > sites are intended to be) a flat, relatively static website. That should
> > mean that running our own website with the aid of our own tool should be
> > far from impossible.
> >
> >
> >
> > What is required? If I understand correctly, we would need Infra to
> > provide a virtual machine on which we could install and run a stable
> > instance of Royale, and a repository of the site's source code in MXML
> and
> > AS files, just like a real Royale application.. Each time we updated a
> page
> > or a file in the website repository, Infra's automated tools would set
> off
> > a build and deployment of the updated site.
> >
> >
> >
> > Some time ago a proof-of-concept was partly built to do this very thing,
> > so we have some resources to start from.
> >
> >
> >
> > Benefits:
> >
> >
> >
> > -- Since it is a simple website, it should probably be an exercise
> > contributors and committers at many skill levels could help work on.
> >
> > -- It would give us a "brag" to point to.
> >
> > -- We would move over to open-source resources, rather than those of
> > WordPress..
> >
> > -- Infra has an efficient and stable CI process in place that can work
> > with Royale's command-line to trigger builds and deployment.
> >
> > -- Other
> >
> >
> >
> > Costs:
> >
> >
> >
> > -- Time to migrate the existing site into Royale assets.
> >
> > -- Other?
> >
> >
> >
> > What do you all think of such a proposal?
> >
> >
> >
> > a
> >
> >
> >
> > --
> >
> > Andrew Wetmore
> >
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Use Royale to build the Royale website?

[Andrew Wetmore]

Hi:

At the moment the Royale website depends on a private server running
WordPress. I wonder if it is time to build and deploy it using Royale
itself.

We don't need the great strengths of Royale--dynamic display, subtle
data-processing, and so on--to support the site. It is (as all projects
sites are intended to be) a flat, relatively static website. That should
mean that running our own website with the aid of our own tool should be
far from impossible.

What is required? If I understand correctly, we would need Infra to provide
a virtual machine on which we could install and run a stable instance of
Royale, and a repository of the site's source code in MXML and AS
files, just like a real Royale application.. Each time we updated a page or
a file in the website repository, Infra's automated tools would set off a
build and deployment of the updated site.

Some time ago a proof-of-concept was partly built to do this very thing, so
we have some resources to start from.

Benefits:

-- Since it is a simple website, it should probably be an exercise
contributors and committers at many skill levels could help work on.
-- It would give us a "brag" to point to.
-- We would move over to open-source resources, rather than those of
WordPress..
-- Infra has an efficient and stable CI process in place that can work with
Royale's command-line to trigger builds and deployment.
-- Other

Costs:

-- Time to migrate the existing site into Royale assets.
-- Other?

What do you all think of such a proposal?

a

-- 
Andrew Wetmore

ApacheCon 2021 in September: tickets available

[Andrew Wetmore]

https://hopin.com/events/apachecon-2021-home

Great event to take part in. We hope to have a track with five or six
presentations. Anyone who wants to help me with the presos is very welcome!

https://github.com/apache/royale-asjs/wiki/Royale-at-ApacheCon-2021

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Build failed in Jenkins: royale-asjs #2690

[Andrew Wetmore]

This has been happening so long I thought it was a feature

On Tue, Apr 6, 2021, 7:33 PM Josh Tynjala  wrote:

> In case anyone else has been wondering about the failing royale-asjs CI
> build (in particular, the Mustella tests) that's been happening since
> January, I was able to track down the cause to this pull request.
>
> https://github.com/apache/royale-asjs/pull/1041
>
> While I was able to figure out where the issue started, I'm not really
> familiar enough with the framework side of Royale (I contribute mostly to
> the compiler) to know where to start to fix it. However, Edward Stangler
> (the author of the PR) says that he'll be looking into providing a better
> fix later this week.
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Tue, Apr 6, 2021 at 11:20 AM  wrote:
>
> > See <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs/2690/display/redirect
> > >
> >
> > Changes:
> >
> >
> > --
> > [...truncated 2.07 MB...]
> >  [echo] playerglobal.version is 11.7
> >  [echo] playerglobal.swc is C:\adobe\flash/11.7/playerglobal.swc
> >
> > check-air-home:
> >  [echo] AIR_HOME is C:\adobe\air\4.0\AdobeAIRSDK
> >
> > check-compiler-home:
> >
> > check-compile-env:
> >  [echo] OS: Windows Server 2016 / 10.0 / amd64
> >  [echo] VM: Java HotSpot(TM) 64-Bit Server VM / 25.201-b09
> >  [echo] Java: 1.8.0_201
> >  [echo] Ant: Apache Ant(TM) version 1.10.7 compiled on September 1
> > 2019 Ant Java Version: 1.8
> >
> > prepare:
> >
> > compile:
> >
> > flat-ui-icons:
> >  [java] Error: Unable to access jarfile <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/fontsrc/${env.ROYALE_HOME}/lib/mxmlc.jar
> > >
> >  [java] Java Result: 1
> >
> > main:
> >
> > main:
> >
> > tweak-for-jsonly:
> >
> > ide:
> >
> > post-build:
> > [mkdir] Created dir: <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/locale
> > >
> > [mkdir] Created dir: <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/mx
> > >
> > [mkdir] Created dir: <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/rsls
> > >
> > [mkdir] Created dir: <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/themes/Halo
> > >
> >  [copy] Copying 1 file to <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/themes/Halo
> > >
> >  [copy] Copying 1 file to <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks
> > >
> > [touch] Creating <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/macfonts.ser
> > >
> > [touch] Creating <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/winfonts.ser
> > >
> > [touch] Creating <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/localfonts.ser
> > >
> >
> > last-message-if-airsdk:
> >
> > main:
> >  [echo] ant main target completed on 04/06/2021 06:19:39 PM
> >
> > sample-themes:
> >
> > check-runtime-env:
> >
> > runtime-setup:
> >
> > mustella-setup:
> >
> > clean:
> >[delete] Deleting: <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/mustella/mustella.swc
> > >
> >
> > check-compiler-home:
> >
> > check-compiler:
> >
> > compile:
> >  [echo] Compiling mustella.swc
> >  [echo] ROYALE_HOME: <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/
> > >
> >  [echo] ROYALE_COMPILER_HOME: <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/js
> > >
> >  [java] args:
> >  [java] +royalelib=<
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks
> > >
> >  [java] +playerglobal.version=11.7
> >  [java] +env.PLAYERGLOBAL_HOME=C:\adobe\flash
> >  [java] +env.AIR_HOME=C:\adobe\air\4.0\AdobeAIRSDK
> >  [java] -compiler.strict-xml=true
> >  [java] -compiler.targets=SWF,JSRoyale
> >  [java] -output=<
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/mustella/mustella.swc
> > >
> >  [java] -load-config=<
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/mustella/src/main/config/compile-swf-config.xml
> > >
> >  [java] -js-load-config=<
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/js-config.xml
> > >
> >  [java] -js-load-config+=<
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/mustella/src/main/config/compile-js-config.xml
> > >
> >  [java] target:SWF
> >  [java] target:JSRoyale
> >  [java] COMPC
> >  [java] Loading configuration: <
> >
> 

Re: Apache Royale wordpress apps - plugin

[Andrew Wetmore]

Sounds good.

What stops us from building the full Royale website in Royale, rather than
relying on WordPress or other frameworks?

a

On Tue, Mar 23, 2021 at 11:58 AM Piotr Zarzycki 
wrote:

> Hey Guys,
>
> In Prominic we have found a need of having plugin which allows us include
> in an easy way Apache Royale scripts into our websites. Essentially the
> idea was to replace some Wordpress forms with written in Royale.
>
> We have created plugin to managed that process called so far "Apache Royale
> wordpress plugin". We are probably under that plugin umbrella would like
> to have more functionalities in future related to Apache Royale in
> connection to Wordpress.
>
> Is there any problem that if we place such plugin into public wordpress
> repository ?
>
> Thanks,
> --
>
> Piotr Zarzycki
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: So long and thanks for the fish ...

[Andrew Wetmore]

Hi, Chris:

This sounds like a great milestone achieved. Can I ask you to stay in the
discussion for a few more days, in case someone runs into something that
needs further clarification?

Thank you.

a

On Sun, Mar 21, 2021 at 9:54 AM Christofer Dutz 
wrote:

> Hi all,
>
> So, I am now considering my Job on the Maven part of the Royale build done.
>
> You should now:
>
>   *   Have a fully working Maven build including tooling for easy
> onboarding
>   *   Have a fully working Jenkins Setup on Apache Infra that should not
> stop working regularly because of exceeded resource-credits (
> https://ci-builds.apache.org/job/Royale/)
>   *   Have a fully working distribution built with Maven
>   *   Have nightly distributions available on https://nightlies.apache.org
> which could be used in the installer (
> https://nightlies.apache.org/Royale/Royale-asjs/)
>   *   Have a working Maven release-build, which could be used to do
> Maven-based releases (If you stick to typical Maven release requirements
> and not the ones the project decided on ... I can't say which of these
> might not be satisfied, but I would like you to challenge, if they are
> really needed)
>   *   Have a tutorial Video I did, explaining how to release Apache Royale
> with Maven, here:
> https://drive.google.com/drive/folders/1BDKG-zPW3CoWLI0KQJDO5PGyEJQtKRb4?usp=sharing
>
> I'm going to leave the discussion on what to do with this up to you.
>
> I consider my work on the Maven part of Royale done, which I strangely
> still felt responsible for, even after being kicked out of the project some
> years ago.
>
> You should now be able to continue on your own.
>
> Good luck,
>   Chris
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: using externall javascript libraries (quilljs rich text editor)

[Andrew Wetmore]

@Yishay, would you consider giving a presentation at ApacheCon 2021 on
using external JS libraries with a Royale app? Since you have a running
example, you are halfway done with preparing your talk!

Andrew

On Mon, Mar 8, 2021 at 5:53 AM Yishay Weiss  wrote:

> I got something working for my app and the emulation components with these
> 2 classes
>
> <https://cdn.quilljs.com/1.3.6/quill.snow.css>
> package components
> {
> import mx.core.UIComponent;
> public class SMQuillEditor extends UIComponent
> {
> public function SMQuillEditor()
> {
> super();
> }
>
>
> private var subComponent:UIComponent;
> private var quill:Quill;
> override public function addedToParent():void
> {
> super.addedToParent();
> if (!subComponent)
> {
> subComponent = new UIComponent;
> subComponent.percentWidth = 100;
> addElement(subComponent);
> quill = new Quill(subComponent.element, {"theme": "snow"});
> }
> }
> }
> }
>
> and
>
> package
> {
> /**
> * @externs
> */
> public class Quill
> {
> /**
> * 
> * var script = document.createElement("script");
> * script.setAttribute("src", "https://cdn.quilljs.com/1.3.6/quill.js;);
> * document.head.appendChild(script);
> * var link = document.createElement("link");
> * link.setAttribute("rel", "stylesheet");
> * link.setAttribute("type", "text/css");
> * link.setAttribute("href", "https://cdn.quilljs.com/1.3.6/quill.snow.css
> ");
> * document.head.appendChild(link);
> * 
> */
> public function Quill(element:*, config:*){}
>
> }
> }
>
> Hope this helps.
>
> 
> From: Yishay Weiss 
> Sent: Sunday, March 7, 2021 7:22 AM
> To: dev@royale.apache.org 
> Subject: Re: using externall javascript libraries (quilljs rich text
> editor)
>
> Check out TinyEditor as well in the mx package.
> ________
> From: anam 
> Sent: Friday, March 5, 2021 7:30 PM
> To: dev@royale.apache.org 
> Subject: Re: using externall javascript libraries (quilljs rich text
> editor)
>
> Great, i think it will be very help full :)
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Fwd: Call for Presentations for ApacheCon 2021 now open

[Andrew Wetmore]

Hi, all. i have attached below the call for presentations for ApacheCon
2021. The submission deadline is May 1.

I have created a wiki page [1] where we can decide on what we want to
present in the Royale track and figure out what we need to do to support
those presentations (who will be the presenter, timing, resources, and so
on). Each presentation slot will probably be 45 minutes.

I suggest we decide together what our presentations will be. Then I can
submit them all on behalf of Royale.


Andrew

[1] https://github.com/apache/royale-asjs/wiki/Royale-at-ApacheCon-2021

-- Forwarded message -
From: Rich Bowen 
Date: Mon, Mar 8, 2021 at 9:53 AM
Subject: Call for Presentations for ApacheCon 2021 now open
To: 


The ApacheCon Planners and the Apache Software Foundation are pleased to
announce that ApacheCon@Home will be held online, September 21-23, 2021.
Once again, we’ll be featuring content from dozens of our projects, as
well as content about our community, how Apache works, business models
around Apache software, the legal aspects of open source, and many other
topics.

Last year’s virtual ApacheCon@Home event was a big success, with 5,745
registrants from more than 150 countries, spanning every time zone, with
the virtual format delivering content to attendees who would never have
attended an in-person ApacheCon (83% of post-event poll responders in
2020 indicated this was their first ApacheCon ever)!

Given the great participation and excitement for last year’s event, we
are announcing the Call for Presentations is now open to presenters from
around the world until May 1st. Talks can be focused on the topics
above, as well as any of our amazing projects. Submit your talks today!

https://acah2021.jamhosted.net/

We look forward to reviewing your contribution to one of the most
popular open source software events in the world!


-- 
Rich Bowen, VP Conferences
The Apache Software Foundation
https://apachecon.com/
@apachecon


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Planning for ApacheCon 2021

[Andrew Wetmore]

It will be an all-virtual event again, as it was in 2020.

On Wed, Mar 3, 2021 at 10:31 AM Harbs  wrote:

> Cool. Thanks for working on this.
>
> What is the plan for ApacheCon? Is it going to be a virtual event?
>
> > On Mar 3, 2021, at 4:17 PM, Andrew Wetmore  wrote:
> >
> > Hi, all:
> >
> > I have started a wiki page [1] where we can assemble proposals for
> > presentations at ApacheCon 2021 (in September), select the most likely
> > ideas, and work through the details of getting them ready. Contributions
> > most welcome.
> >
> > 1. https://github.com/apache/royale-asjs/wiki/Royale-at-ApacheCon-2021
> >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Planning for ApacheCon 2021

[Andrew Wetmore]

Hi, all:

I have started a wiki page [1] where we can assemble proposals for
presentations at ApacheCon 2021 (in September), select the most likely
ideas, and work through the details of getting them ready. Contributions
most welcome.

1. https://github.com/apache/royale-asjs/wiki/Royale-at-ApacheCon-2021

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: question about partial views when using Jewel

[Andrew Wetmore]

Thank you! I will pass the examples on to our questioner.

a

On Thu, Feb 25, 2021 at 4:32 PM Carlos Rovira 
wrote:

> Hi Andrew,
>
> I think this form is used multiple times in TDJ:
>
>
> https://github.com/apache/royale-asjs/blob/develop/examples/jewel/TourDeJewel/src/main/royale/components/FormExample.mxml
>
> for example here:
>
>
> https://github.com/apache/royale-asjs/blob/develop/examples/jewel/TourDeJewel/src/main/royale/FormsValidationPlayGround.mxml
>
> here:
>
>
> https://github.com/apache/royale-asjs/blob/3d020f4ddae3c38a81cc3baa351e1732c7543a62/examples/jewel/TourDeJewel/src/main/royale/MainContent.mxml#L286
>
> and here:
>
>
> https://github.com/apache/royale-asjs/blob/3d020f4ddae3c38a81cc3baa351e1732c7543a62/examples/jewel/TourDeJewel/src/main/royale/WizardPlayGround.mxml#L101
>
>
> Another could be: "ExampleHeader" in TDJ too:
>
>
> https://github.com/apache/royale-asjs/blob/develop/examples/jewel/TourDeJewel/src/main/royale/components/ExampleHeader.mxml
>
> used in all TDJ pages as a header to show different info.
>
> HTH
>
>
>
> El jue, 25 feb 2021 a las 20:23, Andrew Wetmore ()
> escribió:
>
> > So, if that is the case, it would be a matter of creating the component
> and
> > then importing it into wherever Vindra needs it? Is there a good (Jewel)
> > example of embedding a component somewhere in an app?
> >
> > Andrew
> >
> > On Thu, Feb 25, 2021 at 2:49 PM Carlos Rovira 
> > wrote:
> >
> > > Hi,
> > >
> > > sos for what I read here a "partial view" for Royale will be just a
> > > reusable mxml component, since don't think Vindra's talking about a
> > "view"
> > > referring to a concrete Jewel View or ResponsiveView, but just some
> part
> > in
> > > the application that is working on.
> > >
> > >
> > > El mié, 24 feb 2021 a las 22:04, Maria Jose Esteve ( >)
> > > escribió:
> > >
> > > > Hi, Josh is on the right track. They are a kind of "templates". And
> > > surely
> > > > Vrinda comes from the ASP.Net or Razor world.
> > > > What I do not know is if she will want a "component" or will she
> want a
> > > > fixed view that is updated according to the model that is connected
> to
> > it
> > > > ... she will tell us.
> > > >
> > > > Hiedra.
> > > >
> > > > -Mensaje original-
> > > > De: Andrew Wetmore 
> > > > Enviado el: miércoles, 24 de febrero de 2021 19:29
> > > > Para: Apache Royale Development 
> > > > Asunto: Re: question about partial views when using Jewel
> > > >
> > > > Thank you! I have invited Vrinda to join this conversation, rather
> than
> > > me
> > > > having to elbow-bend questions and answers back and forth.
> > > >
> > > > a
> > > >
> > > > On Wed, Feb 24, 2021 at 2:21 PM Josh Tynjala <
> > joshtynj...@bowlerhat.dev>
> > > > wrote:
> > > >
> > > > > When I search for "partial view" on Google, I get a lot of ASP.NET
> > > > > results.
> > > > > In that context, it seems to be a way to create a reusable view
> > > > > component in ASP.NET. So if I'm understanding correctly, in Royale
> > > > > terms, Vrinda is looking for documentation about how to create a
> new
> > > > > MXML view and how to add it as a child in other MXML views. Maybe
> I'm
> > > > > wrong, but that seems like a reasonable place to start.
> > > > >
> > > > > --
> > > > > Josh Tynjala
> > > > > Bowler Hat LLC <https://bowlerhat.dev>
> > > > >
> > > > >
> > > > > On Wed, Feb 24, 2021 at 10:14 AM Andrew Wetmore <
> andr...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > It's a mystery to me. I wonder if it has something to do with
> > > > > > viewports,
> > > > > or
> > > > > > maybe with JSON-style updating of parts of the visible screen
> > > > > > without refreshing the whole screen...I was hoping someone on the
> > > > > > PMC would recognize the term.
> > > > > >
> > > > > > a
> > > > > >
> > > > > > On Wed, Feb 24, 2021 at 11:29 AM Harbs 
> > > wrote:
> > > > > >
> > > > 

Re: question about partial views when using Jewel

[Andrew Wetmore]

So, if that is the case, it would be a matter of creating the component and
then importing it into wherever Vindra needs it? Is there a good (Jewel)
example of embedding a component somewhere in an app?

Andrew

On Thu, Feb 25, 2021 at 2:49 PM Carlos Rovira 
wrote:

> Hi,
>
> sos for what I read here a "partial view" for Royale will be just a
> reusable mxml component, since don't think Vindra's talking about a "view"
> referring to a concrete Jewel View or ResponsiveView, but just some part in
> the application that is working on.
>
>
> El mié, 24 feb 2021 a las 22:04, Maria Jose Esteve ()
> escribió:
>
> > Hi, Josh is on the right track. They are a kind of "templates". And
> surely
> > Vrinda comes from the ASP.Net or Razor world.
> > What I do not know is if she will want a "component" or will she want a
> > fixed view that is updated according to the model that is connected to it
> > ... she will tell us.
> >
> > Hiedra.
> >
> > -Mensaje original-
> > De: Andrew Wetmore 
> > Enviado el: miércoles, 24 de febrero de 2021 19:29
> > Para: Apache Royale Development 
> > Asunto: Re: question about partial views when using Jewel
> >
> > Thank you! I have invited Vrinda to join this conversation, rather than
> me
> > having to elbow-bend questions and answers back and forth.
> >
> > a
> >
> > On Wed, Feb 24, 2021 at 2:21 PM Josh Tynjala 
> > wrote:
> >
> > > When I search for "partial view" on Google, I get a lot of ASP.NET
> > > results.
> > > In that context, it seems to be a way to create a reusable view
> > > component in ASP.NET. So if I'm understanding correctly, in Royale
> > > terms, Vrinda is looking for documentation about how to create a new
> > > MXML view and how to add it as a child in other MXML views. Maybe I'm
> > > wrong, but that seems like a reasonable place to start.
> > >
> > > --
> > > Josh Tynjala
> > > Bowler Hat LLC <https://bowlerhat.dev>
> > >
> > >
> > > On Wed, Feb 24, 2021 at 10:14 AM Andrew Wetmore 
> > > wrote:
> > >
> > > > It's a mystery to me. I wonder if it has something to do with
> > > > viewports,
> > > or
> > > > maybe with JSON-style updating of parts of the visible screen
> > > > without refreshing the whole screen...I was hoping someone on the
> > > > PMC would recognize the term.
> > > >
> > > > a
> > > >
> > > > On Wed, Feb 24, 2021 at 11:29 AM Harbs 
> wrote:
> > > >
> > > > > Any idea what’s meant by “partial view”?
> > > > >
> > > > > Is the a module or something else?
> > > > >
> > > > > > On Feb 24, 2021, at 4:50 PM, Andrew Wetmore 
> > > > wrote:
> > > > > >
> > > > > > Hi, all. I received a question through my LinkedIn account from
> > > Vrinda
> > > > > > Bhat. I have asked Vrinda to join this list and this
> conversation.
> > > > > >
> > > > > > Vrinda wrote, "I'm using Apache Royale for my project and like
> > > > > > the
> > > > design
> > > > > > and working very much. Especially the Jewel part. I would like
> > > > > > to
> > > know
> > > > > > about the documentation of partial views in the official page.
> > > > > > Are
> > > > there
> > > > > > any resources where I can find about partial views in Jewel?
> > > > > > Please
> > > > help
> > > > > me
> > > > > > out."
> > > > > >
> > > > > > I would gladly provide documentation, but I am afraid I don't
> > > > > > know
> > > > what a
> > > > > > "partial view" is. Any thoughts?
> > > > > >
> > > > > > Andrwe
> > > > > >
> > > > > >
> > > > > >
> > > > > >   -
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Andrew Wetmore
> > > > > > Technical Writer-Editor
> > > > > > Infra
> > > > > > *Apache Software Foundation*
> > > > > > andr...@apache.org
> > > > >
> > > > >
> > > >
> > > > --
> > > > Andrew Wetmore
> > > > Technical Writer-Editor
> > > > Infra
> > > > *Apache Software Foundation*
> > > > andr...@apache.org
> > > >
> > >
> >
> >
> > --
> > Andrew Wetmore
> > Technical Writer-Editor
> > Infra
> > *Apache Software Foundation*
> > andr...@apache.org
> >
>
>
> --
> Carlos Rovira
> Apache Member & Apache Royale PMC
> *Apache Software Foundation*
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: question about partial views when using Jewel

[Andrew Wetmore]

Thank you! I have invited Vrinda to join this conversation, rather than me
having to elbow-bend questions and answers back and forth.

a

On Wed, Feb 24, 2021 at 2:21 PM Josh Tynjala 
wrote:

> When I search for "partial view" on Google, I get a lot of ASP.NET
> results.
> In that context, it seems to be a way to create a reusable view component
> in ASP.NET. So if I'm understanding correctly, in Royale terms, Vrinda is
> looking for documentation about how to create a new MXML view and how to
> add it as a child in other MXML views. Maybe I'm wrong, but that seems like
> a reasonable place to start.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Wed, Feb 24, 2021 at 10:14 AM Andrew Wetmore 
> wrote:
>
> > It's a mystery to me. I wonder if it has something to do with viewports,
> or
> > maybe with JSON-style updating of parts of the visible screen without
> > refreshing the whole screen...I was hoping someone on the PMC would
> > recognize the term.
> >
> > a
> >
> > On Wed, Feb 24, 2021 at 11:29 AM Harbs  wrote:
> >
> > > Any idea what’s meant by “partial view”?
> > >
> > > Is the a module or something else?
> > >
> > > > On Feb 24, 2021, at 4:50 PM, Andrew Wetmore 
> > wrote:
> > > >
> > > > Hi, all. I received a question through my LinkedIn account from
> Vrinda
> > > > Bhat. I have asked Vrinda to join this list and this conversation.
> > > >
> > > > Vrinda wrote, "I'm using Apache Royale for my project and like the
> > design
> > > > and working very much. Especially the Jewel part. I would like to
> know
> > > > about the documentation of partial views in the official page. Are
> > there
> > > > any resources where I can find about partial views in Jewel? Please
> > help
> > > me
> > > > out."
> > > >
> > > > I would gladly provide documentation, but I am afraid I don't know
> > what a
> > > > "partial view" is. Any thoughts?
> > > >
> > > > Andrwe
> > > >
> > > >
> > > >
> > > >   -
> > > >
> > > >
> > > >
> > > > --
> > > > Andrew Wetmore
> > > > Technical Writer-Editor
> > > > Infra
> > > > *Apache Software Foundation*
> > > > andr...@apache.org
> > >
> > >
> >
> > --
> > Andrew Wetmore
> > Technical Writer-Editor
> > Infra
> > *Apache Software Foundation*
> > andr...@apache.org
> >
>


-- 
Andrew Wetmore
Technical Writer-Editor
Infra
*Apache Software Foundation*
andr...@apache.org

Re: question about partial views when using Jewel

[Andrew Wetmore]

It's a mystery to me. I wonder if it has something to do with viewports, or
maybe with JSON-style updating of parts of the visible screen without
refreshing the whole screen...I was hoping someone on the PMC would
recognize the term.

a

On Wed, Feb 24, 2021 at 11:29 AM Harbs  wrote:

> Any idea what’s meant by “partial view”?
>
> Is the a module or something else?
>
> > On Feb 24, 2021, at 4:50 PM, Andrew Wetmore  wrote:
> >
> > Hi, all. I received a question through my LinkedIn account from Vrinda
> > Bhat. I have asked Vrinda to join this list and this conversation.
> >
> > Vrinda wrote, "I'm using Apache Royale for my project and like the design
> > and working very much. Especially the Jewel part. I would like to know
> > about the documentation of partial views in the official page. Are there
> > any resources where I can find about partial views in Jewel? Please help
> me
> > out."
> >
> > I would gladly provide documentation, but I am afraid I don't know what a
> > "partial view" is. Any thoughts?
> >
> > Andrwe
> >
> >
> >
> >   -
> >
> >
> >
> > --
> > Andrew Wetmore
> > Technical Writer-Editor
> > Infra
> > *Apache Software Foundation*
> > andr...@apache.org
>
>

-- 
Andrew Wetmore
Technical Writer-Editor
Infra
*Apache Software Foundation*
andr...@apache.org

question about partial views when using Jewel

[Andrew Wetmore]

Hi, all. I received a question through my LinkedIn account from Vrinda
Bhat. I have asked Vrinda to join this list and this conversation.

Vrinda wrote, "I'm using Apache Royale for my project and like the design
and working very much. Especially the Jewel part. I would like to know
about the documentation of partial views in the official page. Are there
any resources where I can find about partial views in Jewel? Please help me
out."

I would gladly provide documentation, but I am afraid I don't know what a
"partial view" is. Any thoughts?

Andrwe



   -



-- 
Andrew Wetmore
Technical Writer-Editor
Infra
*Apache Software Foundation*
andr...@apache.org

Re: youtube statistics

[Andrew Wetmore]

Looks like ApacheCon AtHome 2021 will be September 21-22-23. Gives us lots
of time to get ready!

a

On Sat, Feb 20, 2021 at 11:37 AM Carlos Rovira 
wrote:

> Hi Andrew,
>
> great to see that youtube presentations have a significant number of looks!
> Royale rocks!! :D
> (one thing I'm interested, how we can check the number of looks? can that
> be seen?)
>
> About presentations I think are good ideas and it is good to put a wiki
> page where we can add possible options and candidates as people want to
> talk about something it has "at hand" and is good and interesting for the
> rest of users. I'll need to think on my own what it could be.
>
> What it will help is to know more about the time schedule, This will be for
> ApacheCon 2021? will be around October?
>
> Thanks for putting this on the table!
>
> Carlos
>
> El sáb, 20 feb 2021 a las 16:09, Andrew Wetmore ()
> escribió:
>
> > Updated data from YouTube shows the ApacheCon 2020 videos are getting a
> lot
> > of looks.
> >
> > I have told the 2021 organizers that I will be happy to put together
> > another set of Royale presentations, if nobody else from the project
> steps
> > forward to do it. What do you think we should present on this year? Off
> the
> > top of my head, here are a couple topics that might attract viewers:
> >
> > -- Apache Royale: Your app after Flash
> > -- Apache Royale: Charts, dashboards, data display
> > -- Apache Royale: Localizing your app
> > -- Apache Royale: Building your responsive website
> > -- Apache Royale: Tips and tricks (stuff that would not make a track by
> > itself but would make people say 'Oh, that's neat' or 'Now I get how to
> do
> > that'.
> >
> > I can start another wiki page to catch ideas, if people like. However, I
> am
> > also happy to shift this to someone else, if another person wants to be
> the
> > channel coordinator.
> >
> > Andrew
> >
> > -- Forwarded message -
> > From: Elek, Marton 
> > Date: Sat, Feb 20, 2021 at 10:47 AM
> > Subject: Re: youtube statistics
> > To: 
> >
> >
> > Bumping this thread after additional two months with updated statistics
> > about the Apache Home @2020 youtube videos.
> >
> > Since my first mail the overall view count is increased from 19137 to
> > 52432. With ~300 videos it's 176 view / session in average. (I don't
> > have hopin statistics, but as far as I remember the live audience was
> > between 20-60).
> >
> > 52432 view roughly the 12% of all the view counts under the ASF youtube
> > channel (683 videos)
> >
> > Keynotes are responsible for ~25% of the views.
> >
> > The most popular videos are:
> >
> > title,viewcount,likecount
> > ApacheCon @Home 2020 Tuesday welcome message (Asia/Pacific
> > audience),4663,65
> > ApacheCon @Home 2020 Keynote: Sheng Wu - Apache grows in China,2404,23
> > Apache Superset - A data visualization platform,2362,37
> > "ApacheCon @Home 2020: Tuesday welcome address (Europe, North
> > America)",1463,16
> > Building efficient and reliable data lakes with Apache Iceberg,1282,30
> > Containerized Cassandra Cluster (CCC),1063,32
> > 5 Ways to Solve Cassandra GC Problems,1052,11
> > Apache Royale - moving a Flex app to Royale,959,35
> > ApacheCon @Home 2020: State of the Feather. David Nalley,908,6
> > Spark and Iceberg at Apple's Scale - Leveraging differential files for
> > efficient upserts and deletes,739,18
> > Achieve the event-driven Nirvana with Apache Druid,708,20
> > "Real-Time Stock Processing With Apache NiFi, Apache Flink and Apache
> > Kafka",691,8
> > ApacheCon @Home 2020 Tuesday keynote: Thomas Huang NASA/JPL,658,5
> > Apache Spark Development Lifecycle at Workday,560,2
> > "ApacheCon @Home 2020 Tuesday keynote: Sam Lightstone, IBM",551,3
> > Google Cloud Pub/Sub vs Apache Kafka for streaming solution at
> scale,546,13
> > Enabling geospatial in big data lakes and databases with LocationTech
> > GeoMesa,512,8
> > Data Streaming using Apache Flink and Apache Ignite,500,18
> > TVM: An End to End Deep Learning Compiler Stack,495,9
> > "ApacheCon @Home 2020 Tuesday Keynote - Jonathan Ellis, Datastax",448,4
> >
> > (NOTE: As Rich commented last time, some viewcounts can be wrong if the
> > video is auto-played in a playlist/channel)
> >
> >
> > And the tracks with the most views are:
> >
> > playlisttitle,viewcount,likecount,videos
> > ApacheCon @Home 2020: Keynotes,13131,142,15
> > ApacheCon @Home 20

Fwd: youtube statistics

[Andrew Wetmore]

Updated data from YouTube shows the ApacheCon 2020 videos are getting a lot
of looks.

I have told the 2021 organizers that I will be happy to put together
another set of Royale presentations, if nobody else from the project steps
forward to do it. What do you think we should present on this year? Off the
top of my head, here are a couple topics that might attract viewers:

-- Apache Royale: Your app after Flash
-- Apache Royale: Charts, dashboards, data display
-- Apache Royale: Localizing your app
-- Apache Royale: Building your responsive website
-- Apache Royale: Tips and tricks (stuff that would not make a track by
itself but would make people say 'Oh, that's neat' or 'Now I get how to do
that'.

I can start another wiki page to catch ideas, if people like. However, I am
also happy to shift this to someone else, if another person wants to be the
channel coordinator.

Andrew

-- Forwarded message -
From: Elek, Marton 
Date: Sat, Feb 20, 2021 at 10:47 AM
Subject: Re: youtube statistics
To: 


Bumping this thread after additional two months with updated statistics
about the Apache Home @2020 youtube videos.

Since my first mail the overall view count is increased from 19137 to
52432. With ~300 videos it's 176 view / session in average. (I don't
have hopin statistics, but as far as I remember the live audience was
between 20-60).

52432 view roughly the 12% of all the view counts under the ASF youtube
channel (683 videos)

Keynotes are responsible for ~25% of the views.

The most popular videos are:

title,viewcount,likecount
ApacheCon @Home 2020 Tuesday welcome message (Asia/Pacific audience),4663,65
ApacheCon @Home 2020 Keynote: Sheng Wu - Apache grows in China,2404,23
Apache Superset - A data visualization platform,2362,37
"ApacheCon @Home 2020: Tuesday welcome address (Europe, North
America)",1463,16
Building efficient and reliable data lakes with Apache Iceberg,1282,30
Containerized Cassandra Cluster (CCC),1063,32
5 Ways to Solve Cassandra GC Problems,1052,11
Apache Royale - moving a Flex app to Royale,959,35
ApacheCon @Home 2020: State of the Feather. David Nalley,908,6
Spark and Iceberg at Apple's Scale - Leveraging differential files for
efficient upserts and deletes,739,18
Achieve the event-driven Nirvana with Apache Druid,708,20
"Real-Time Stock Processing With Apache NiFi, Apache Flink and Apache
Kafka",691,8
ApacheCon @Home 2020 Tuesday keynote: Thomas Huang NASA/JPL,658,5
Apache Spark Development Lifecycle at Workday,560,2
"ApacheCon @Home 2020 Tuesday keynote: Sam Lightstone, IBM",551,3
Google Cloud Pub/Sub vs Apache Kafka for streaming solution at scale,546,13
Enabling geospatial in big data lakes and databases with LocationTech
GeoMesa,512,8
Data Streaming using Apache Flink and Apache Ignite,500,18
TVM: An End to End Deep Learning Compiler Stack,495,9
"ApacheCon @Home 2020 Tuesday Keynote - Jonathan Ellis, Datastax",448,4

(NOTE: As Rich commented last time, some viewcounts can be wrong if the
video is auto-played in a playlist/channel)


And the tracks with the most views are:

playlisttitle,viewcount,likecount,videos
ApacheCon @Home 2020: Keynotes,13131,142,15
ApacheCon @Home 2020: Cassandra,4119,99,19
ApacheCon @Home 2020: Incubator,3415,55,11
ApacheCon @Home 2020: Streaming,3408,63,15
ApacheCon @Home 2020: Big Data (Track 1),3143,69,18
ApacheCon @Home 2020: Big Data (Track 2),2281,54,17
ApacheCon @Home 2020: Royale,1983,53,5
ApacheCon @Home 2020: IoT,1917,41,10
ApacheCon @Home 2020: Camel/Integration,1892,42,14
ApacheCon @Home 2020: Geospatial,1776,24,11
ApacheCon @Home 2020: Machine Learning,1637,52,9
ApacheCon @Home 2020: Fineract,1620,34,16
ApacheCon @Home 2020: Tomcat,1334,21,13
ApacheCon @Home 2020: cTAKES,1281,13,9
ApacheCon @Home 2020: Groovy,1239,29,18



Sorting by the average views per tracks:

playlisttitle,viewcount,likecount,videos,avgview
ApacheCon @Home 2020: Keynotes,13131,142,15,875.4
ApacheCon @Home 2020: Royale,1983,53,5,396.6
ApacheCon @Home 2020: Incubator,3415,55,11,310.45454545454544
ApacheCon @Home 2020: Streaming,3408,63,15,227.2
ApacheCon @Home 2020: Cassandra,4119,99,19,216.78947368421052
ApacheCon @Home 2020: IoT,1917,41,10,191.7
ApacheCon @Home 2020: Machine Learning,1637,52,9,181.89
ApacheCon @Home 2020: Big Data (Track 1),3143,69,18,174.61
ApacheCon @Home 2020: Geospatial,1776,24,11,161.45454545454547
ApacheCon @Home 2020: cTAKES,1281,13,9,142.34
ApacheCon @Home 2020: Camel/Integration,1892,42,14,135.14285714285714
ApacheCon @Home 2020: Big Data (Track 2),2281,54,17,134.1764705882353
ApacheCon @Home 2020: Tomcat,1334,21,13,102.61538461538461
ApacheCon @Home 2020: Fineract,1620,34,16,101.25
ApacheCon @Home 2020: Groovy,1239,29,18,68.83


Hope we will have the popular tracks in 2021, again ;-)

Marton

-- 
Andrew Wetmore
Technical Writer-Editor
Infra
*Apache Software Foundation*
andr...@apache.org

Fwd: [apache/royale-asjs] Hashes required for https://downloads.apache.org/royale/compiler-build-tools/1.2.0/binaries/ (#1080)

[Andrew Wetmore]

Hi, team. Did this email get to the people it needs to get to?

a

-- Forwarded message -
From: sebbASF 
Date: Mon, Feb 15, 2021 at 9:00 PM
Subject: [apache/royale-asjs] Hashes required for
https://downloads.apache.org/royale/compiler-build-tools/1.2.0/binaries/
(#1080)
To: apache/royale-asjs 
Cc: Subscribed 


Hashes are required for all release artifacts.
Please upload them for
https://downloads.apache.org/royale/compiler-build-tools/1.2.0/binaries/

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/apache/royale-asjs/issues/1080>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC3RFXME4GHQ2ZFR7A2BI5TS7G7S5ANCNFSM4XVRW73Q>
.


-- 
Andrew Wetmore
Technical Writer-Editor
Infra
*Apache Software Foundation*
andr...@apache.org

Re: Royale nightly server down again

[Andrew Wetmore]

Infra has some Apache-dedicated AWS space available, I believe. If Royale
starts a Jira ticket aimed at INFRA, they can talk us through what is
involved.

I will ask at today's team meeting.

Andrew

On Thu, Feb 18, 2021 at 11:30 AM Carlos Rovira 
wrote:

> Hi,
>
> my motivation behind of the use of Apache machines is to be "as compliant"
> as possible with Apache, since we are an apache project. We use AWS and
> love it, but setting up another machine that is tied to one of us wouldn't
> be the same problem in the end? I mean, if we rely on apache
> infrastructure, we always can get the help of Apache infra...but if we do
> things on our own that means we depend on us to be accessible to avoid the
> rest of the project to be on a halt.
>
> That doesn't mean that we shouldn't use AWS... but just one to make a point
> so you put in the balance, and if finally you want to go that route is
> because we consider it too.
>
> thanks
>
>
>
> El jue, 18 feb 2021 a las 11:15, Harbs () escribió:
>
> > Let’s connect early next week on this?
> >
> > > On Feb 18, 2021, at 12:04 PM, Christofer Dutz <
> christofer.d...@c-ware.de>
> > wrote:
> > >
> > > I could definitely help with that.
> > >
> > > Guess I've sort of grown on Apache's infrastructure over the years.
> > >
> > > Chris
> > >
> > > -Ursprüngliche Nachricht-
> > > Von: Harbs 
> > > Gesendet: Donnerstag, 18. Februar 2021 11:03
> > > An: Apache Royale Development 
> > > Betreff: Re: Royale nightly server down again
> > >
> > > I’m not sure what would be involved in getting it working on Apache
> > hardware.
> > >
> > > I can try and setup a AWS server to replace the Azure one which will
> not
> > run out of credits.
> > >
> > > (The reason I’m suggesting AWS is because I’m more familiar with that.)
> > >
> > >> On Feb 18, 2021, at 10:16 AM, Carlos Rovira 
> > wrote:
> > >>
> > >> Hi,
> > >>
> > >> just report nightlies are on again. I think at 18th of each month
> > >> azure credits are setup on Alex's account and for this reason is on
> > again.
> > >>
> > >> El mar, 16 feb 2021 a las 20:01, Maria Jose Esteve
> > >> ()
> > >> escribió:
> > >>
> > >>> Yes, it falls out often, I had not detected it in a couple of weeks,
> > >>> but the weekend is usually inaccessible.
> > >>>
> > >>> Hiedra.
> > >>>
> > >>> -Mensaje original-
> > >>> De: Carlos Rovira  Enviado el: martes, 16
> de
> > >>> febrero de 2021 13:18
> > >>> Para: Apache Royale Development 
> > >>> Asunto: Re: Royale nightly server down again
> > >>>
> > >>> Hi folks,
> > >>>
> > >>> the nightly build server is still down. Can someone take a look?
> > >>> thanks in advance for any help you can provide
> > >>>
> > >>>
> > >>> El lun, 15 feb 2021 a las 17:43, Carlos Rovira
> > >>> ()
> > >>> escribió:
> > >>>
> > >>>> Hi,
> > >>>>
> > >>>> It seems that the server for nightly builds is down again.
> > >>>>
> > >>>>
> > >>>>
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-as
> > >>>> js
> > >>>> /lastSuccessfulBuild/artifact/out/
> > >>>>
> > >>>>
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-as
> > >>>> js _jsonly/lastSuccessfulBuild/artifact/out/
> > >>>>
> > >>>> This problem is happening from time to time and seems a bit
> > cumbersome.
> > >>>>
> > >>>> I still can't understand why we can't rely on Apache infrastructure
> > >>>> for this...since we are an Apache project, we shouldn't need to have
> > >>>> this kind of extra build server.
> > >>>>
> > >>>>
> > >>>> --
> > >>>> Carlos Rovira
> > >>>> Apache Member & Apache Royale PMC
> > >>>> *Apache Software Foundation*
> > >>>> http://about.me/carlosrovira
> > >>>>
> > >>>>
> > >>>
> > >>> --
> > >>> Carlos Rovira
> > >>> Apache Member & Apache Royale PMC
> > >>> *Apache Software Foundation*
> > >>> http://about.me/carlosrovira
> > >>>
> > >>
> > >>
> > >> --
> > >> Carlos Rovira
> > >> Apache Member & Apache Royale PMC
> > >> *Apache Software Foundation*
> > >> http://about.me/carlosrovira
> > >
> >
> >
>
> --
> Carlos Rovira
> Apache Member & Apache Royale PMC
> *Apache Software Foundation*
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Board report statistics

[Andrew Wetmore]

Hi, @Piotr Zarzycki  ! I was just about to pull
the trigger on the report. No inconvenience at all. I will leave it in your
hands now.

a

On Tue, Dec 8, 2020 at 4:11 PM Piotr Zarzycki 
wrote:

> Hi Guys,
>
> I will submit report tomorrow morning my time. Sorry for inconvenience
>
> Thanks,
> Piotr
>
> pon., 7 gru 2020 o 16:54 Carlos Rovira 
> napisał(a):
>
> > Hi Andrew,
> >
> > very good work thanks!, great report so far! :)
> >
> > El lun, 7 dic 2020 a las 13:45, Andrew Wetmore ()
> > escribió:
> >
> >> Hi:
> >>
> >> I have updated all the activity statistics in our December board report
> >> except those for our mailing lists. Somebody who is a moderator needs to
> >> provide them, or just drop them into the report here: [1]
> >>
> >> The report is due in two days. If we can't update those stats, I
> recommend
> >> we drop the section about email list activity or just say the two lists
> >> continue active.
> >>
> >> @Piotr Zarzycki  , will you be in a position
> >> to
> >> submit the report?
> >>
> >> Andrew
> >>
> >> --
> >> Andrew Wetmore
> >> Technical Writer-Editor
> >> Infra
> >> *Apache Software Foundation*
> >> andr...@apache.org
> >>
> >> [1] https://github.com/apache/royale-asjs/wiki/Board-Report-2020-12
> >>
> >
> >
> > --
> > Carlos Rovira
> > Apache Member & Apache Royale PMC
> > *Apache Software Foundation*
> > http://about.me/carlosrovira
> >
> >
>
> --
>
> Piotr Zarzycki
>


-- 
Andrew Wetmore
Technical Writer-Editor
Infra
*Apache Software Foundation*
andr...@apache.org

Board report statistics

[Andrew Wetmore]

Hi:

I have updated all the activity statistics in our December board report
except those for our mailing lists. Somebody who is a moderator needs to
provide them, or just drop them into the report here: [1]

The report is due in two days. If we can't update those stats, I recommend
we drop the section about email list activity or just say the two lists
continue active.

@Piotr Zarzycki  , will you be in a position to
submit the report?

Andrew

-- 
Andrew Wetmore
Technical Writer-Editor
Infra
*Apache Software Foundation*
andr...@apache.org

[1] https://github.com/apache/royale-asjs/wiki/Board-Report-2020-12

Lazy consensus on December board report

[Andrew Wetmore]

Hi:

The draft of the December board report, due on the 9th, is here [1]. I am
going to recommend that @piotr submit it on the 9th, so any additions or
suggestions need to come in by the 7th. I still need help updating the
social-media and mailing list statistics section. If I can't find current
values for followers, etc., I recommend removing the specifics and just
speaking in general terms about increased activity (the increase in
numbers, quarter over quarter, is not overwhelming in any case).

Andrew

-- 
Andrew Wetmore
Technical Writer-Editor
Infra
*Apache Software Foundation*
andr...@apache.org

[1] https://github.com/apache/royale-asjs/wiki/Board-Report-2020-12

Re: Statistics for board report, and review

[Andrew Wetmore]

I should have been more clear. I have not touched the statistics area at
all; it is just as I inherited it from the previous report. I agree it
could be more clear.

On Thu, Dec 3, 2020, 9:15 AM Christofer Dutz 
wrote:

> Hi Andrew,
>
> if now there are 84/83 subscribers to the lists and this is an increase of
> 79/75 in the last 3 months …
> I doubt we had only 5 subscribers for the user-list and 8 on the dev list
> … or am I reading this wrong and it 84 was an Increase of 5 compared to the
> 79 we counted 3 months ago?
>
> … ok having a look at the last report shed some light on this … perhaps we
> should rephrase that a bit to make things more clear?
>
> Chris
>
>
>
> Von: Andrew Wetmore 
> Datum: Donnerstag, 3. Dezember 2020 um 13:29
> An: Apache Royale Development , Carlos Rovira <
> carlosrov...@apache.org>
> Betreff: Statistics for board report, and review
> Hi:
>
> I have made a shot at the board report for Royale which is due next week
> [1]. Improvements and corrections are most welcome.
>
> In particular, I need someone to provide updated statistics on email list
> and social media activity. @Carlos Rovira  ,
> might
> that be you?
>
> --
> Andrew Wetmore
> Technical Writer-Editor
> Infra
> *Apache Software Foundation*
> andr...@apache.org
>
> 1. https://github.com/apache/royale-asjs/wiki/Board-Report-2020-12
>

Statistics for board report, and review

[Andrew Wetmore]

Hi:

I have made a shot at the board report for Royale which is due next week
[1]. Improvements and corrections are most welcome.

In particular, I need someone to provide updated statistics on email list
and social media activity. @Carlos Rovira  , might
that be you?

-- 
Andrew Wetmore
Technical Writer-Editor
Infra
*Apache Software Foundation*
andr...@apache.org

1. https://github.com/apache/royale-asjs/wiki/Board-Report-2020-12

Re: Release Step 003 Succeeded

[Andrew Wetmore]

aharui%40adobe.com%7C0dfee94522994db49bac08d89517682f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637423275059861693%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=RWjzL3%2BWQT%2F%2FwplDb2tRuVu9UnMYb%2BzWgBrCCU%2FAl5U%3Dreserved=0
> >>
> >>>>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmaven.apache.org%2Fxsd%2Fsettings-1.1.0.xsddata=04%7C01%7Caharui%40adobe.com%7C0dfee94522994db49bac08d89517682f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637423275059861693%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=Tqb3NTDYub92VOQ%2Bfv6l4lrNofNkg5v1300Qsabfg%2BQ%3Dreserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmaven.apache.org%2Fxsd%2Fsettings-1.1.0.xsddata=04%7C01%7Caharui%40adobe.com%7C0dfee94522994db49bac08d89517682f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637423275059861693%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=Tqb3NTDYub92VOQ%2Bfv6l4lrNofNkg5v1300Qsabfg%2BQ%3Dreserved=0>
> <
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmaven.apache.org%2Fxsd%2Fsettings-1.1.0.xsddata=04%7C01%7Caharui%40adobe.com%7C0dfee94522994db49bac08d89517682f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637423275059871688%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=lg7DQM424LoaG%2Fxs14PCC3oEc9d6LyHjMzMNQLZeZaQ%3Dreserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmaven.apache.org%2Fxsd%2Fsettings-1.1.0.xsddata=04%7C01%7Caharui%40adobe.com%7C0dfee94522994db49bac08d89517682f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637423275059871688%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=lg7DQM424LoaG%2Fxs14PCC3oEc9d6LyHjMzMNQLZeZaQ%3Dreserved=0
> >>"
> >>>> xmlns="
> >>>>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmaven.apache.org%2FSETTINGS%2F1.1.0data=04%7C01%7Caharui%40adobe.com%7C0dfee94522994db49bac08d89517682f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637423275059871688%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=luAo65ks8jSwlQBdhO%2FcyzwV6EJj3VllqhO0vpNvvls%3Dreserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmaven.apache.org%2FSETTINGS%2F1.1.0data=04%7C01%7Caharui%40adobe.com%7C0dfee94522994db49bac08d89517682f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637423275059871688%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=luAo65ks8jSwlQBdhO%2FcyzwV6EJj3VllqhO0vpNvvls%3Dreserved=0>
> <
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmaven.apache.org%2FSETTINGS%2F1.1.0data=04%7C01%7Caharui%40adobe.com%7C0dfee94522994db49bac08d89517682f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637423275059871688%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=luAo65ks8jSwlQBdhO%2FcyzwV6EJj3VllqhO0vpNvvls%3Dreserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmaven.apache.org%2FSETTINGS%2F1.1.0data=04%7C01%7Caharui%40adobe.com%7C0dfee94522994db49bac08d89517682f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637423275059871688%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=luAo65ks8jSwlQBdhO%2FcyzwV6EJj3VllqhO0vpNvvls%3Dreserved=0
> >>
> >>>> "
> >>>>>>>>xmlns:xsi="
> >>>>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2F2001%2FXMLSchema-instancedata=04%7C01%7Caharui%40adobe.com%7C0dfee94522994db49bac08d89517682f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637423275059871688%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=JNROzst8YhChfx1uKgDjwtzkTkLyOzp2KQxi5835LSM%3Dreserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2F2001%2FXMLSchema-instancedata=04%7C01%7Caharui%40adobe.com%7C0dfee94522994db49bac08d89517682f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637423275059871688%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=JNROzst8YhChfx1uKgDjwtzkTkLyOzp2KQxi5835LSM%3Dreserved=0>
> <
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2F2001%2FXMLSchema-instancedata=04%7C01%7Caharui%40adobe.com%7C0dfee94522994db49bac08d89517682f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637423275059871688%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=JNROzst8YhChfx1uKgDjwtzkTkLyOzp2KQxi5835LSM%3Dreserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2F2001%2FXMLSchema-instancedata=04%7C01%7Caharui%40adobe.com%7C0dfee94522994db49bac08d89517682f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637423275059871688%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=JNROzst8YhChfx1uKgDjwtzkTkLyOzp2KQxi5835LSM%3Dreserved=0
> >>
> >>>> ">
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> apache.releases.https
> >>>>>>>> {your apache user id}
> >>>>>>>> {your apache user password}
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>>
> >>>>>>>> (Be sure to replace the placeholders with your actual apache
> >>>> committer id and your Apache password)
> >>>>>>>>
> >>>>>>>> If you already have a settings.xml, just be sure the "server"
> block
> >>>> containing your credentials is added to a servers block in that file.
> >>>>>>>>
> >>>>>>>> Do not "Close" the staging repository until the other repos have
> been
> >>>> added.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >>> --
> >>>
> >>> Piotr Zarzycki
>
>

-- 
Andrew Wetmore
Technical Writer-Editor
Infra
*Apache Software Foundation*
andr...@apache.org

Re: Compiler options for reducing release build size of Royale projects

[Andrew Wetmore]

Do the Falcon compiler options apply if one is not using Falcon? Or are we
ALWAYS using Falcon now?

a

On Tue, Nov 24, 2020 at 10:36 AM Carlos Rovira 
wrote:

> Hi,
>
> here's a list of Falcon compiler options that could be added to [1].
> I think an initial copy-paste could be enough for a "first pass", although
> I guess the older options should come from other sources like the one from
> Andrew's links or this other one [2]:
>
> [1]
>
> https://cwiki.apache.org/confluence/display/FLEX/Getting+Started+with+the+Falcon+and+FalconJX+Compilers
> [2] http://renaun.com/blog/2006/08/list-of-mxmlccompc-arguments/
>
>
>
> El lun, 23 nov 2020 a las 23:23, Andrew Wetmore ()
> escribió:
>
> > There are quite a few options. Maybe the most likely ones should be on
> the
> > page you were editing, and we can add the other to a sub page.
> >
> > a
> >
> > On Mon, Nov 23, 2020 at 6:19 PM Andrew Wetmore 
> > wrote:
> >
> > > @Josh Tynjala  did you check this page [1]?
> > If
> > > not, I can scrape from it.
> > >
> > > a
> > >
> > > 1. http://www.docsultant.com/site2/articles/flex_cmd.html
> > >
> > > On Mon, Nov 23, 2020 at 6:14 PM Andrew Wetmore 
> > > wrote:
> > >
> > >> I guess I better jump on that before it all melts away. I probably
> have
> > >> some in some crackly downloads from a decade ago, unless I used them
> to
> > >> feed a fire.
> > >>
> > >> Great work, Josh!
> > >>
> > >> a
> > >>
> > >> On Mon, Nov 23, 2020 at 6:07 PM Josh Tynjala <
> joshtynj...@bowlerhat.dev
> > >
> > >> wrote:
> > >>
> > >>> I've added all of the new export-* and prevent-rename-* options,
> > >>> including
> > >>> descriptions. I also added several more options that I saw were
> > missing.
> > >>>
> > >>> Eventually, someone needs to fill in this page with *all* of the
> > missing
> > >>> options. Especially the core options that already existed during the
> > Flex
> > >>> days. Adobe has pulled down most of its Flex documentation now, and
> I'm
> > >>> not
> > >>> sure that the Apache version of Flex ever had them fully documented
> > >>> either.
> > >>> Soon, there may be no documentation for these options anywhere on the
> > >>> web,
> > >>> even for someone persistent and knowledgeable enough to look for
> legacy
> > >>> content.
> > >>>
> > >>> Most of the missing options may be found in this compiler class
> > >>> (descriptions of each option are usually in jsdoc comments):
> > >>>
> > >>>
> >
> https://github.com/apache/royale-compiler/blob/develop/compiler-common/src/main/java/org/apache/royale/compiler/config/Configuration.java
> > >>>
> > >>> There are likely some more JS-specific options that are not
> documented
> > >>> yet
> > >>> in these compiler classes too:
> > >>>
> > >>>
> >
> https://github.com/apache/royale-compiler/blob/develop/compiler-jx/src/main/java/org/apache/royale/compiler/clients/JSConfiguration.java
> > >>>
> > >>>
> >
> https://github.com/apache/royale-compiler/blob/develop/compiler-jx/src/main/java/org/apache/royale/compiler/internal/driver/js/goog/JSGoogConfiguration.java
> > >>>
> > >>> --
> > >>> Josh Tynjala
> > >>> Bowler Hat LLC <https://bowlerhat.dev>
> > >>>
> > >>>
> > >>> On Fri, Nov 20, 2020 at 1:08 PM Josh Tynjala <
> > joshtynj...@bowlerhat.dev>
> > >>> wrote:
> > >>>
> > >>> > I'll try to fill in the details soon.
> > >>> >
> > >>> > --
> > >>> > Josh Tynjala
> > >>> > Bowler Hat LLC <https://bowlerhat.dev>
> > >>> >
> > >>> >
> > >>> > On Fri, Nov 20, 2020 at 11:42 AM Andrew Wetmore <
> cottag...@gmail.com
> > >
> > >>> > wrote:
> > >>> >
> > >>> >> I have added a section that includes the four compiler options
> that
> > >>> Carlos
> > >>> >> mentioned. If there are more that, when used, reduce output size,
> > they
> > >>> >> should go there.

Re: Compiler options for reducing release build size of Royale projects

[Andrew Wetmore]

There are quite a few options. Maybe the most likely ones should be on the
page you were editing, and we can add the other to a sub page.

a

On Mon, Nov 23, 2020 at 6:19 PM Andrew Wetmore  wrote:

> @Josh Tynjala  did you check this page [1]? If
> not, I can scrape from it.
>
> a
>
> 1. http://www.docsultant.com/site2/articles/flex_cmd.html
>
> On Mon, Nov 23, 2020 at 6:14 PM Andrew Wetmore 
> wrote:
>
>> I guess I better jump on that before it all melts away. I probably have
>> some in some crackly downloads from a decade ago, unless I used them to
>> feed a fire.
>>
>> Great work, Josh!
>>
>> a
>>
>> On Mon, Nov 23, 2020 at 6:07 PM Josh Tynjala 
>> wrote:
>>
>>> I've added all of the new export-* and prevent-rename-* options,
>>> including
>>> descriptions. I also added several more options that I saw were missing.
>>>
>>> Eventually, someone needs to fill in this page with *all* of the missing
>>> options. Especially the core options that already existed during the Flex
>>> days. Adobe has pulled down most of its Flex documentation now, and I'm
>>> not
>>> sure that the Apache version of Flex ever had them fully documented
>>> either.
>>> Soon, there may be no documentation for these options anywhere on the
>>> web,
>>> even for someone persistent and knowledgeable enough to look for legacy
>>> content.
>>>
>>> Most of the missing options may be found in this compiler class
>>> (descriptions of each option are usually in jsdoc comments):
>>>
>>> https://github.com/apache/royale-compiler/blob/develop/compiler-common/src/main/java/org/apache/royale/compiler/config/Configuration.java
>>>
>>> There are likely some more JS-specific options that are not documented
>>> yet
>>> in these compiler classes too:
>>>
>>> https://github.com/apache/royale-compiler/blob/develop/compiler-jx/src/main/java/org/apache/royale/compiler/clients/JSConfiguration.java
>>>
>>> https://github.com/apache/royale-compiler/blob/develop/compiler-jx/src/main/java/org/apache/royale/compiler/internal/driver/js/goog/JSGoogConfiguration.java
>>>
>>> --
>>> Josh Tynjala
>>> Bowler Hat LLC <https://bowlerhat.dev>
>>>
>>>
>>> On Fri, Nov 20, 2020 at 1:08 PM Josh Tynjala 
>>> wrote:
>>>
>>> > I'll try to fill in the details soon.
>>> >
>>> > --
>>> > Josh Tynjala
>>> > Bowler Hat LLC <https://bowlerhat.dev>
>>> >
>>> >
>>> > On Fri, Nov 20, 2020 at 11:42 AM Andrew Wetmore 
>>> > wrote:
>>> >
>>> >> I have added a section that includes the four compiler options that
>>> Carlos
>>> >> mentioned. If there are more that, when used, reduce output size, they
>>> >> should go there. I have not populated the descriptions, as a smart
>>> person
>>> >> should do that.
>>> >>
>>> >> a
>>> >>
>>> >> On Fri, Nov 20, 2020 at 3:23 PM Andrew Wetmore 
>>> >> wrote:
>>> >>
>>> >> > Yes, that page is a good location. Should we start a subsection for
>>> >> these
>>> >> > options which have the benefit of reducing output size?
>>> >> >
>>> >> > a
>>> >> >
>>> >> > On Fri, Nov 20, 2020 at 1:48 PM Carlos Rovira <
>>> carlosrov...@apache.org>
>>> >> > wrote:
>>> >> >
>>> >> >> Hi Josh,
>>> >> >>
>>> >> >> thanks for working on this. I finally could get here after weeks of
>>> >> hard
>>> >> >> work in other things with almost not time.
>>> >> >> I tried in Tour de Jewel with:
>>> >> >>
>>> >> >> -export-public-symbols=false
>>> >> >> -prevent-rename-protected-symbols=false
>>> >> >> -prevent-rename-internal-symbols=false
>>> >> >> -prevent-rename-public-static-methods=false
>>> >> >> -prevent-rename-public-instance-methods=false
>>> >> >>
>>> >> >> (for what I read that's the set it can be used without breaking
>>> app)
>>> >> >>
>>> >> >> and a downsize from 1045kb to 910kb so amazing! :)
>>> >> >>
>>> >> >> I'll 

Re: Compiler options for reducing release build size of Royale projects

[Andrew Wetmore]

@Josh Tynjala  did you check this page [1]? If
not, I can scrape from it.

a

1. http://www.docsultant.com/site2/articles/flex_cmd.html

On Mon, Nov 23, 2020 at 6:14 PM Andrew Wetmore  wrote:

> I guess I better jump on that before it all melts away. I probably have
> some in some crackly downloads from a decade ago, unless I used them to
> feed a fire.
>
> Great work, Josh!
>
> a
>
> On Mon, Nov 23, 2020 at 6:07 PM Josh Tynjala 
> wrote:
>
>> I've added all of the new export-* and prevent-rename-* options, including
>> descriptions. I also added several more options that I saw were missing.
>>
>> Eventually, someone needs to fill in this page with *all* of the missing
>> options. Especially the core options that already existed during the Flex
>> days. Adobe has pulled down most of its Flex documentation now, and I'm
>> not
>> sure that the Apache version of Flex ever had them fully documented
>> either.
>> Soon, there may be no documentation for these options anywhere on the web,
>> even for someone persistent and knowledgeable enough to look for legacy
>> content.
>>
>> Most of the missing options may be found in this compiler class
>> (descriptions of each option are usually in jsdoc comments):
>>
>> https://github.com/apache/royale-compiler/blob/develop/compiler-common/src/main/java/org/apache/royale/compiler/config/Configuration.java
>>
>> There are likely some more JS-specific options that are not documented yet
>> in these compiler classes too:
>>
>> https://github.com/apache/royale-compiler/blob/develop/compiler-jx/src/main/java/org/apache/royale/compiler/clients/JSConfiguration.java
>>
>> https://github.com/apache/royale-compiler/blob/develop/compiler-jx/src/main/java/org/apache/royale/compiler/internal/driver/js/goog/JSGoogConfiguration.java
>>
>> --
>> Josh Tynjala
>> Bowler Hat LLC <https://bowlerhat.dev>
>>
>>
>> On Fri, Nov 20, 2020 at 1:08 PM Josh Tynjala 
>> wrote:
>>
>> > I'll try to fill in the details soon.
>> >
>> > --
>> > Josh Tynjala
>> > Bowler Hat LLC <https://bowlerhat.dev>
>> >
>> >
>> > On Fri, Nov 20, 2020 at 11:42 AM Andrew Wetmore 
>> > wrote:
>> >
>> >> I have added a section that includes the four compiler options that
>> Carlos
>> >> mentioned. If there are more that, when used, reduce output size, they
>> >> should go there. I have not populated the descriptions, as a smart
>> person
>> >> should do that.
>> >>
>> >> a
>> >>
>> >> On Fri, Nov 20, 2020 at 3:23 PM Andrew Wetmore 
>> >> wrote:
>> >>
>> >> > Yes, that page is a good location. Should we start a subsection for
>> >> these
>> >> > options which have the benefit of reducing output size?
>> >> >
>> >> > a
>> >> >
>> >> > On Fri, Nov 20, 2020 at 1:48 PM Carlos Rovira <
>> carlosrov...@apache.org>
>> >> > wrote:
>> >> >
>> >> >> Hi Josh,
>> >> >>
>> >> >> thanks for working on this. I finally could get here after weeks of
>> >> hard
>> >> >> work in other things with almost not time.
>> >> >> I tried in Tour de Jewel with:
>> >> >>
>> >> >> -export-public-symbols=false
>> >> >> -prevent-rename-protected-symbols=false
>> >> >> -prevent-rename-internal-symbols=false
>> >> >> -prevent-rename-public-static-methods=false
>> >> >> -prevent-rename-public-instance-methods=false
>> >> >>
>> >> >> (for what I read that's the set it can be used without breaking app)
>> >> >>
>> >> >> and a downsize from 1045kb to 910kb so amazing! :)
>> >> >>
>> >> >> I'll try to add to TodoMVC as well and see what happens ;)
>> >> >>
>> >> >> @Andrew I think you and Josh can add this doc to the Royale Docs
>> >> compiler
>> >> >> options page here [1]
>> >> >>
>> >> >> [1] https://apache.github.io/royale-docs/compiler/compiler-options
>> >> >>
>> >> >>
>> >> >>
>> >> >> El mar, 10 nov 2020 a las 23:36, Josh Tynjala (<
>> >> joshtynj...@bowlerhat.dev
>> >> >> >)
>> >> >> escribió:
>>

Re: Compiler options for reducing release build size of Royale projects

[Andrew Wetmore]

I guess I better jump on that before it all melts away. I probably have
some in some crackly downloads from a decade ago, unless I used them to
feed a fire.

Great work, Josh!

a

On Mon, Nov 23, 2020 at 6:07 PM Josh Tynjala 
wrote:

> I've added all of the new export-* and prevent-rename-* options, including
> descriptions. I also added several more options that I saw were missing.
>
> Eventually, someone needs to fill in this page with *all* of the missing
> options. Especially the core options that already existed during the Flex
> days. Adobe has pulled down most of its Flex documentation now, and I'm not
> sure that the Apache version of Flex ever had them fully documented either.
> Soon, there may be no documentation for these options anywhere on the web,
> even for someone persistent and knowledgeable enough to look for legacy
> content.
>
> Most of the missing options may be found in this compiler class
> (descriptions of each option are usually in jsdoc comments):
>
> https://github.com/apache/royale-compiler/blob/develop/compiler-common/src/main/java/org/apache/royale/compiler/config/Configuration.java
>
> There are likely some more JS-specific options that are not documented yet
> in these compiler classes too:
>
> https://github.com/apache/royale-compiler/blob/develop/compiler-jx/src/main/java/org/apache/royale/compiler/clients/JSConfiguration.java
>
> https://github.com/apache/royale-compiler/blob/develop/compiler-jx/src/main/java/org/apache/royale/compiler/internal/driver/js/goog/JSGoogConfiguration.java
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Fri, Nov 20, 2020 at 1:08 PM Josh Tynjala 
> wrote:
>
> > I'll try to fill in the details soon.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
> >
> > On Fri, Nov 20, 2020 at 11:42 AM Andrew Wetmore 
> > wrote:
> >
> >> I have added a section that includes the four compiler options that
> Carlos
> >> mentioned. If there are more that, when used, reduce output size, they
> >> should go there. I have not populated the descriptions, as a smart
> person
> >> should do that.
> >>
> >> a
> >>
> >> On Fri, Nov 20, 2020 at 3:23 PM Andrew Wetmore 
> >> wrote:
> >>
> >> > Yes, that page is a good location. Should we start a subsection for
> >> these
> >> > options which have the benefit of reducing output size?
> >> >
> >> > a
> >> >
> >> > On Fri, Nov 20, 2020 at 1:48 PM Carlos Rovira <
> carlosrov...@apache.org>
> >> > wrote:
> >> >
> >> >> Hi Josh,
> >> >>
> >> >> thanks for working on this. I finally could get here after weeks of
> >> hard
> >> >> work in other things with almost not time.
> >> >> I tried in Tour de Jewel with:
> >> >>
> >> >> -export-public-symbols=false
> >> >> -prevent-rename-protected-symbols=false
> >> >> -prevent-rename-internal-symbols=false
> >> >> -prevent-rename-public-static-methods=false
> >> >> -prevent-rename-public-instance-methods=false
> >> >>
> >> >> (for what I read that's the set it can be used without breaking app)
> >> >>
> >> >> and a downsize from 1045kb to 910kb so amazing! :)
> >> >>
> >> >> I'll try to add to TodoMVC as well and see what happens ;)
> >> >>
> >> >> @Andrew I think you and Josh can add this doc to the Royale Docs
> >> compiler
> >> >> options page here [1]
> >> >>
> >> >> [1] https://apache.github.io/royale-docs/compiler/compiler-options
> >> >>
> >> >>
> >> >>
> >> >> El mar, 10 nov 2020 a las 23:36, Josh Tynjala (<
> >> joshtynj...@bowlerhat.dev
> >> >> >)
> >> >> escribió:
> >> >>
> >> >> > Hi Andrew,
> >> >> >
> >> >> > Yes, I can help with that!
> >> >> >
> >> >> > --
> >> >> > Josh Tynjala
> >> >> > Bowler Hat LLC <https://bowlerhat.dev>
> >> >> >
> >> >> >
> >> >> > On Mon, Nov 9, 2020 at 3:22 PM Andrew Wetmore  >
> >> >> wrote:
> >> >> >
> >> >> > > Josh, this is very interesting. I would like to include an
> >> actionable
> >> >> > > a

Re: Compiler options for reducing release build size of Royale projects

[Andrew Wetmore]

I have added a section that includes the four compiler options that Carlos
mentioned. If there are more that, when used, reduce output size, they
should go there. I have not populated the descriptions, as a smart person
should do that.

a

On Fri, Nov 20, 2020 at 3:23 PM Andrew Wetmore  wrote:

> Yes, that page is a good location. Should we start a subsection for these
> options which have the benefit of reducing output size?
>
> a
>
> On Fri, Nov 20, 2020 at 1:48 PM Carlos Rovira 
> wrote:
>
>> Hi Josh,
>>
>> thanks for working on this. I finally could get here after weeks of hard
>> work in other things with almost not time.
>> I tried in Tour de Jewel with:
>>
>> -export-public-symbols=false
>> -prevent-rename-protected-symbols=false
>> -prevent-rename-internal-symbols=false
>> -prevent-rename-public-static-methods=false
>> -prevent-rename-public-instance-methods=false
>>
>> (for what I read that's the set it can be used without breaking app)
>>
>> and a downsize from 1045kb to 910kb so amazing! :)
>>
>> I'll try to add to TodoMVC as well and see what happens ;)
>>
>> @Andrew I think you and Josh can add this doc to the Royale Docs compiler
>> options page here [1]
>>
>> [1] https://apache.github.io/royale-docs/compiler/compiler-options
>>
>>
>>
>> El mar, 10 nov 2020 a las 23:36, Josh Tynjala (> >)
>> escribió:
>>
>> > Hi Andrew,
>> >
>> > Yes, I can help with that!
>> >
>> > --
>> > Josh Tynjala
>> > Bowler Hat LLC <https://bowlerhat.dev>
>> >
>> >
>> > On Mon, Nov 9, 2020 at 3:22 PM Andrew Wetmore 
>> wrote:
>> >
>> > > Josh, this is very interesting. I would like to include an actionable
>> > > amount of this information in our user documentation. If I create a
>> page
>> > in
>> > > the help docs for it, can you help me populate instructions based on
>> your
>> > > researchs?
>> > >
>> > > Thanks!
>> > >
>> > > Andrew
>> > >
>> > > On Mon, Nov 9, 2020 at 6:16 PM Josh Tynjala <
>> joshtynj...@bowlerhat.dev>
>> > > wrote:
>> > >
>> > > > Hi all,
>> > > >
>> > > > Some of you have probably been wondering about my changes to the
>> > compiler
>> > > > over the last year or more. I apologize again for occasionally
>> breaking
>> > > > things for short periods. It's been quite a challenge getting this
>> > stuff
>> > > > working, but I'm excited to finally be able to report some real
>> > > > improvements that pretty much anyone should be able to take
>> advantage
>> > of
>> > > > when building a Royale app.
>> > > >
>> > > > First some background. A while back, Harbs asked me to look into
>> ways
>> > of
>> > > > reducing the file size of release builds. As you may know, we use
>> > > Google's
>> > > > Closure compiler to optimize our generated JavaScript. Closure can
>> be
>> > > very
>> > > > aggressive in its optimizations, by renaming symbols (things like
>> > > variable
>> > > > and function names) and removing "dead code" that is detected as
>> never
>> > > > being called.
>> > > >
>> > > > Closure's optimizations are good, but they also require developers
>> to
>> > be
>> > > > very careful about how they write their JavaScript code. When you
>> > enable
>> > > > Closure's full optimizations, you are not allowed to use certain
>> > > JavaScript
>> > > > features because Closure cannot analyze them properly. For instance,
>> > > > consider the following code:
>> > > >
>> > > > var propName= "myProp";
>> > > > var value = obj[propName];
>> > > >
>> > > > When you dynamically access a property with a string, Closure cannot
>> > > > reliably know that the property exists and will be accessed at
>> runtime.
>> > > It
>> > > > may decide to rename or remove that property, which would break
>> things
>> > at
>> > > > runtime.
>> > > >
>> > > > ActionScript supports many of the same restricted dynamic features
>> too,
>> > > so
>> > > &g

Re: Compiler options for reducing release build size of Royale projects

[Andrew Wetmore]

Yes, that page is a good location. Should we start a subsection for these
options which have the benefit of reducing output size?

a

On Fri, Nov 20, 2020 at 1:48 PM Carlos Rovira 
wrote:

> Hi Josh,
>
> thanks for working on this. I finally could get here after weeks of hard
> work in other things with almost not time.
> I tried in Tour de Jewel with:
>
> -export-public-symbols=false
> -prevent-rename-protected-symbols=false
> -prevent-rename-internal-symbols=false
> -prevent-rename-public-static-methods=false
> -prevent-rename-public-instance-methods=false
>
> (for what I read that's the set it can be used without breaking app)
>
> and a downsize from 1045kb to 910kb so amazing! :)
>
> I'll try to add to TodoMVC as well and see what happens ;)
>
> @Andrew I think you and Josh can add this doc to the Royale Docs compiler
> options page here [1]
>
> [1] https://apache.github.io/royale-docs/compiler/compiler-options
>
>
>
> El mar, 10 nov 2020 a las 23:36, Josh Tynjala ( >)
> escribió:
>
> > Hi Andrew,
> >
> > Yes, I can help with that!
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
> >
> > On Mon, Nov 9, 2020 at 3:22 PM Andrew Wetmore 
> wrote:
> >
> > > Josh, this is very interesting. I would like to include an actionable
> > > amount of this information in our user documentation. If I create a
> page
> > in
> > > the help docs for it, can you help me populate instructions based on
> your
> > > researchs?
> > >
> > > Thanks!
> > >
> > > Andrew
> > >
> > > On Mon, Nov 9, 2020 at 6:16 PM Josh Tynjala  >
> > > wrote:
> > >
> > > > Hi all,
> > > >
> > > > Some of you have probably been wondering about my changes to the
> > compiler
> > > > over the last year or more. I apologize again for occasionally
> breaking
> > > > things for short periods. It's been quite a challenge getting this
> > stuff
> > > > working, but I'm excited to finally be able to report some real
> > > > improvements that pretty much anyone should be able to take advantage
> > of
> > > > when building a Royale app.
> > > >
> > > > First some background. A while back, Harbs asked me to look into ways
> > of
> > > > reducing the file size of release builds. As you may know, we use
> > > Google's
> > > > Closure compiler to optimize our generated JavaScript. Closure can be
> > > very
> > > > aggressive in its optimizations, by renaming symbols (things like
> > > variable
> > > > and function names) and removing "dead code" that is detected as
> never
> > > > being called.
> > > >
> > > > Closure's optimizations are good, but they also require developers to
> > be
> > > > very careful about how they write their JavaScript code. When you
> > enable
> > > > Closure's full optimizations, you are not allowed to use certain
> > > JavaScript
> > > > features because Closure cannot analyze them properly. For instance,
> > > > consider the following code:
> > > >
> > > > var propName= "myProp";
> > > > var value = obj[propName];
> > > >
> > > > When you dynamically access a property with a string, Closure cannot
> > > > reliably know that the property exists and will be accessed at
> runtime.
> > > It
> > > > may decide to rename or remove that property, which would break
> things
> > at
> > > > runtime.
> > > >
> > > > ActionScript supports many of the same restricted dynamic features
> too,
> > > so
> > > > if you want to support the entire AS3 language, we can't let Closure
> do
> > > its
> > > > full optimization. Luckily, Closure also provides a bit of a
> backdoor:
> > it
> > > > allows you to "export" symbols, which means that they won't be
> renamed
> > > and
> > > > they won't be removed as dead code. Traditionally, we have made heavy
> > use
> > > > of this exporting feature in Royale.
> > > >
> > > > Harbs wanted to know if we absolutely needed to export everything
> that
> > we
> > > > currently export, and if we could potentially allow developers to
> turn
> > > off
> > > > exporting entirely, as long as they follow the stricter rules
> required
> > b

Re: about releasing 0.9.8

[Andrew Wetmore]

Is there a list of new features and fixes since 0.9.7? I would like to see
if i can at least get good documentation in place about those changes.

a

On Mon, Nov 16, 2020 at 1:23 PM Harbs  wrote:

> OK. I’ll start tomorrow.
>
> (fingers crossed)
>
> > On Nov 16, 2020, at 5:55 PM, Carlos Rovira 
> wrote:
> >
> > Hi,
> >
> > I think the time zone problems Chris warned are now behind us, and want
> to
> > open this thread about releasing 0.9.8. Many months have passed and I
> think
> > we need to push a new release soon, I think before the end of the year
> will
> > be the best for us if possible.
> >
> > What do you think? Harbs can we count on you to do the task?
> >
> > Thanks in advance
> >
> > --
> > Carlos Rovira
> > Apache Member & Apache Royale PMC
> > *Apache Software Foundation*
> > http://about.me/carlosrovira
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Compiler options for reducing release build size of Royale projects

[Andrew Wetmore]

d see even more file size savings in release builds if
> Closure works with full optimizations for all symbols. Obviously,
> ActionScript developers would be required to strictly follow Closure's
> rules, if they opt into renaming of public symbols, but that's a choice
> that they should be allowed to make.
>
> As I mentioned above, our implementation of MXML and binding uses dynamic
> access, which is not compatible with Closure's full optimizations. To
> support those optimizations, I will need to explore changes to how we
> generate JS for MXML, and how it gets parsed at runtime.
>
> We previously discussed this subject a bit in this older thread from
> January 2020:
>
>
> https://lists.apache.org/thread.html/r843e55252e37967b71b1430a2a904719791d698f3e5e2a79de74e493%40%3Cdev.royale.apache.org%3E
>
> At the time, I tried out some ideas that we came up with while
> brainstorming, but all had various downsides that didn't make for an
> obvious winner. In the end, I decided to set further investigation aside
> and first focus on exporting/renaming stuff. Now, I'm ready to take a
> second look with a fresh perspective, and maybe we'll have some new ideas
> to try.
>
> -
>
> That was really long, so thank you for reading, if you made it to the end!
>
> TL;DR: By enabling certain, new compiler options, most Royale developers
> can make their app release builds smaller. Additionally, I plan to keep
> investigating, and I expect to find more ways to reduce file size in the
> future.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: How to stop Jenkins job

[Andrew Wetmore]

They are beginning to think that something is wrong with the build node.
They have disconnected that node, as you can see from the update to the
ticket, and want to see what happens the next time the build runs.

a

On Sun, Oct 25, 2020 at 3:19 PM Andrew Wetmore  wrote:

> I was just reading them. I think the team probably has everything they
> need.
>
> On Sun, Oct 25, 2020 at 2:52 PM Piotr Zarzycki 
> wrote:
>
>> Well I think we have expressed that in comments of that jira
>>
>> niedz., 25 paź 2020 o 18:33 Andrew Wetmore 
>> napisał(a):
>>
>> > Are all those details in the ticket?
>> >
>> > On Sun, Oct 25, 2020, 2:27 PM Piotr Zarzycki > >
>> > wrote:
>> >
>> > > It's not only about stopping current build - that's one thing. The
>> most
>> > > important thing is why it is happening. It's stuck at the very
>> beginning
>> > -
>> > > when maven is going to checkout Royale repository. It can be seen in
>> > logs.
>> > >
>> > > niedz., 25 paź 2020 o 18:23 Andrew Wetmore 
>> > > napisał(a):
>> > >
>> > > > I will check with Chris Lambertus, who is assigned to this ticket.
>> > > >
>> > > > On Sun, Oct 25, 2020 at 1:56 PM Piotr Zarzycki <
>> > > piotrzarzyck...@gmail.com>
>> > > > wrote:
>> > > >
>> > > > > Jira is being raised some time ago:
>> > > > > https://issues.apache.org/jira/browse/INFRA-21002
>> > > > >
>> > > > > niedz., 25 paź 2020 o 17:42 Andrew Wetmore 
>> > > > > napisał(a):
>> > > > >
>> > > > > > A Jira ticket is very useful because it is harder to forget
>> about
>> > > than
>> > > > an
>> > > > > > email or a Slack comment.
>> > > > > >
>> > > > > > On Sun, Oct 25, 2020 at 11:33 AM Carlos Rovira <
>> > > > carlosrov...@apache.org>
>> > > > > > wrote:
>> > > > > >
>> > > > > > > Hi,
>> > > > > > >
>> > > > > > > Greg and I contact infra through slack asg channel
>> (#asfinfra).
>> > > There
>> > > > > > Gavin
>> > > > > > > MacDonald was of great support. But that was the latest time
>> the
>> > > > build
>> > > > > > got
>> > > > > > > stuck and they needed to restart the server to fix it. I think
>> > they
>> > > > > were
>> > > > > > > looking to the server to see what could be happening. Piotr,
>> it
>> > > would
>> > > > > be
>> > > > > > > good that you post in that channel asking for help (or as
>> Andrew
>> > > says
>> > > > > > > through the other ways he posted before) to avoid Greg and I
>> > report
>> > > > > again
>> > > > > > > so they see others here are noticing the problem and make
>> them to
>> > > > take
>> > > > > > > another look at it if they are busy or forgot to try to fix
>> it.
>> > > > > > >
>> > > > > > > Thanks
>> > > > > > >
>> > > > > > > El dom., 25 oct. 2020 a las 13:05, Andrew Wetmore (<
>> > > > andr...@apache.org
>> > > > > >)
>> > > > > > > escribió:
>> > > > > > >
>> > > > > > > > Anyone can ask Infra about a thing like this. Email
>> > > users@infra.a.o
>> > > > > > with
>> > > > > > > > the full details of what's happening, or start a Jira
>> ticket.
>> > > > > > > >
>> > > > > > > > Andrew
>> > > > > > > >
>> > > > > > > > On Sun, Oct 25, 2020 at 8:42 AM Piotr Zarzycki <
>> > > > > > > piotrzarzyck...@gmail.com>
>> > > > > > > > wrote:
>> > > > > > > >
>> > > > > > > > > Hi Guys,
>> > > > > > > > >
>> > > > > > > > > Our build doesn't work at all. It under stuck for the past
>> > > days.
>> > > > > > Anyone
>> > > > &

Re: How to stop Jenkins job

[Andrew Wetmore]

I was just reading them. I think the team probably has everything they need.

On Sun, Oct 25, 2020 at 2:52 PM Piotr Zarzycki 
wrote:

> Well I think we have expressed that in comments of that jira
>
> niedz., 25 paź 2020 o 18:33 Andrew Wetmore 
> napisał(a):
>
> > Are all those details in the ticket?
> >
> > On Sun, Oct 25, 2020, 2:27 PM Piotr Zarzycki 
> > wrote:
> >
> > > It's not only about stopping current build - that's one thing. The most
> > > important thing is why it is happening. It's stuck at the very
> beginning
> > -
> > > when maven is going to checkout Royale repository. It can be seen in
> > logs.
> > >
> > > niedz., 25 paź 2020 o 18:23 Andrew Wetmore 
> > > napisał(a):
> > >
> > > > I will check with Chris Lambertus, who is assigned to this ticket.
> > > >
> > > > On Sun, Oct 25, 2020 at 1:56 PM Piotr Zarzycki <
> > > piotrzarzyck...@gmail.com>
> > > > wrote:
> > > >
> > > > > Jira is being raised some time ago:
> > > > > https://issues.apache.org/jira/browse/INFRA-21002
> > > > >
> > > > > niedz., 25 paź 2020 o 17:42 Andrew Wetmore 
> > > > > napisał(a):
> > > > >
> > > > > > A Jira ticket is very useful because it is harder to forget about
> > > than
> > > > an
> > > > > > email or a Slack comment.
> > > > > >
> > > > > > On Sun, Oct 25, 2020 at 11:33 AM Carlos Rovira <
> > > > carlosrov...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > Greg and I contact infra through slack asg channel (#asfinfra).
> > > There
> > > > > > Gavin
> > > > > > > MacDonald was of great support. But that was the latest time
> the
> > > > build
> > > > > > got
> > > > > > > stuck and they needed to restart the server to fix it. I think
> > they
> > > > > were
> > > > > > > looking to the server to see what could be happening. Piotr, it
> > > would
> > > > > be
> > > > > > > good that you post in that channel asking for help (or as
> Andrew
> > > says
> > > > > > > through the other ways he posted before) to avoid Greg and I
> > report
> > > > > again
> > > > > > > so they see others here are noticing the problem and make them
> to
> > > > take
> > > > > > > another look at it if they are busy or forgot to try to fix it.
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > > El dom., 25 oct. 2020 a las 13:05, Andrew Wetmore (<
> > > > andr...@apache.org
> > > > > >)
> > > > > > > escribió:
> > > > > > >
> > > > > > > > Anyone can ask Infra about a thing like this. Email
> > > users@infra.a.o
> > > > > > with
> > > > > > > > the full details of what's happening, or start a Jira ticket.
> > > > > > > >
> > > > > > > > Andrew
> > > > > > > >
> > > > > > > > On Sun, Oct 25, 2020 at 8:42 AM Piotr Zarzycki <
> > > > > > > piotrzarzyck...@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hi Guys,
> > > > > > > > >
> > > > > > > > > Our build doesn't work at all. It under stuck for the past
> > > days.
> > > > > > Anyone
> > > > > > > > > know whether they are working on it or have any idea ?
> There
> > is
> > > > no
> > > > > > > answer
> > > > > > > > > in jira - I bet Chris have channel to ask infra about some
> > > > details
> > > > > ?
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > Piotr
> > > > > > > > >
> > > > > > > > > pon., 19 paź 2020 o 22:46 Piotr Zarzycki <
> > > > > piotrzarzyck...@gmail.com>
> > > > > > > > > napisał(a):
> &