Welcome to the CoronaCards for OS X beta forum.
My name is Perry and I’ll be your engineer today. Please let me know how I can help you get your Corona projects running on OS X.
Congratulations! I am very happy how much appears to be working. I imagine there’s a working list of what’s not supported or planned to be supported. In my testing, in addition to the sandbox issue and general plug-in issues, I was also unable to use native.newWebView and native.newVideo - are these intended to work?
Check it out!
Awesome! I love seeing screenshots of newly ported apps.
At the moment we’re not planning on implementing much in the native.* space because most of them are better implemented as part of the Cocoa app (“better” in the sense they will be more appropriate for desktop use). However, the other side of the coin is wanting to maximize compatibility between device and desktop builds so there will likely be some give and take in this area.
One thing that is on my list to do is to make sure that unimplemented APIs fail gracefully and don’t do something nasty like crash (like I’ve just noticed native.showWebPopup() does).
I’m really excited to be part of this beta program! I can’t wait to get Doggins running on desktops.
Like @tschussler, I use native.newVideo in my game to display several video cutscenes (6 in total). I’ve never programmed in Objective-C/Cocoa, so I have no idea how to go about getting started replacing this Corona API call with my own handler. Any advice/suggestions on getting started?
Thanks a lot!
@tschussler: Having issues building a project, what OS X and Xcode are you running, and did you get any errors along the way such as code sign fails exit code 1, or any errors such as this?
Appreciate anyone’s help, we are running OS X 10.10.2 and Xcode the latest version
I’m using the same release of Mac OS X and XCode 6.2. I set the Code Signing Identity to Developer ID: * (automatic).
It would really be great to see support for native.webView because re-implementing all of the code for that in our applications will take a lot of work for little gain and as you mentioned create an obstacle for deploying single source codebases. I could definitely see why you wouldn’t want to support native.newVideo though as that isn’t really one of Corona strongest areas.
@tschussler: Did you ever get any errors at all that you had to fix, or did it just work automatically for you?
I’m getting the Warning: Warning: usage of --preserve-metadata with option “resource-rules” (deprecated in Mac OS X >= 10.10)!
failed with exit code 1 error
Hi all, excited to see that this is being worked on.
I’m trying to port a simple app that I’ve run before on OUYA and Fire TV (1280x720). Unfortunately, the settings in my config.lua are overridden and XCode tries to run in what appears to be a portrait phone orientation. Does anyone know why this might be / how to change it? Thanks!
Can you post your config.lua?
Hi Rob, I actually found the issue - width and height had to be switched in config.lua – it was not reading my ‘landscape only’ build settings and therefore was building a window 768px wide and 1024px tall.
Just remember, config.lua should always be done assuming the device is in portrait orientation.
Rob
Congratulations! I am very happy how much appears to be working. I imagine there’s a working list of what’s not supported or planned to be supported. In my testing, in addition to the sandbox issue and general plug-in issues, I was also unable to use native.newWebView and native.newVideo - are these intended to work?
Check it out!
Awesome! I love seeing screenshots of newly ported apps.
At the moment we’re not planning on implementing much in the native.* space because most of them are better implemented as part of the Cocoa app (“better” in the sense they will be more appropriate for desktop use). However, the other side of the coin is wanting to maximize compatibility between device and desktop builds so there will likely be some give and take in this area.
One thing that is on my list to do is to make sure that unimplemented APIs fail gracefully and don’t do something nasty like crash (like I’ve just noticed native.showWebPopup() does).
I’m really excited to be part of this beta program! I can’t wait to get Doggins running on desktops.
Like @tschussler, I use native.newVideo in my game to display several video cutscenes (6 in total). I’ve never programmed in Objective-C/Cocoa, so I have no idea how to go about getting started replacing this Corona API call with my own handler. Any advice/suggestions on getting started?
Thanks a lot!
@tschussler: Having issues building a project, what OS X and Xcode are you running, and did you get any errors along the way such as code sign fails exit code 1, or any errors such as this?
Appreciate anyone’s help, we are running OS X 10.10.2 and Xcode the latest version
I’m using the same release of Mac OS X and XCode 6.2. I set the Code Signing Identity to Developer ID: * (automatic).
It would really be great to see support for native.webView because re-implementing all of the code for that in our applications will take a lot of work for little gain and as you mentioned create an obstacle for deploying single source codebases. I could definitely see why you wouldn’t want to support native.newVideo though as that isn’t really one of Corona strongest areas.
@tschussler: Did you ever get any errors at all that you had to fix, or did it just work automatically for you?
I’m getting the Warning: Warning: usage of --preserve-metadata with option “resource-rules” (deprecated in Mac OS X >= 10.10)!
failed with exit code 1 error
Hi all, excited to see that this is being worked on.
I’m trying to port a simple app that I’ve run before on OUYA and Fire TV (1280x720). Unfortunately, the settings in my config.lua are overridden and XCode tries to run in what appears to be a portrait phone orientation. Does anyone know why this might be / how to change it? Thanks!