Jump to content

[TOPIC: topicViewTemplate]
[GLOBAL: userSmallPhoto]
Photo

Building desktop app for testing
Started by kalle.jillheden Aug 21 2015 01:32 PM

3 replies to this topic
win32 build corona editor desktop

Best Answer Joshua Quick , 21 August 2015 - 02:29 PM

Our desktop app support is still in beta.  That's why we put "BETA" in huge all caps letters in the build dialog.  :)

We do plan on adding better testing support to the Corona Simulator in the future.  We'll eventually get there.

The Corona Shell is definitely the tool to use at the moment.

 

Side Note: The Windows "Corona Shell" was a cool little hidden Easter Egg that we've made available in the Corona SDK before we announced beta Win32 desktop app support.  ;)

[TOPIC CONTROLS]
This topic has been archived. This means that you cannot reply to this topic.
[/TOPIC CONTROLS]
[modOptionsDropdown]
[/modOptionsDropdown]
[reputationFilter]
[TOPIC: post.html]
#1

kalle.jillheden

[GLOBAL: userInfoPane.html]
kalle.jillheden
  • Observer

  • 13 posts
  • Corona SDK

I'm trying to learn how to make desktop apps with Corona, but I am having some struggles.
 
I am using the Corona Editor addon for sublime text and when I am trying to build/run the project it shows up with my app in a simulated phone, while I am trying to build it as a desktop app...
 
Is it something I am doing wrong?
 
I would just like a window like the one you get when you do a final build of the project, but when doing Tools>Build or Corona Editor>Run Project I get an android or something.
 
It's like the window table in build.settings is ignored when doing a fast build..
 
Example outcome from this very simple build.settings file:

settings = { window = { defaultMode = "minimized" } }

Now from this if I build the project and then run the desktop app it starts minimized as expected, but not if I run the project via the Corona Editor.
 
 
And I hope you understand that this is important because, opening the simulator, then opening the project, then building the project for desktop, then open the built application, takes far too long when doing small changes. You want to just change some code and then immediately build and see the new version, not this silly work around as it is now.



[TOPIC: post.html]
#2

kalle.jillheden

[GLOBAL: userInfoPane.html]
kalle.jillheden
  • Observer

  • 13 posts
  • Corona SDK

Just found out I can point the Corona Editor to build via the Corona.Shell.exe instead of Corona Simulator.exe. This fixed my problem, but still I think it would be nice if I wouldn't have to change a bunch of stuff to just test build the app.

 

Oh well, cant get everything in life, as they say



[TOPIC: post.html]
#3

Joshua Quick

[GLOBAL: userInfoPane.html]
Joshua Quick
  • Moderator

  • 3,397 posts
  • Corona Staff

  Best Answer

Our desktop app support is still in beta.  That's why we put "BETA" in huge all caps letters in the build dialog.  :)

We do plan on adding better testing support to the Corona Simulator in the future.  We'll eventually get there.

The Corona Shell is definitely the tool to use at the moment.

 

Side Note: The Windows "Corona Shell" was a cool little hidden Easter Egg that we've made available in the Corona SDK before we announced beta Win32 desktop app support.  ;)



[TOPIC: post.html]
#4

kalle.jillheden

[GLOBAL: userInfoPane.html]
kalle.jillheden
  • Observer

  • 13 posts
  • Corona SDK

Our desktop app support is still in beta.  That's why we put "BETA" in huge all caps letters in the build dialog.  :)
We do plan on adding better testing support to the Corona Simulator in the future.  We'll eventually get there.
The Corona Shell is definitely the tool to use at the moment.


Ok that makes sence. Was just a bit tricky finding that you're supposed to use the shell. =)


[topic_controls]
[/topic_controls]