build automation, build interface

Solar2D General Questions/Discussion
#1

Hi all,

I know there is plenty of threads about this which is even more reason to open another one:)

at
our company we make a whole lot of small games. So I often have to
build different games games with different profiles for different
devices:

Like many programmers, I am very bad at manual labor, especially when it involves concentration tasks:)

Imagine
you have say 10 projects you are working on, each for android and ios. I
often switch between projects, build one, adjust another build it
again, switch, you get my point…So if I build a corona project, I have
to adjust the destination folder and the profile manually. Every time!
Our Programs are often so trivial that building the projects is the most
challenging part where a lot of time gets wasted.

It really would be great if building with corona was a only a little bit less pain.

If
Ansca will only support full scripted build automation for pro
subscribers (which is simply not affordable for many), it could at least
improve it’s point-and-click interface.

For
example: ATM I have around 30 provisioning profiles to work with. The
list in the simulator of these profiles is the opposite of sorted. It
even looks like the interface encorporates a very elaborate system which
unsorts perfectly named profiles :wink:

Another thing,
that would help a lot and wouldn’t take much time to implement would be
remembering the profile and destination folder per project (not only
the last profile/destfolder). When you switch projects this is a major
source of wtf-moments.

Coding in Coron is 10 times faster, but building with Corona, well…

So everybody pls +1 here

#2

I thought this before. Even if it was something we had to do manually in the build.settings file first time round, it would be much easier. 

Perhaps we could write the details of a debug + release prov profile for each project, and the drop down menu on the build screen would only show those ones. Likewise, if we could specify the app name and package name in the build.setttings file beforehand that would be helpful. If it could just read the value from build.settings then when I rename the folder etc, it won’t change the names in the build window (I quite often include the date in my folder name). 

I would say it is only a minor problem, but a very repetitive one.

#3

I thought this before. Even if it was something we had to do manually in the build.settings file first time round, it would be much easier. 

Perhaps we could write the details of a debug + release prov profile for each project, and the drop down menu on the build screen would only show those ones. Likewise, if we could specify the app name and package name in the build.setttings file beforehand that would be helpful. If it could just read the value from build.settings then when I rename the folder etc, it won’t change the names in the build window (I quite often include the date in my folder name). 

I would say it is only a minor problem, but a very repetitive one.