[GitHub] [royale-website] dependabot[bot] opened a new pull request, #13: Bump socket.io-parser from 4.2.1 to 4.2.3

dependabot[bot] opened a new pull request, #13: URL: https://github.com/apache/royale-website/pull/13 Bumps [socket.io-parser](https://github.com/socketio/socket.io-parser) from 4.2.1 to 4.2.3. Release notes Sourced from https://github.com/socketio/socket.io-parser/releases

[GitHub] [royale-website] dependabot[bot] closed pull request #9: Bump engine.io from 6.2.0 to 6.2.1

dependabot[bot] closed pull request #9: Bump engine.io from 6.2.0 to 6.2.1 URL: https://github.com/apache/royale-website/pull/9 -- 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

[GitHub] [royale-website] dependabot[bot] opened a new pull request, #12: Bump engine.io and socket.io

dependabot[bot] opened a new pull request, #12: URL: https://github.com/apache/royale-website/pull/12 Bumps [engine.io](https://github.com/socketio/engine.io) and [socket.io](https://github.com/socketio/socket.io). These dependencies needed to be updated together. Updates `engine.io

[GitHub] [royale-website] dependabot[bot] commented on pull request #9: Bump engine.io from 6.2.0 to 6.2.1

dependabot[bot] commented on PR #9: URL: https://github.com/apache/royale-website/pull/9#issuecomment-1533929993 Superseded by #12. -- 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

[GitHub] [royale-website] dependabot[bot] opened a new pull request, #11: Bump nunjucks from 3.2.3 to 3.2.4

dependabot[bot] opened a new pull request, #11: URL: https://github.com/apache/royale-website/pull/11 Bumps [nunjucks](https://github.com/mozilla/nunjucks) from 3.2.3 to 3.2.4. Release notes Sourced from https://github.com/mozilla/nunjucks/releases;>nunjucks's relea

[GitHub] [royale-website] dependabot[bot] opened a new pull request, #10: Bump luxon from 2.5.0 to 2.5.2

dependabot[bot] opened a new pull request, #10: URL: https://github.com/apache/royale-website/pull/10 Bumps [luxon](https://github.com/moment/luxon) from 2.5.0 to 2.5.2. Changelog Sourced from https://github.com/moment/luxon/blob/master/CHANGELOG.md;>luxon's change

[GitHub] [royale-website] dependabot[bot] commented on pull request #8: Bump socket.io-parser from 4.0.4 to 4.0.5

dependabot[bot] commented on PR #8: URL: https://github.com/apache/royale-website/pull/8#issuecomment-1329464859 Looks like socket.io-parser is up-to-date now, so this is no longer needed. -- This is an automated message from the Apache Git Service. To respond to the message, please log

[GitHub] [royale-website] dependabot[bot] closed pull request #8: Bump socket.io-parser from 4.0.4 to 4.0.5

dependabot[bot] closed pull request #8: Bump socket.io-parser from 4.0.4 to 4.0.5 URL: https://github.com/apache/royale-website/pull/8 -- 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

[GitHub] [royale-website] dependabot[bot] opened a new pull request, #9: Bump engine.io from 6.2.0 to 6.2.1

dependabot[bot] opened a new pull request, #9: URL: https://github.com/apache/royale-website/pull/9 Bumps [engine.io](https://github.com/socketio/engine.io) from 6.2.0 to 6.2.1. Release notes Sourced from https://github.com/socketio/engine.io/releases;>engine.io's relea

[GitHub] [royale-website] dependabot[bot] opened a new pull request, #8: Bump socket.io-parser from 4.0.4 to 4.0.5

dependabot[bot] opened a new pull request, #8: URL: https://github.com/apache/royale-website/pull/8 Bumps [socket.io-parser](https://github.com/socketio/socket.io-parser) from 4.0.4 to 4.0.5. Release notes Sourced from https://github.com/socketio/socket.io-parser/releases

Re: [GitHub] [royale-asjs] yishayw commented on pull request #1147: Jewel: Cancel spinner auto increment/decrement when mousing away from buttons

I have no idea why that error was happening, but I cleaned up the file. It should not have been using removeAllListeners either way. > On Oct 11, 2022, at 10:38 AM, GitBox wrote: > > > yishayw commented on PR #1147: > URL:

