Re: [Royale] Building Hello World on Mac

Hi Piotr, I'm removing the files from the Royale repo that FlexJS used in the installer. I just think we need to find other ways for Royale users to get Royale without relying on an Apache Flex branded app. Again, if you are not concerned about SWF output for Royale, you should be able to pull

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

Hi Carlos, Because we use CSS to choose beads, I think it might be possible to choose different views, layouts, etc based on media query. If there is some other popular way of reconfiguring layouts in JS we can certainly try to leverage that as well or instead. Of course, I could be wrong...

Re: Apache Royale static web site

Hi Carlos, I'm not quite sure what you meant here. I think without a deadline there is no chance they will approve. Is the deadline what you meant by "other option"? -Alex On 11/2/17, 4:36 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"

Re: Working on UI Controls styling

Hi, I want to expose my initial work (very very initial) on two styles for Royale Wireframe: https://snag.gy/tDFxQT.jpg (Wireframe intention is for quick Royale App prototyping, people will use this to start their applications, and then moving to it's own styling that could be another royale

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

Alex, for sizing and look and feel, yes, I propose media queries, I think this is what makes usable to use the same button component (or checkbox, radio, tooglebutton,) In the other hand there are other issues that should be managed with other techniques. For example would tooltips be in

Re: Apache Royale static web site

Hi, since nobody is responding to the latest plan of put static html site on our repo, I think this could be what we want and could get it live even without a concrete deadline so we can go with other solution with more or less time. Let me try to ask in the current thread with trademarks if it's

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

FYI, My PrintUI app supports touch events. Eventually, we’re going to change the UI (i.e. simplify some things) for phones, but right now, the UI works fine for both desktop and tablets. The touch support was added by using hammer.js.[1] The basics for adding that support was basically: #1

RE: Mobile vs Desktop diferences in components

In our eyes, having *components* that can run on desktop or mobile is certainly very interesting. After all, nothing prevent us from coding listeners that will never be triggered on desktop (swipe...). I know, I know, it will make the component heavier but not very much... And we are seeing

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

Hi Carlos, I agree that a great goal would be to allow the development of an application that can run anywhere. You are welcome to build components that can look different and interact differently in different environments. Under the covers, I hope they are compositions of beads. Royale

Re: Apache Royale static web site

I would ask for 90 days to give us a bit more time, but I think this is a good idea. > On Nov 2, 2017, at 11:44 PM, Alex Harui wrote: > > FWIW, maybe the least effort choice right now is to ask ASF Trademarks and > Infra for a 60 day exception to redirect royale.a.o

Re: Apache Royale static web site

FWIW, maybe the least effort choice right now is to ask ASF Trademarks and Infra for a 60 day exception to redirect royale.a.o to royale.codeoscopic.com. That'll keep us for burning more energy trying to make this work some other way so we can get other stuff done, including creating a similar

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

Hi Alex, my opinion here is different, since making different libraries for the same purpose make the user task more complicated. For example, for the case commented of touch vs mouse we could have only one button component that will use conditional compilation to get mouse for desktop and

Re: VSCode

Some other things to know that could help you with VSCODE: * For building a project you can use CMD+SHIFT+B Some projects has a .vscode folder and a tasks.json to use maven to build using that key combo. (See for example MDLExample) * You can launch the App as well when building For this in

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

I agree that some components in Mobile.swc could be moved elsewhere and used on desktops, but I thought there would be library of mobile components that default to different interaction models (gesture vs mouse). Flex had some mobile-specific components (ToggleSwitch, DateSpinner, etc). I

VSCode

Hi, Since FlashBuilder refuses to run for me, I thought I'd take a step into 2017 and use VSCode. Seems quite nice and well designed. I need help getting this to work for Royale. Or does it not yet work for Royale? I'm not sure what to do. Here is what I have done so far: Installed VSCode

Re: Trying to commit to royale-asjs repo

> the url I use to connect is : https://github.com/apache/royale-asjs.git > Yes. You’d only use one in your username if you fork the repo and submit pull requests. > On Nov 2, 2017, at 6:20 PM, Carlos Rovira > wrote:

Re: Event Metadata

Hi Nicolas, A breakdown would be nice, but I'm also curious about your evaluation process. Could you share what steps you are taking? Are you building simple tests of various features or just plain trying to port your existing code to Royale? Also, once you choose a development environment a

Re: Trying to commit to royale-asjs repo

Hi Harbs, in the process you describe, I need to use my GitHub password, but not the token Then, if I try to commit the commit fails. If I use Basic instead of Oauth, and use the token, then I can commit, but I have the problem described of having to put the token all times I commit

Re: [Royale] Building Hello World on Mac

I just checked and it's working. :) However I'm wondering what is for +config=royale ? It's working for me without this one. Why are you having -debug option I thought it is used when we are compiling to SWF. Without -debug I'm still getting JS application release and debug folder. Piotr

Re: [Royale] Building Hello World on Mac

Hi Harbs, I got it! You have helped me. I didn't realize that on Windows I had player global setup in environment variables all the time. On Mac I didn't make any setup, so probably simply copying there player global resolve issue. I just thought that on Mac I need to do some magic things in

Re: [Royale] Building Hello World on Mac

> The question is why compiler is complaining about missing playerglobal Do you have the playerglobal.swc there? > On Nov 2, 2017, at 5:11 PM, Piotr Zarzycki wrote: > > Hi Guys, > > I'm trying to build simple Hello World app on Mac with newest sources of > Royale

Re: [Royale] Building Hello World on Mac

Your output should look something like this: MXMLJSC +royalelib=/FlexSDK/FlexJSNightly/frameworks +configname=royale --debug=true --targets=JSRoyale > On Nov 2, 2017, at 5:21 PM, Harbs wrote: > > This does not look right: >

Re: [Royale] Building Hello World on Mac

This does not look right: -load-config+=obj/NewFlexJSBrowserProjectConfig.xml > On Nov 2, 2017, at 5:11 PM, Piotr Zarzycki wrote: > > Hi Guys, > > I'm trying to build simple Hello World app on Mac with newest sources of > Royale [1]. On windows exactly same

[Royale] Building Hello World on Mac

Hi Guys, I'm trying to build simple Hello World app on Mac with newest sources of Royale [1]. On windows exactly same application is building without the problem and not complaining with such errors. Maybe I'm missing something obvious. Windows version - Works OK [2] - Part of the console stack.

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

Hi Peter, thanks, I think would be great to have that in mind to avoid extra efforts for users. As applications are wired nowadays it would be bad for us if we have separate component libraries to target different devices. We should try to make differentiations in the components and we have

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

(copied from another email thread; this one seems more appropriate). I created the Mobile kit. I did it separately because it was supposed to mimic how UINavigationController, UIViewController, and UITabController work on iOS (which I'm more familiar with than Android). But there is nothing

RE: Event Metadata

Hi Nicolas, Very good perspective. I think Royale’s philosophy is to allow different component sets for different user types. The two obvious ones that exist right now are Basic and Express. Basic emphasizes small and fast, while Express emphasizes usable. A lot of the discussions you’ll see