Build Numbers Appended to Recent Daily Build Folders

Solar2D Daily Builds and Public Releases
#1

Hello!

This is certainly not critical, but I was wondering why the decision was made to append build numbers to recent daily build folders for OS X (for example, today’s daily build comes in a folder called “CoronaSDK-2602”). Maybe it’s just me, but I liked the simplicity of dragging the latest daily build into my Applications folder and knowing that it would overwrite the previous version without clogging my Applications folder with numerous daily builds of Corona. Under this new system, I need to copy the folder from the DMG to my hard drive, rename the folder, and then move it into the Applications folder. Not a major issue, but those extra steps are an irritant, at least from my perspective.

I can see the logic in appending the build number, to keep things organized if you want to host several builds on one machine, but if I may add my own two cents, I’d prefer to see a return to having daily build folders simply called “CoronaSDK.” I understand if I’m overruled on that, but thought I’d at least make the case for it.

Thanks!

#2

Hi @schroederapps,

This decision was made because, at least in our estimation, most Corona users prefer to have a few versions of Corona SDK installed, or at least the most recent public/stable release plus a recent daily build. Personally, I keep a dedicated “Corona” folder within my “Applications” folder, and inside that I keep 3-4 different builds installed at any time.

We understand that this decision might not be ideal for everybody, so if you (or anybody else) feels strongly about it, let us know and we may reconsider.

Personally, I think you should have at least the last public/stable release installed, plus a recent daily. This is good practice for testing IMHO.

Thanks,

Brent

#3

You are right, many of us do prefer to a few versions of Corona SDK installed.

Why do you think we haven’t all figured out how to solve this problem in our own way? As the old saying goes, if it aint broke don’t fix it.

#4

Hi Brent;

I strongly prefer the old method. I think it takes about 20 seconds on my Mac to overwrite one install with another and it won’t have me wondering if I launched my authoring session in the wrong version (when 2 or more were installed).

As a long-time Pro user, I have paid no attention to “public releases”. Rather, I have authored through a series of Daily Builds grabbing maybe one a month over the years. If anything messes up (which has only happened once in the years), I drop back a month. This way, I feel like I am usually authoring with builds that contain almost all of the most recent improvements and features.

I agree with elbowroom. It wasn’t broke. :slight_smile:

Steve

#5

Hi @schroederapps,

This decision was made because, at least in our estimation, most Corona users prefer to have a few versions of Corona SDK installed, or at least the most recent public/stable release plus a recent daily build. Personally, I keep a dedicated “Corona” folder within my “Applications” folder, and inside that I keep 3-4 different builds installed at any time.

We understand that this decision might not be ideal for everybody, so if you (or anybody else) feels strongly about it, let us know and we may reconsider.

Personally, I think you should have at least the last public/stable release installed, plus a recent daily. This is good practice for testing IMHO.

Thanks,

Brent

#6

You are right, many of us do prefer to a few versions of Corona SDK installed.

Why do you think we haven’t all figured out how to solve this problem in our own way? As the old saying goes, if it aint broke don’t fix it.

#7

Hi Brent;

I strongly prefer the old method. I think it takes about 20 seconds on my Mac to overwrite one install with another and it won’t have me wondering if I launched my authoring session in the wrong version (when 2 or more were installed).

As a long-time Pro user, I have paid no attention to “public releases”. Rather, I have authored through a series of Daily Builds grabbing maybe one a month over the years. If anything messes up (which has only happened once in the years), I drop back a month. This way, I feel like I am usually authoring with builds that contain almost all of the most recent improvements and features.

I agree with elbowroom. It wasn’t broke. :slight_smile:

Steve