Re: Removing the * selector

Here’s a first stab at that: https://github.com/apache/royale-compiler/wiki/Eclipse-Setup > On Feb 23, 2018, at 10:11 AM, Piotr Zarzycki > wrote: > > Can you please describe how to setup debugger for

Re: Removing the * selector

I think all you have to do in this case is remove [Bindable]. You can still initialize statics as long as there aren't certain kinds of dependencies in there. An alternative is to force a simple static initialization that depends on ValueChangeEvent that the remove circulars code can detect.

Re: Removing the * selector

You should not need to exclude defaults.css. We want to try to separate styles to basic.css so you don't need to. MDLTabsExample broke with a recent change I made because MaterialDesignLite.swc is using typeNames and className inconsistently with the rest of the framework. I think we should set

Re: Removing the * selector

I think value and ordinal are not changing later. I will try refactor that class to do not use static instantiation, but it will probably use some constant, because it have to emulate Enums. 2018-02-23 9:26 GMT+01:00 Alex Harui : > Well, in theory yes the compiler needs

Re: Removing the * selector

Well, in theory yes the compiler needs more work, but I don't think it is practical to solve it in the compiler in any reasonable amount of time. I think you'd have to write a code-flow analyzer. We don't have a definitive way of knowing what goog.requires are needed at static initialization

Re: Removing the * selector

Because I see that we are missing in the file: ->goog.require('org.apache.royale.events.ValueChangeEvent'); That's why I'm assuming this is a problem, so wonted to debug it somehow. 2018-02-23 9:11 GMT+01:00 Piotr Zarzycki : > Alex, > > Can you please describe how

Re: Removing the * selector

Alex, Can you please describe how to setup debugger for Royale compiler on the Wiki? I would like to setup it for me. This is probably issue in RoyaleEmitter .

Re: Removing the * selector

This is in the compiler right ? 2018-02-23 9:06 GMT+01:00 Alex Harui : > Feel free to dig in and fix it. > > On 2/22/18, 11:59 PM, "Piotr Zarzycki" wrote: > > >Your changes related to circulars helped with static Binding, but there is >

Re: Removing the * selector

Feel free to dig in and fix it. On 2/22/18, 11:59 PM, "Piotr Zarzycki" wrote: >Your changes related to circulars helped with static Binding, but there is >still some problems with that class [1]. I've updated example with you >newest changes [2]. Take a look into the

Re: Removing the * selector

Your changes related to circulars helped with static Binding, but there is still some problems with that class [1]. I've updated example with you newest changes [2]. Take a look into the console. [2] [1] https://goo.gl/Y9YuuJ [2]

Re: Removing the * selector

By turning off you mean something like this ? -> https://github.com/apache/royale-asjs/commit/4d298a160aa388eb6306c6f0f80a3269ca240b40 2018-02-23 8:48 GMT+01:00 Piotr Zarzycki : > I pickup latest build and MDLTabsExample doesn't look like it should be. > I would like

Re: Removing the * selector

I pickup latest build and MDLTabsExample doesn't look like it should be. I would like to understand what I need to do in order to get the look back. What do you mean by that: " MDL also needed to turn off default layout in the Grid." I see that you have created that file [1] which simply force

Re: Removing the * selector

I moved more styles from the framework to the theme to deal with the wrong layout in MDLTabsExample. MDL also needed to turn off default layout in the Grid. The data binding static variable issue turned out to be the remove-circulars code which is now on by default. I fixed that as well.

Re: Removing the * selector

Isn't that a different problem? I thought you were having problems getting a dataProvider assigned? -Alex On 2/22/18, 3:34 PM, "piotrz" wrote: >I'm building them using JSonly Royale and Moonshine. Tomorrow my time I >will >try Maven build. > >If I have this:

Re: Removing the * selector

I'm building them using JSonly Royale and Moonshine. Tomorrow my time I will try Maven build. If I have this: -compiler.exclude-defaults-css-files=BasicJS.swc:defaults.css Example looks like that: If remove this:

Re: Removing the * selector

MDLDynamicTabsExample looks ok to me. What do you see wrong with it? On 2/22/18, 1:21 PM, "Piotr Zarzycki" wrote: >I think the best example would be the simplest one. Please look into >the MDLDynamicTableExample or MDLDynamicTabsExample and see how table/tabs >looks

Re: Removing the * selector

I think the best example would be the simplest one. Please look into the MDLDynamicTableExample or MDLDynamicTabsExample and see how table/tabs looks like. Thanks, Piotr 2018-02-22 22:10 GMT+01:00 Piotr Zarzycki : > I did a bit more experiments. I've declared variable

Re: Removing the * selector

I did a bit more experiments. I've declared variable like that: [Bindable] public var comboList:Array = RoleEnum.comboList; compoList was changed to get/set in JavaScript. I've placed breakpoint in setter and it didn't raised. Piotr. 2018-02-22 21:44 GMT+01:00 Piotr Zarzycki

Re: Removing the * selector

Maybe there problem started to occur because the getter of RoleEnum is static [1] [1] https://goo.gl/rPkNog 2018-02-22 21:32 GMT+01:00 Piotr Zarzycki : > Link with non working version [1]. Select one row and see what is in the > console. > > [1]

Re: Removing the * selector