[GitHub] [royale-docs] Harbs merged pull request #28: Create LICENSE

Harbs merged pull request #28: URL: https://github.com/apache/royale-docs/pull/28 -- 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

[GitHub] [royale-docs] carlosrovira merged pull request #27: fix the relative path, should not be start with /

carlosrovira merged pull request #27: URL: https://github.com/apache/royale-docs/pull/27 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

[GitHub] [royale-docs] yestaro opened a new pull request #27: fix the relative path, should not be start with /

yestaro opened a new pull request #27: URL: https://github.com/apache/royale-docs/pull/27 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

[GitHub] [royale-docs] carlosrovira commented on pull request #26: remove duplicated 'the'

carlosrovira commented on pull request #26: URL: https://github.com/apache/royale-docs/pull/26#issuecomment-680863211 Thanks yestaro, hope to see you again around here :) This is an automated message from the Apache Git

[GitHub] [royale-docs] carlosrovira merged pull request #26: remove duplicated 'the'

carlosrovira merged pull request #26: URL: https://github.com/apache/royale-docs/pull/26 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

[GitHub] [royale-docs] yestaro opened a new pull request #26: remove duplicated 'the'

yestaro opened a new pull request #26: URL: https://github.com/apache/royale-docs/pull/26 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

[GitHub] [royale-docs] yishayw merged pull request #25: Update hello-world.md

yishayw merged pull request #25: URL: https://github.com/apache/royale-docs/pull/25 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

[GitHub] [royale-docs] LogapriyanL opened a new pull request #25: Update hello-world.md

LogapriyanL opened a new pull request #25: URL: https://github.com/apache/royale-docs/pull/25 Corrected few Typo This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[GitHub] [royale-docs] cottage14 merged pull request #24: Cottage14 patch 2

cottage14 merged pull request #24: Cottage14 patch 2 URL: https://github.com/apache/royale-docs/pull/24 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

[GitHub] [royale-docs] cottage14 opened a new pull request #24: Cottage14 patch 2

cottage14 opened a new pull request #24: Cottage14 patch 2 URL: https://github.com/apache/royale-docs/pull/24 Added general material about why we need to test our code, and a teaser about hints and tips to come

Re: Suggestion to request Royale addition to Facebook's 'flash migration recommendations'

, but I am unlikely to get there before sometime next month. For now, I do think it's appropriate to request inclusion on the page as a 'flash to html5' migration technology. Hopefully Carlos's request will result in someone at FB looking into that. Beyond that, in terms of 'migrating' something s

Re: Suggestion to request Royale addition to Facebook's 'flash migration recommendations'

ider to include it?" El mar., 18 jun. 2019 a las 3:34, Greg Dove () escribió: > fyi I got a ping today from Facebook today about flash migrations to html5. > > If anyone knows how to contact them internally to request that they update > their options, this

Re: Suggestion to request Royale addition to Facebook's 'flash migration recommendations'

a las 3:34, Greg Dove () escribió: > fyi I got a ping today from Facebook today about flash migrations to html5. > > If anyone knows how to contact them internally to request that they update > their options, this page [1] could do with a Royale mention, I believe. In > case you're wonder

Suggestion to request Royale addition to Facebook's 'flash migration recommendations'

fyi I got a ping today from Facebook today about flash migrations to html5. If anyone knows how to contact them internally to request that they update their options, this page [1] could do with a Royale mention, I believe. In case you're wondering, yes, I know of cases where Flex was used

[GitHub] [royale-docs] piotrzarzycki21 merged pull request #23: Remove empty link from page content and toc menu

piotrzarzycki21 merged pull request #23: Remove empty link from page content and toc menu URL: https://github.com/apache/royale-docs/pull/23 This is an automated message from the Apache Git Service. To respond

[GitHub] [royale-docs] carlosrovira merged pull request #22: Add missing links to menu

carlosrovira merged pull request #22: Add missing links to menu URL: https://github.com/apache/royale-docs/pull/22 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[GitHub] [royale-docs] Aszusz opened a new pull request #23: Remove empty link from page content and toc menu

Aszusz opened a new pull request #23: Remove empty link from page content and toc menu URL: https://github.com/apache/royale-docs/pull/23 This fix removes completely page What Royale and You Can Do (because it's empty now). If you want to keep this page anyway, close this pull request

