Re: 0.9.3 Release

2018-05-16 Thread Piotr Zarzycki
I do mean let's have it radical changes, but not partially as it is now. It looks like discussion may bring us some solution. Thanks, Piotr On Thu, May 17, 2018, 8:50 AM Harbs wrote: > Having trouble getting this email to “take”. Trying a paste link instead... > > It looks like it does have iss

Re: 0.9.3 Release

2018-05-16 Thread Harbs
Having trouble getting this email to “take”. Trying a paste link instead... It looks like it does have issues. I just pulled the 0.9.3 branch. I get a lot of these warnings when I compile the framework: https://paste.apache.org/Wy9t I used it to compile my app, a

Re: 0.9.3 Release

2018-05-16 Thread Harbs
Having trouble getting this email to “take”... It looks like it does have issues. I just pulled the 0.9.3 branch. I get a lot of these warnings when I compile the framework: [java] /Apache/royale-asjs/frameworks/projects/DragDrop/src/main/royale/org/apache/royale/html/beads/ButtonBarReorde

Re: 0.9.3 Release

2018-05-16 Thread Piotr Zarzycki
Hi Guys, We definitely cannot have in release breaking changes. We may have another customer. I would like to avoid impression for him where in 0.9.3 we have some changes in the next release there is radical another direction. It would be great if we could merge at least compiler if there were s

Build failed in Jenkins: royale-asjs_jsonly #809

2018-05-16 Thread apacheroyaleci
See -- [...truncated 1.77 MB...] [mxmlc] org.apache.royale.html.ButtonBar depends on org.apache.royale.html.List [mxmlc]

Build failed in Jenkins: royale-asjs_jsonly #808

2018-05-16 Thread apacheroyaleci
See -- [...truncated 1.76 MB...] [mxmlc] org.apache.royale.html.ButtonBar depends on org.apache.royale.html.List [mxmlc]

Re: Type Selector Approximation (was Re: [DISCUSS] Explanation of the changes)

2018-05-16 Thread Alex Harui
Typo in there: "...make the compiler output the class selectors that are supposed to approximate type selectors..." Sorry, -Alex On 5/16/18, 2:26 PM, "Alex Harui" wrote: Changing the subject line... What is the failure case? I think I've gotten lost somewhere. IMO, the

Type Selector Approximation (was Re: [DISCUSS] Explanation of the changes)

2018-05-16 Thread Alex Harui
Changing the subject line... What is the failure case? I think I've gotten lost somewhere. IMO, the goal is to approximate Type Selectors (effectively extend Type Selectors to other types not specified by W3C), and AIUI, order of class selectors is about specificity and order of appearance in

Re: Transferring Collections with RemoteObject/AMF