Link with non working version [1]. Select one row and see what is in the console. [1] https://transpiledactionscript.com/dev/examples/PureMVCEmployeeAdminBasic/ Thanks, Piotr 2018-02-22 21:26 GMT+01:00 Piotr Zarzycki : > Link is to the old version which is working. I

Re: Removing the * selector

Link is to the old version which is working. I can deploy somewhere non working version if it helps. Let me do this and I will provide you link in couple of minutes. DropDownList will be available once you click on some row in the DataGrid. 2018-02-22 21:20 GMT+01:00 Alex Harui

Re: Removing the * selector

I may not be understanding you. In theory, nothing has changed that should affect your code, but I did have to replace some public vars on the Binding classes so maybe I messed up there, although DataBindingExample is working. In this last link, which my email server has obfuscated, appears to

Re: Removing the * selector

Above problems are with MDL version of this example [1], but I compiled also Basic version where I don't use anything from MDL and have the same issue. [1]

Re: Removing the * selector

Another question. I build one of my example with newest royale package. I have following static getter [1]. This code previously was working [2]. Now this Array is not being assigned to dataProvider. My dataProvider is undefined. Can you say what could change, if not I will prepare small example.

Re: Removing the * selector

On 2/22/18, 11:49 AM, "Piotr Zarzycki" wrote: >Alex, > >So in my css I cannot do such things ? > >global { > IStatesImpl: ClassReference("org.apache.royale.core.SimpleStatesImpl"); >} That will still work, because IStatesImpl is not css-compliant, so it is only

Re: Removing the * selector

Alex, So in my css I cannot do such things ? global { IStatesImpl: ClassReference("org.apache.royale.core.SimpleStatesImpl"); } 2018-02-22 19:38 GMT+01:00 Piotr Zarzycki : > Ahh that is what you mean! :) Good idea. I will try in the next week play > with that!

Re: Removing the * selector

Ahh that is what you mean! :) Good idea. I will try in the next week play with that! :) Thanks Harbs for clarification :) Piotr 2018-02-22 18:59 GMT+01:00 Alex Harui : > Yep. It would fun to see what APIs Moonshine itself uses. > > -Alex > > On 2/22/18, 9:48 AM, "Gabe

Re: Removing the * selector

Yep. It would fun to see what APIs Moonshine itself uses. -Alex On 2/22/18, 9:48 AM, "Gabe Harbs" wrote: >I think Alex was suggesting to run it on the Moonshine *codebase*. > >> On Feb 22, 2018, at 7:39 PM, Piotr Zarzycki >>wrote: >> >> Yep.

Re: Removing the * selector

I think Alex was suggesting to run it on the Moonshine *codebase*. > On Feb 22, 2018, at 7:39 PM, Piotr Zarzycki wrote: > > Yep. That's what I suggested to Alina, because she was started to use > Moonshine. I think it's doable also through the VSCode. In the end it is

Re: Removing the * selector

Yep. That's what I suggested to Alina, because she was started to use Moonshine. I think it's doable also through the VSCode. In the end it is all about passing that argument as additional compiler options. 2018-02-22 18:36 GMT+01:00 Alex Harui : > Isn't Moonshine

Re: Removing the * selector

Isn't Moonshine also a SWF-based app? Could try it there too. -Alex On 2/22/18, 9:31 AM, "Piotr Zarzycki" wrote: >Carlos, > >It would be great to get that report from your application! > >Thanks, Piotr > >2018-02-22 18:17 GMT+01:00 Alex Harui

Re: Removing the * selector

Your point of view is valid, but it might depend on the kind of application. Some might have 100's of views to port, others might only have 2 or 3 views and a million lines of business logic. In another thread I mentioned the -api-report option I added. It would be interesting for folks to try

Re: Removing the * selector

Without know nothing about the solution I want to share a though: I think the implementation of all the things related to visuals (and css is one of them) is completely different in Royale to what it was in flex, so maybe we should not be worried that CSS is not following main flex rules. For me

Re: Removing the * selector

Well, it might be a migration issue in the sense that you could use a selector called "global" in Flex and it would become the default value for styles. Flex and Royale CSS has non-compliant CSS in it like "cffHinting" or "focusSkin" in Flex or "IStatesImpl" in Royale. Non-compliant styles are

Re: Removing the * selector

Hi Alex I hope that vivid work let us know much more about all of this. Right now I don't dare to adventure how this should be... 2018-02-22 10:29 GMT+01:00 Alex Harui : > > I think I agree. That's sort of where I was heading by creating a > separate theme in

Re: Removing the * selector

Hi Andrew, this is new for Apache Royale since is how to deal with CSS and how browsers manage it. So maybe not much relation with Flex in this case Best Carlos 2018-02-22 13:27 GMT+01:00 Andrew Wetmore : > Is this a migration issue for Flex apps, or is this specific to

Re: Removing the * selector

Is this a migration issue for Flex apps, or is this specific to Royale? On Thu, Feb 22, 2018 at 5:29 AM, Alex Harui wrote: > > > On 2/22/18, 1:12 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" >

Re: Removing the * selector

On 2/22/18, 1:12 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: >Hi Alex, > >I think this is a very good change since I had many problems with MDL and >have to use the exclusion on CSS to make it work properly. >

Re: Removing the * selector

Hi Alex, I think this is a very good change since I had many problems with MDL and have to use the exclusion on CSS to make it work properly. If I understand ok, I should see fonts at 16px, that I think is nowadays the standard for "normal" text, so good. What I don't understand is what basic