carlosrovira commented on issue #1: Font is not loaded when accessed over https
URL: https://github.com/apache/royale-website/issues/1#issuecomment-357503357
Hi, I fixed HTTP/HTTPS problems. I had to install a certificate in WP
instance for HTTPS and export /upload the changes to the
carlosrovira closed issue #1: Font is not loaded when accessed over https
URL: https://github.com/apache/royale-website/issues/1
This is an automated message from the Apache Git Service.
To respond to the message, please log
bigosmallm commented on issue #1: Font is not loaded when accessed over https
URL: https://github.com/apache/royale-website/issues/1#issuecomment-357405275
@neminovno As a workaround, you can use the url: http://royale.apache.org/
for now
neminovno opened a new issue #1: Font is not loaded when accessed over https
URL: https://github.com/apache/royale-website/issues/1
Font is not loaded if open https://royale.apache.org/
carlosrovira commented on issue #1: Font is not loaded when accessed over https
URL: https://github.com/apache/royale-website/issues/1#issuecomment-357420943
Thanks @neminovno and @bigosmallm, I'll see how to solve it
This is
carlosrovira commented on issue #1: Font is not loaded when accessed over https
URL: https://github.com/apache/royale-website/issues/1#issuecomment-357420924
Thanks @neminovno, and @bigosmallm, I check this and see how to solve it
2018-01-13 4:06 GMT+01:00 bigosmallm
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.
This is an
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,
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 to
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.
To respond
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
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
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 to
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 to
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
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
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 to
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 a
Harbs commented on issue #11: fix top menu url and some css
URL: https://github.com/apache/royale-docs/pull/11#issuecomment-414736623
Thanks for this. It looks like a nice improvement.
The links should probably all simply be domain-relative links instead of
hard-coded absolute links
yestaro commented on issue #11: fix top menu url and some css
URL: https://github.com/apache/royale-docs/pull/11#issuecomment-414871177
Yes, relative links are better than absolute links.
But main site's domain is royale.apache.org that is different from doc
site's domain -
Harbs commented on issue #11: fix top menu url and some css
URL: https://github.com/apache/royale-docs/pull/11#issuecomment-414928248
No. I merged the PR because it's an improvement. The relative links can
always be added later.
Thanks!
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
carlosrovira commented on issue #11: fix top menu url and some css
URL: https://github.com/apache/royale-docs/pull/11#issuecomment-414951894
I think to get relative links in docs, we should have cloacking url to make
"apache.github.io" be "royale.apache.org", don't know if this is possible
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 the
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 to
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
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
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
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.
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
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
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 the
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
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 to the
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 the
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.
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
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
Aszusz commented on issue #16: Improve Build Instructions
URL: https://github.com/apache/royale-docs/pull/16#issuecomment-491951905
@aharui @carlosrovira Excuse me guys, but I've just checked out develop and
it seems like it's 1 year old. It doesn't even contain the section I modified.
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
carlosrovira commented on issue #16: Improve Build Instructions
URL: https://github.com/apache/royale-docs/pull/16#issuecomment-492393739
Hi Guys, getting to this now, was very busy this days with other things,
seem I don't have to do nothing for now. Let me know in case I'm wrong. Thanks!
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
carlosrovira commented on issue #16: Improve Build Instructions
URL: https://github.com/apache/royale-docs/pull/16#issuecomment-491879930
Thanks for your contribution @Aszusz! You're welcome to continue improving
it! Thanks :)
Aszusz commented on issue #16: Improve Build Instructions
URL: https://github.com/apache/royale-docs/pull/16#issuecomment-491902170
@aharui Thank you, next PRs will be against develop
This is an automated message from the
Aszusz commented on issue #16: Improve Build Instructions
URL: https://github.com/apache/royale-docs/pull/16#issuecomment-491900040
Thank you :) New improvements coming soon!
This is an automated message from the Apache Git
aharui commented on issue #16: Improve Build Instructions
URL: https://github.com/apache/royale-docs/pull/16#issuecomment-491900107
Yes, thank you @Aszusz, however these changes should go against the develop
branch, not master. @carlosrovira can you move that commit?
piotrzarzycki21 commented on issue #16: Improve Build Instructions
URL: https://github.com/apache/royale-docs/pull/16#issuecomment-491904696
@aharui can we make cherry pick from master to develop and revert on master?
This is
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
aharui commented on issue #16: Improve Build Instructions
URL: https://github.com/apache/royale-docs/pull/16#issuecomment-491910251
I don't know the best way.
This is an automated message from the Apache Git Service.
To
joshtynjala commented on issue #16: Improve Build Instructions
URL: https://github.com/apache/royale-docs/pull/16#issuecomment-492008858
When I made some contributions to royale-docs a week or two ago, I also
committed to master because that seemed to have more recent commits than
piotrzarzycki21 commented on issue #16: Improve Build Instructions
URL: https://github.com/apache/royale-docs/pull/16#issuecomment-492126369
@Aszusz let's continue improvements towards master - if anyone would like to
change something - we can start discussion on dev.
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 on to
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
Aszusz commented on issue #23: Remove empty link from page content and toc menu
URL: https://github.com/apache/royale-docs/pull/23#issuecomment-494930324
Hi Carlos, thanks for merging. On my way to solve it.
On Wed, May 22, 2019 at 8:58 PM Carlos Rovira
wrote:
> Hi Adrian,
carlosrovira commented on issue #23: Remove empty link from page content and
toc menu
URL: https://github.com/apache/royale-docs/pull/23#issuecomment-494924331
Hi Adrian, seems that after merging you latest PR this one has conflicts,
can you solve it?
thanks
Aszusz commented on issue #23: Remove empty link from page content and toc menu
URL: https://github.com/apache/royale-docs/pull/23#issuecomment-494939479
Resolved
This is an automated message from the Apache Git Service.
To
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 to the
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
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
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
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 on
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
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
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
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 the
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.
This is an
cristallium opened a new issue #4: Nightly Build links are broken on actual
website
URL: https://github.com/apache/royale-website/issues/4
Hi
Nightly Build links are broken on actual website (both JS Only and JS + SWf)
cristallium opened a new issue #5: Broken link in
using-external-javascript-libraries-in-apache-royale article
URL: https://github.com/apache/royale-website/issues/5
Hi
On article using-external-javascript-libraries-in-apache-royale :
carlosrovira closed issue #4: Nightly Build links are broken on actual website
URL: https://github.com/apache/royale-website/issues/4
This is an automated message from the Apache Git Service.
To respond to the message,
carlosrovira commented on issue #4: Nightly Build links are broken on actual
website
URL: https://github.com/apache/royale-website/issues/4#issuecomment-544908336
HI Fred,
URL has changed and now are:
carlosrovira closed issue #5: Broken link in
using-external-javascript-libraries-in-apache-royale article
URL: https://github.com/apache/royale-website/issues/5
This is an automated message from the Apache Git Service.
To
carlosrovira commented on issue #5: Broken link in
using-external-javascript-libraries-in-apache-royale article
URL: https://github.com/apache/royale-website/issues/5#issuecomment-544904674
Thanks Fred,
The right link now is:
carlosrovira commented on issue #4: Nightly Build links are broken on actual
website
URL: https://github.com/apache/royale-website/issues/4#issuecomment-544909016
one more thing, is that due to some Apache rules, nightly builds section in
download page will be moved to "get involved" page
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
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 to
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 to
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
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 to
luc4smoreira opened a new issue #6:
URL: https://github.com/apache/royale-website/issues/6
URL : https://apache.github.io/royale-docs/get-started/hello-world
The instruction to compile the source file HelloWorld.mxml is wrong.
It should be:
`mxmlc src/HelloWorld.mxml `
luc4smoreira opened a new issue #7:
URL: https://github.com/apache/royale-website/issues/7
Newbies (like me) will access apache Flex website and they will think it is
dead. It is necessary to inform with a big banner, on the front page that
Apache Flex was changed to Apache Royale.
carlosrovira commented on issue #7:
URL: https://github.com/apache/royale-website/issues/7#issuecomment-663379862
Hi Lucas, Apache Flex is not dead, it continues to work and people use it
with AIR. But you're right, I think we should put some banner there.
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 to
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 to
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:
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
changelog.
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
releases.
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
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
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
89 matches
Mail list logo