2018-05-16 Thread Carlos Rovira
Just tried AMF in Edge and IE11 and both works as well :) 2018-05-16 16:13 GMT+02:00 Carlos Rovira : > Hi Piotr, > > finaly Safari works ok as well, I was checked some development tools and > seems that was interfering, so for now works great in all 3 browsers (still > need to test on Windows IE1

Re: [DISCUSS] Explanation of the changes

2018-05-16 Thread Carlos Rovira
I'm not sure that making different namespaces be interpreted in different ways would be good. That kind of things would be things that people coming would need to now or they will find problems when using Royale. In the other hand that kind of things (this work in this way for A but works in this o

Re: [DISCUSS] Explanation of the changes

2018-05-16 Thread Harbs
I guess it depends. As long as the styling is set by class selectors, it will work because class selectors trump type selectors. I think it would at least be better than what we have now. > On May 16, 2018, at 10:42 PM, Alex Harui wrote: > > Would that work? I think any TLC with an HTMLButto

Re: 0.9.3 Release

2018-05-16 Thread Alex Harui
I'm pretty sure the branches were cut before the changes in question. You can pull down the branches and build them to verify. Or look at their history on GitHub. Om, did you see a date for when Maven SCM would be released? The only response I got from the Maven folks was to build Maven SCM

Re: [DISCUSS] Explanation of the changes

2018-05-16 Thread Alex Harui
Would that work? I think any TLC with an HTMLButtonElement as its element (or sub-element) will still be affected by any Button type selector in some CSS file. Or maybe I don't fully understand what you are proposing. -Alex On 5/16/18, 9:41 AM, "Harbs" wrote: Sure. I wonder if we shoul

Re: 0.9.3 Release

2018-05-16 Thread Harbs
different *swcs* (I really need to turn off auto-correct…) > On May 16, 2018, at 10:33 PM, Harbs wrote: > > different secs

Re: 0.9.3 Release

2018-05-16 Thread Harbs
The last time I checked, the last commit that worked on existing apps was 88cffe995de541584024cbf38eb016acfc677f98 I have not checked develop for the last 11 commits or so. Unless package names have been reverted I assume the problem still exists. I see three options: 1. Revert develop back to

Re: 0.9.3 Release

2018-05-16 Thread OmPrakash Muppirala
So we just revert back develop to the last known good build? Sorry, I don't want to trample on anyone's changes, but we need to either do that or wait until all issues are fixed. Thoughts? On Wed, May 16, 2018 at 11:46 AM, Harbs wrote: > Right now I’m pretty sure we have classes with changed p

Re: 0.9.3 Release

2018-05-16 Thread Harbs
Right now I’m pretty sure we have classes with changed package names. That will break existing applications. I doubt we’re going to be finished with the “refactor” discussion before we get the 0.9.3 release out. I’d like to be sure that no package names are changed in this release. I don’t real

Re: 0.9.3 Release

2018-05-16 Thread OmPrakash Muppirala
On Wed, May 16, 2018, 9:42 AM Harbs wrote: > Can we make sure the release does not have any breaking changes currently > in develop? The fixes need to go into develop so that we can simply cut a release branch of off develop. If not we will have to cherry pick. What is the status of develop?

Re: 0.9.3 Release

2018-05-16 Thread Harbs
Can we make sure the release does not have any breaking changes currently in develop? > On May 16, 2018, at 2:58 AM, OmPrakash Muppirala wrote: > > On Mon, May 14, 2018 at 12:56 PM, Alex Harui > wrote: > >> Update: I’ve been trying to get the release script to work o

Re: [DISCUSS] Explanation of the changes

2018-05-16 Thread Harbs
Sure. I wonder if we should handle different namespaces differently. Maybe the following two namespaces should get proper type selectors, while any others would get class selectors? http://www.w3.org/1999/xhtml library://ns.apache.org/royale/html Harbs > On May 15, 2018, at 6:52 PM, Alex Haru

Re: Transferring Collections with RemoteObject/AMF

2018-05-16 Thread Carlos Rovira
Hi Piotr, finaly Safari works ok as well, I was checked some development tools and seems that was interfering, so for now works great in all 3 browsers (still need to test on Windows IE11 and Edge), so not need to fill any bug for now ;) About the place where you run the client, right, you need t

Re: Transferring Collections with RemoteObject/AMF

2018-05-16 Thread Piotr Zarzycki
Carlos, Last time when I was testing AMF PHP it was working fine on my sight. I had to just push application in the same place as AMF server. I didn't test it in Safari. Great to hear that! Congrats! Thanks, Piotr 2018-05-16 15:46 GMT+02:00 Carlos Rovira : > Piotr, > > I finally get total comm

Re: Transferring Collections with RemoteObject/AMF

2018-05-16 Thread Carlos Rovira
Piotr, I finally get total communication with my Backend!! :D The problem is localized in Safari. I was testing all the time with Safari, and then I tried with Chrome and it worked. I tried with Firefox as well and worked as well. So we have some bug that generates some problem in deserialization

Build failed in Jenkins: royale-asjs_jsonly #807

2018-05-16 Thread apacheroyaleci
See -- [...truncated 1.77 MB...] [mxmlc] org.apache.royale.html.ButtonBar depends on org.apache.royale.html.List [mxmlc]

Build failed in Jenkins: royale-asjs_jsonly #806

2018-05-16 Thread apacheroyaleci
See Changes: [yishayjobs] Make controller more reusable -- [...truncated 1.76 MB...] [mxmlc] org.apache.royale.html.ButtonBar depends on

Re: Transferring Collections with RemoteObject/AMF

2018-05-16 Thread Carlos Rovira
Hi Piotr, right! I think we still have something wrong. Let me explain: I'm right now trying to make a first communication with our company app. I get to communicate from Royale to Java sending a populate type object, but I'm still don't get the response ok, I'm getting a "Failed decoding the resp

Re: Transferring Collections with RemoteObject/AMF

2018-05-16 Thread Piotr Zarzycki
Hi Carlos, I'm wondering now what should be on the AMF PHP sight to have it working. Maybe I will try to find some time to investigate it. Since on Java HashSet is ok, maybe on PHP sight there is something which can accept ArrayList. ;) Thanks, Piotr 2018-05-16 12:02 GMT+02:00 Carlos Rovira : >

Transferring Collections with RemoteObject/AMF

2018-05-16 Thread Carlos Rovira
Hi, just let you know that I tried to retrieve a Collection from Java with RemoteObject/AMF, and that worked without problem. I updated the example with this test that compose a java.util.Set (a HashSet), send it and we get it in Royale as a royale ArrayList. I'm a bit surprised that this works w

Build failed in Jenkins: royale-asjs_jsonly #805

2018-05-16 Thread apacheroyaleci
See Changes: [yishayjobs] Make ComboBoxView more reusable [yishayjobs] remove from controller logic which is handled by view -- [...truncated