[GitHub] [royale-docs] Aszusz opened a new pull request #22: Add missing links to menu

Aszusz opened a new pull request #22: Add missing links to menu URL: https://github.com/apache/royale-docs/pull/22 This fix adds four links from Welcome to Apache Royale page to ToC menu: - What Royale and You Can Do (*which is empty, but maybe you want to reenable it. If not I'm

[GitHub] [royale-docs] carlosrovira merged pull request #21: Improve toc menu expanding behavior

carlosrovira merged pull request #21: Improve toc menu expanding behavior URL: https://github.com/apache/royale-docs/pull/21 This is an automated message from the Apache Git Service. To respond to the message, please log

[GitHub] [royale-docs] Aszusz opened a new pull request #21: Improve toc menu expanding behavior

Aszusz opened a new pull request #21: Improve toc menu expanding behavior URL: https://github.com/apache/royale-docs/pull/21 This feature improves ToC menu expanding behavior. It makes the menu always expend the current item if it has any children. This allows the user to see where he/she

[GitHub] [royale-docs] piotrzarzycki21 merged pull request #19: Make the logo clickable

piotrzarzycki21 merged pull request #19: Make the logo clickable URL: https://github.com/apache/royale-docs/pull/19 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[GitHub] [royale-docs] piotrzarzycki21 merged pull request #20: Further improve build instructions

piotrzarzycki21 merged pull request #20: Further improve build instructions URL: https://github.com/apache/royale-docs/pull/20 This is an automated message from the Apache Git Service. To respond to the message, please log

[GitHub] [royale-docs] Aszusz opened a new pull request #20: Further improve build instructions

Aszusz opened a new pull request #20: Further improve build instructions URL: https://github.com/apache/royale-docs/pull/20 Let me correct the instructions I provided last time. This method uses a built-in Jekyll server and doesn't require manipulating the baseurl parameter

[GitHub] [royale-docs] Aszusz opened a new pull request #19: Make the logo clickable

Aszusz opened a new pull request #19: Make the logo clickable URL: https://github.com/apache/royale-docs/pull/19 This feature makes the Royale logo in docs clickable. It points to Royale main page. This is an automated

[GitHub] [royale-docs] piotrzarzycki21 merged pull request #17: Move Getting Started to Docs

piotrzarzycki21 merged pull request #17: Move Getting Started to Docs URL: https://github.com/apache/royale-docs/pull/17 This is an automated message from the Apache Git Service. To respond to the message, please log

[GitHub] [royale-docs] Aszusz closed pull request #18: Fix instruction of how to set up baseurl in local_config

Aszusz closed pull request #18: Fix instruction of how to set up baseurl in local_config URL: https://github.com/apache/royale-docs/pull/18 This is an automated message from the Apache Git Service. To respond to the message

[GitHub] [royale-docs] Aszusz opened a new pull request #18: Fix instruction of how to set up baseurl in local_config

Aszusz opened a new pull request #18: Fix instruction of how to set up baseurl in local_config URL: https://github.com/apache/royale-docs/pull/18 Let me correct my instructions on how to properly set up baseurl parameter for working locally with docs

[GitHub] [royale-docs] Aszusz opened a new pull request #17: Move Getting Started to Docs

Aszusz opened a new pull request #17: Move Getting Started to Docs URL: https://github.com/apache/royale-docs/pull/17 This feature takes one page of online documentation hosted outside docs: Getting Started (https://royale.apache.org/getting-started/) and merges it with docs: Get

[GitHub] [royale-docs] carlosrovira merged pull request #16: Improve Build Instructions

carlosrovira merged pull request #16: Improve Build Instructions URL: https://github.com/apache/royale-docs/pull/16 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[GitHub] [royale-docs] Aszusz opened a new pull request #16: Improve Build Instructions

Aszusz opened a new pull request #16: Improve Build Instructions URL: https://github.com/apache/royale-docs/pull/16 This feature improves build instructions in README.md. New instructions: - are more detailed - show how to override default _config with local_config. It allows the user

[GitHub] cottage14 closed pull request #15: Cottage14 patch 2

