this thread was closed, along with the forum containing it.
http://developer.anscamobile.com/forum/2011/02/07/support-command-line-thus-continuous-integration-builds
I’d like to bring it up again, because:
Imagine you are to build 2 Versions of an app for release: demo and full. For iphone, ipads, different androids each. So you have to click through the build screens: select appropriate profiles, fill in the app name, select output dir and target device at least. (the fontsize is very small in the dropdown btw and profiles are sorted the ansca way). 4 things that can go wrong per version multiplied by number of versions say 5 we end up with 20 clicks per build. Programmers are Programmers because they are bad at doing manual labor and they all have ADS, so we will surely make a mistake in above process. When you select the wrong profile, you often realize very late… And then we have to do it again. you get my point
Guys, build automation is ALPHA and OMEGA! It’s the first thing, that has to be done! All programmers get very frustrated if they have to do tedious and uneeded work cycles over and over again. We hate that. We really, really hate that very much to the point that we get angry.
Corona is about Productivity. The build screen is the opposite of productivity. It looks, feels and behaves clumsy. Please, if you won’t support scripting in the build process, then make saveable configurations for that window or something. It can’t be hard for hot shot opengl programmers like you ansca ppl.
Everyone plus 1 now please [import]uid: 169740 topic_id: 37155 reply_id: 67155[/import]