Hey guys,
Flashers have been trained that when “print” functions are called, or when errors occur, the **terminal window** slaps us in the face “up front” and “by default”.
Likewise, Javascript developers know how to launch the “Tools > Error console” so that they can monitor events “on demand”.
I would swap things around a little bit and make “Corona Terminal” the primary “Corona Simulator.app”. You could quickly hide the terminal window during startup, then when a “print” or “error” event occurs bring the terminal window up and slap us in the face.
In addition I would add “View Output” and “View Debugger” to the “Window” menu.
File Edit Hardware Window Help
- View Ouput
- View Debugger (Or maybe an additional “Tools” menu item?)
Also, you could put a setting in the preferences to “disable automatically displaying output and errors”, to bring things back to the way you have them now.
FYI: The debugger is still a mystery to me… it just crashes every time I try and launch something in it.
Why? (The long winded explanation)
I had an awful time in the beginning with “print”, I was never able to see where the “print” output was going. ( The grey and gloomy “Corona Terminal”, “debugger” and “simulator” icons seemed like they should not be touched. )
After struggling with trying to find where the “print” output was going, I ended up using Console to detect errors and resorted to building my own “print” class, which renderd text into the display port so I could “see” what the heck was going on.
Crazy, I know, but I spent, like, an hour or more digging around for “print” ouput. The reason I had so much trouble was that it **seemed** like (documentation-wise) you have to build your project out as a full app (e.g. “build”), then run your app under terminal in order to get the “print” function to show what was going on in your code.
Obviously, that’s not the case.
But when I was first trying to learn, that’s what it seemed like. Most of us “script babies” try to avoid terminal as much as we can.
It wasn’t until after I finished my first Corona App that I discovered how to launch the simulator using the “Corona Terminal” thingy… I didn’t use that in the beginning because I thought it was a system component or something or other.
This feature would help Flasher-script-babies, like myself, quickly get a grip on the “print” feature, which is imperative during the learning curve to “see” what’s going on in the code.
[import]uid: 616 topic_id: 7909 reply_id: 307909[/import]