cottage14 closed pull request #15: Cottage14 patch 2 URL: https://github.com/apache/royale-docs/pull/15 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use

[GitHub] cottage14 opened a new pull request #15: Cottage14 patch 2

cottage14 opened a new pull request #15: Cottage14 patch 2 URL: https://github.com/apache/royale-docs/pull/15 updating the file This is an automated message from the Apache Git Service. To respond to the message, please log

[GitHub] cottage14 closed pull request #14: Update PAYG.md

cottage14 closed pull request #14: Update PAYG.md URL: https://github.com/apache/royale-docs/pull/14 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a fork

[GitHub] cottage14 opened a new pull request #13: Cottage14 patch 1

cottage14 opened a new pull request #13: Cottage14 patch 1 URL: https://github.com/apache/royale-docs/pull/13 Updating page on strands and beads This is an automated message from the Apache Git Service. To respond

[GitHub] cottage14 closed pull request #13: Cottage14 patch 1

cottage14 closed pull request #13: Cottage14 patch 1 URL: https://github.com/apache/royale-docs/pull/13 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use

[GitHub] cottage14 closed pull request #12: External interface documentation

cottage14 closed pull request #12: External interface documentation URL: https://github.com/apache/royale-docs/pull/12 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull

[GitHub] hcsuk opened a new pull request #12: External interface documentation

hcsuk opened a new pull request #12: External interface documentation URL: https://github.com/apache/royale-docs/pull/12 Adding some documentation about how to call external javascript via an ExternalInterface style API

FW: Request for Participation in University of Cincinnati - Open Source Survey

FYI for anyone who likes taking surveys. On 10/16/18, 11:24 AM, "Sharan Foga" wrote: Hi Everyone Please see below for a message from some researchers from the University of Cincinnati who are running a survey on participation in Open Source. The survey is open to all Apache

RE: [royale-asjs] 01/01: Merge pull request #309 from pashminakazi/branch21

Sorry I will be more careful while merging a Pull Request. -Alina -Original Message- From: Alex Harui [mailto:aha...@adobe.com.INVALID] Sent: Wednesday, October 03, 2018 12:49 PM To: dev@royale.apache.org; comm...@royale.apache.org Subject: Re: [royale-asjs] 01/01: Merge pull request

Re: [royale-asjs] 01/01: Merge pull request #309 from pashminakazi/branch21

reserved=0 commit 057caff98e725dce3a5d3a59cd6bb4918f95af2c Merge: a62cd11 822cfb5 Author: alinakazi AuthorDate: Wed Oct 3 10:28:00 2018 +0500 Merge pull request #309 from pashminakazi/branch21 Changes on 10.oct.2018 .../src/main/royale/mx/

[GitHub] Harbs closed pull request #11: fix top menu url and some css

Harbs closed pull request #11: fix top menu url and some css URL: https://github.com/apache/royale-docs/pull/11 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request

[GitHub] yestaro opened a new pull request #11: fix top menu url and some css

yestaro opened a new pull request #11: fix top menu url and some css URL: https://github.com/apache/royale-docs/pull/11 fix top menu and footer link and css to follow royale main website This is an automated message from

[GitHub] Harbs closed pull request #10: fix typo thir to theri

Harbs closed pull request #10: fix typo thir to theri URL: https://github.com/apache/royale-docs/pull/10 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from

Request info about JSONLY build

Hi, I'd like to deal with JSONLY build since seems is not building in the same way the normal build. If someone can let me know some steps to follow, I'll try to configure what I need localy and pass scripts for building localy and see why is failing. Some info in some wiki to look at? I think

Re: Request

Hi Raj, Do you mean by that you want to subscribe that list? Thanks, Piotr On Sun, Apr 29, 2018, 8:15 AM Raj Raju wrote: > Please add me to the group. > > Thanks, > Raju M. >

Request

Please add me to the group. Thanks, Raju M.

Re: IntelliJ IDEA official support request

Ok! Let's see what happen now. 2018-04-04 16:54 GMT+02:00 Carlos Rovira : > Piotr, I don't see a way to change the old ticket...If I could change topic > and content to update to new names, I think it would be more interesting > due to voting and history. If not is of no

Re: IntelliJ IDEA official support request

