Re: Mobile vs Desktop diferences in components (Was: Re: Restarting contributions)

2017-11-04 Thread Carlos Rovira
Hi Alex, that sounds very good to me and is where Apache Royale *magic* is. So, I think it would be great to make our CSS to handle devices and/or OS in order to have all possible flavors and be able to compile targeting some device or OS Thanks! 2017-11-03 18:06 GMT+01:00 Alex Harui

Re: Working on UI Controls styling

2017-11-04 Thread Carlos Rovira
HI Alex, 2017-11-03 17:52 GMT+01:00 Alex Harui : > Hi Carlos, > > I skimmed through https://material.io/guidelines/# last night. > > My impression is that there were two parts to it. First was the > environment/principles section which talked about physical objects

Re: Working on UI Controls styling

2017-11-04 Thread Piotr Zarzycki
Carlos, I just wanted to point to your last sentences. I think we don't know for sure what can we do with Basic. Let's go and try if we came up that something is not achievable let's discuss what need to be done. Piotr On Sat, Nov 4, 2017, 16:19 Carlos Rovira wrote: >

Re: Mobile vs Desktop diferences in components (Was: Re: Restarting contributions)

2017-11-04 Thread Carlos Rovira
Hi, for me states are something very concrete and I don't see too much relation with what we want to get about discriminate layout for different kind of devices states seems to me more widely uses to handle application states that are not dependent on how the app is visualized. For that reason I

Re: Unit Tests et. al.

2017-11-04 Thread Greg Dove
Harbs, I don't know if it still works since changes to Royale, but I had something rudimentary for cross-target unit testing quite shortly after working on the reflection support last year, in fact that was my primary reason for choosing to focus on reflection at the time. It was visual output

Re: Unit Tests et. al.

2017-11-04 Thread Harbs
Thanks! That looks very useful. I started work on a feature/testing branch. I’ll try to merge what you did into what Josh did. I’m going to try to get the existing Core and/or Basic tests working in both swf and node js output tomorrow. We’ll see how well I do… ;-) We might need different

Re: Unit Tests et. al.

2017-11-04 Thread Harbs
FYI, It compiled and worked on the first try. :-) The test view is very cool. I’m not sure if I missed it when you mentioned this, but I like. :-) Harbs > On Nov 4, 2017, at 10:30 PM, Greg Dove wrote: > > Harbs, I don't know if it still works since changes to Royale, but

Re: Unit Tests et. al.

2017-11-04 Thread Harbs
Wow. I don’t think I ever noticed the tutorial for FlexUnit on the Flex site: https://flex.apache.org/flexunit/tutorial/ Who put that together? Looks like a lot of work went into that. Harbs > On Nov 4, 2017, at 6:59 PM, Harbs

Re: Unit Tests et. al.

2017-11-04 Thread Harbs
Reading the FlexUnit docs, I see that there’s a lot of advanced features (that I never even knew about). I’m going to start with just the metadata tags that Josh wrote support for (i.e. Before, Text and After). Maybe I’ll add Ignore, BeforeClass and AfterClass as well. A question I have for

RE: FB : Strange side effects of -js-output argument

2017-11-04 Thread Idylog - Nicolas Granon
It's not such a big issue for now : what I have done is, I have a small eclipse plug-in that can copy files from workspace to another destination after compile. Since we have other (non Royale) files to copy to the http server anyway... Your suggestion (adding the js-output argument in

Re: Unit Tests et. al.

2017-11-04 Thread Harbs
Awesome! I assume that this means I can code the code to the Royale repo under Apache 2. Right? Harbs > On Nov 3, 2017, at 5:37 PM, Josh Tynjala wrote: > > Please feel free to use my test runner. I'm happy to commit it somewhere to > make it official Apache code, if

Re: Mobile vs Desktop diferences in components (Was: Re: Restarting contributions)

2017-11-04 Thread Alex Harui
Hmm. That looks more like States than media query. It brings up the question of how much of the visuals should be in CSS vs in MXML. Royale should someday be able to do this same sort of thing via CSS Media Query. I think it would look something like: MXML: CSS: @media (max-width:

Re: Unit Tests et. al.

2017-11-04 Thread Harbs
It looks like FlexUnit is currently broken. I’m getting the following output when trying to run the FlexUnit tests on Core and Basic: [mxmlc] /Users/harbs/Documents/ApacheRoyale/flex-flexunit/FlexUnit4/target/flexunit-4.3.0-20140410-as3_4.12.0.swc Warning: The definition