-remove-circulars

Hi Folks, I've spent the last day or so trying to get ASDoc to run when minified. I created a JSON to ValueObjects utility which helped a lot. It still isn't completely running, but it appears that we need to stop pruning classes that are only used in type annotations. This will make most apps

To-do list from Wiki

Hi: There is a to-do list from the Wiki [1] which lists a number of Flex features that may not yet be available in Royale. Could someone review the list and confirm whether all the entries are yet-to-be-ported? Also, what is the status of the wiki vis-a-vis the help docs? Do we maintain it or

Re: Page linked to from license page no longer exists

I'll look into it. Thanks, Om On Feb 16, 2018 8:35 AM, "Alex Harui" wrote: > Bummer. Looks like WikiPedia decided to remove it. I think Om > contributed that, so I guess we should let him decide whether to find > another source for the data or remove the example. >

Re: How to install Nightly build through NPM

You can just do npm install -g That should install the nightly for you. Thanks, Om On Feb 16, 2018 5:49 AM, "Piotr Zarzycki" wrote: > Hi Guys, > > Is it possible to install Nightly build of Royale through NPM ? I need to > check some scenario with Moonshine on Mac

Re: Website help doc links not working

Thanks! I think I am caught up with the existing link issues, and have added some more material. I will keep QA in mind a little better at least as we head toward each new release and each possible bump of new website visitors. There is lots more material to add, and I have some questions in

Re: Website help doc links not working

Hi Andrew, I don't think I changed any file names. You can always rummage through the commit log to find out, but maybe not worth the time. I'm not planning to be in royale-docs over the next couple of days so feel free to rename lots of things to the pattern you wanted. -Alex On 2/16/18,

[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 to

[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

Re: How I can use multiple CSS files

Hi Alex, if as you said all pieces are in place, maybe I'm doing something wrong, since I don't get it to work. Can you check the current example in "feature/vivid" branch? *First build "Vivid" project (in projects folder)*. Here only look to "TextField" component. This component uses

Page linked to from license page no longer exists

Hi: on Welcome/licenses.md there is this passage: The map coordinates in examples/native/USStatesMap/src/MapCoords.as were placed into the Public Domain by its author. See: https://en.wikipedia.org/wiki/File:USA_CIA_Map.svg#file When I click that link I get a message that the file has been

[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 to

[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

Re: Website help doc links not working

The first issues we hit are on the index.md page. I did not write this page or create the links there, so perhaps they were created before the file names reached their current form. I will do a link sweep. On Fri, Feb 16, 2018 at 6:07 AM, Andrew Wetmore wrote: > That's

Re: Website help doc links not working

That's interesting, as I carefully matched the links to the file names when I created the links. Did the file names get changed at some point? On Fri, Feb 16, 2018 at 4:20 AM, Alex Harui wrote: > Thanks Berty, > > Andrew, the link has to reference the correct file

Re: Website help doc links not working

Thanks Berty, Andrew, the link has to reference the correct file name. For "Features and Concepts", the file is currently named "Features And Concepts" (note capital "A" in "And") For "A Bit of History", I only see a file called history.md For "Licenses and Policies", I only see a file called