Piotr, I don't see a way to change the old ticket...If I could change topic and content to update to new names, I think it would be more interesting due to voting and history. If not is of no interest since that ticket is very cold now due to many months has passed 2018-04-04 15:54 GMT+02:00

Re: IntelliJ IDEA official support request

I just loose hope in case Intellij and doubt that new ticket change anything. The previous one was relevant. Several people has voted for it. You could change the title in the previous ticket. Discussion in the comments was important etc. Let's see what happened now. 2018-04-04 15:47 GMT+02:00

Re: IntelliJ IDEA official support request

I'm sorry I wanted to respond only to the Dev. That ticket is already in place for a long time. They asked us several months ago for some statistics and explained some confusion related to the support. [1] I doubt that we enough relevant to ask them for the support right now. Maybe in the future.

IntelliJ IDEA official support request

Hi, just filled the following ticket to ask JetBrains to add official support for Apache Royale https://youtrack.jetbrains.com/issue/IDEA-189525 Please, vote and share to make it relevant for this IDE thanks -- Carlos Rovira http://about.me/carlosrovira

[GitHub] cottage14 opened a new pull request #9: Develop

cottage14 opened a new pull request #9: Develop URL: https://github.com/apache/royale-docs/pull/9 Updating several help-docs pages. This is an automated message from the Apache Git Service. To respond to the message, please

[GitHub] cottage14 closed pull request #8: Develop

cottage14 closed pull request #8: Develop URL: https://github.com/apache/royale-docs/pull/8 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above

[GitHub] cottage14 opened a new pull request #8: Develop

cottage14 opened a new pull request #8: Develop URL: https://github.com/apache/royale-docs/pull/8 Fixing links This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use

[GitHub] cottage14 closed pull request #7: Develop

cottage14 closed pull request #7: Develop URL: https://github.com/apache/royale-docs/pull/7 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above

[GitHub] cottage14 opened a new pull request #7: Develop

cottage14 opened a new pull request #7: Develop URL: https://github.com/apache/royale-docs/pull/7 Fixing links. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use

[GitHub] cottage14 closed pull request #6: Develop

cottage14 closed pull request #6: Develop URL: https://github.com/apache/royale-docs/pull/6 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above

[GitHub] cottage14 opened a new pull request #6: Develop

cottage14 opened a new pull request #6: Develop URL: https://github.com/apache/royale-docs/pull/6 Fixing some text issues and added a page about Royale CLI This is an automated message from the Apache Git Service. To respond

[GitHub] cottage14 closed pull request #5: Develop

cottage14 closed pull request #5: Develop URL: https://github.com/apache/royale-docs/pull/5 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above

[GitHub] cottage14 opened a new pull request #5: Develop

cottage14 opened a new pull request #5: Develop URL: https://github.com/apache/royale-docs/pull/5 Made some edits to the files in the "Get Started" package. This is an automated message from the Apache Git Service.

[GitHub] cottage14 opened a new pull request #4: added a note about documentation being incomplete.

cottage14 opened a new pull request #4: added a note about documentation being incomplete. URL: https://github.com/apache/royale-docs/pull/4 Added a short note, and merging to master to make sure that I can

[GitHub] cottage14 closed pull request #4: added a note about documentation being incomplete.

cottage14 closed pull request #4: added a note about documentation being incomplete. URL: https://github.com/apache/royale-docs/pull/4 This is an automated message from the Apache Git Service. To respond to the message

[GitHub] cottage14 closed pull request #1: Added an entry to the doc ToC

cottage14 closed pull request #1: Added an entry to the doc ToC URL: https://github.com/apache/royale-docs/pull/1 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request

[GitHub] cottage14 closed pull request #2: Provided writing guidelines

cottage14 closed pull request #2: Provided writing guidelines URL: https://github.com/apache/royale-docs/pull/2 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request

[GitHub] cottage14 closed pull request #3: Merging new, added file into develop branch

cottage14 closed pull request #3: Merging new, added file into develop branch URL: https://github.com/apache/royale-docs/pull/3 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign

[GitHub] cottage14 opened a new pull request #3: Merging new, added file into develop branch

cottage14 opened a new pull request #3: Merging new, added file into develop branch URL: https://github.com/apache/royale-docs/pull/3 Test of merging. This is an automated message from the Apache Git Service. To respond