Re: Website description

Hi Om, google now reflects right search values for "Apache Royale", so the fix is now in place :) 2018-02-06 17:31 GMT+01:00 OmPrakash Muppirala : > On Feb 5, 2018 11:39 PM, "Justin Mclean" wrote: > > Hi, > > Or if you want to use slack for

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

This should be fixed in the nightly builds. This is the last thing I wanted to get done before cutting this release. When I start my day tomorrow I will start the process. I would also like to push royale-docs to master so it gets published with this release. I think it is good enough (or will

Re: Royale substitutes for Flex features

I wouldn't link to ASDoc, but if we have a reverse-search feature, explain in the main docs how to use it. I think your suggestions for royale-docs is fine. The advantage of having it all in ASDoc is the committer working on the component doesn't have to go to another repo to document it, but

Re: Royale substitutes for Flex features

We have created a placeholder in the documentation for migrating an existing project from Flex to Royale. That is where I would look for such help. Would you suggest that we add links from there to the ASDoc? That seems a little awkward to me. For me, holding an existing Flex application, it

Re: Royale substitutes for Flex features

I don't think we have a list. Some components are just missing (no Menu/MenuBar). Some components are missing things (locked rows/columns, virtual renderers). I don't really know how to manage such a list. The Spark Button has over 100 public APIs. Tracking all of that would be daunting.

Re: JSON Objects renaming (was Re: ASDoc, Routing, Releases)

Pretty sure something like this was done for Flash Builder. You could direct FB to generate ValueObjects from a WSDL. I'm imagining an AIR app that lets you specify a path to an output folder and a class name and lets you paste a JSON result. If you look at the ASDoc structure for

Re: JSON Objects renaming (was Re: ASDoc, Routing, Releases)

The java Jackson parser supports metadata based specification that can tell the deserializer to use a custom parser for specific sub properties. https://fasterxml.github.io/jackson-annotations/javadoc/2.0.0/com/fasterxml/jackson/annotation/JsonSetter.html This site has a pretty good rundown on

Royale substitutes for Flex features

Do we have a list of Flex features not (yet) available in Royale, and known ways of getting to the desired result using Royale? Recent conversations regarding Alina's product migration make me think that would be a useful feature in the help documentation. a -- Andrew Wetmore

Re: JSON Objects renaming (was Re: ASDoc, Routing, Releases)

I’m really not sure how you plan on going about strongly typing hierarchical data. > On Feb 6, 2018, at 7:13 PM, Gabe Harbs wrote: > > What kind of utility do you have in mind? > > >> On Feb 6, 2018, at 7:09 PM, Alex Harui wrote: >> >> Don't

Re: JSON Objects renaming (was Re: ASDoc, Routing, Releases)

What kind of utility do you have in mind? > On Feb 6, 2018, at 7:09 PM, Alex Harui wrote: > > Don't bother making VO's by hand for ASDoc. Let's write a utility to > generate it. It will save everyone time. If you want to see > bin/js-release, change the build to

Re: JSON Objects renaming (was Re: ASDoc, Routing, Releases)

Don't bother making VO's by hand for ASDoc. Let's write a utility to generate it. It will save everyone time. If you want to see bin/js-release, change the build to not use ADVANCED_OPTIMIZATIONS for now. There are lots of reasons to avoid using plain Object in a Royale app other than as a

Re: JSON Objects renaming (was Re: ASDoc, Routing, Releases)

Huh? I don’t see how it’s possible to avoid Object completely. Even using VOs require constructing them from Objects when coming from outside sources. Again: I’m not arguing against using VOs when possible/practical. I’m just arguing that use of dot notation on Objects shouldn’t blow up your

Re: JSON Objects renaming (was Re: ASDoc, Routing, Releases)

Good catch. I fixed that. Actually, you are arguing in favor of ValueObjects. The error was there because commitObj was a plain Object so the compiler couldn't understand more about it. We want to not have any plain objects in a Royale app. They only create potential problems. In fact, maybe

Re: Website description

On Feb 5, 2018 11:39 PM, "Justin Mclean" wrote: Hi, Or if you want to use slack for Royale then create a channel on the “official” ASF slack group. Thanks, Justin 1. https://the-asf.slack.com Justin, Please don't invent issues when there are none. If you stop for

Re: JSON Objects renaming (was Re: ASDoc, Routing, Releases)

To illustrate that the VO solution is also error prone, I’m pretty sure that this page has a mistake: http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/RoyaleDocs_Staging/lastSuccessfulBuild/artifact/_site/create-an-application/application-tutorial/value-objects.html

Re: JSON Objects renaming (was Re: ASDoc, Routing, Releases)

Related: On this page: http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/RoyaleDocs_Staging/lastSuccessfulBuild/artifact/_site/create-an-application/application-tutorial/data.html

Re: JSON Objects renaming (was Re: ASDoc, Routing, Releases)

I'm not sure how solution should look like, but in case of going by the parse path I have raised some time ago jira [1]. Maybe it is a good place to refresh that. [1] https://issues.apache.org/jira/browse/FLEX-35297 Thanks, Piotr 2018-02-06 10:14 GMT+01:00 Gabe Harbs : >

Re: ASDoc, Routing, Releases

+1 for automatic copying ASDoc app to the Royale website. :) Thanks, Piotr 2018-02-06 9:53 GMT+01:00 Alex Harui : > The current implementation only calls your custom logic when the hash > changes. I'm not sure if there is a way to make that more generic, but > maybe

Re: JSON Objects renaming (was Re: ASDoc, Routing, Releases)

I’m suggesting we have a compiler option to do it for all Object-typed properties. This problem is not limited to objects coming from JSON. The bracket access gets converted to dot access when google minifies the code, so there’s no effect on the minified code other than preventing the

Re: JSON Objects renaming (was Re: ASDoc, Routing, Releases)

I'm not convinced we can know when to generate obj.property vs obj["property"] unless we do it for all Objects, not just ones that came from JSON. Or for all property access. And that is at least 3 extra characters per access for anything that isn't JSON. I would rather we find ways to make use

Re: ASDoc, Routing, Releases

Hi Alex, in fact I think that's what it should be :) don't know if as part of the website or in the royale-docs live url. Anyway the proposed url is ok. When I updated the website I overlay the folder with changes, as in the website there's no "/asdoc/" url it will be untouched by my changes

Re: ASDoc, Routing, Releases

Hi Alex, for "generic" I want to say that "routing" should be a framework feature and we should have a library that could link and use with some API in order to make any royale app capable of use permalinks 2018-02-05 17:15 GMT+01:00 Alex Harui : > Regarding Routing.