Cross Versions folder

[djphaidon]

Due to issues with 2.3.0 that I have had, I reverted back to 2.2. I realized when I did, that one of the things that Traktor does right is always keeps the previous program, settings, and collection in a folder so that if you need to revert to the previous. This also helps if you want to test out the upgrade, but can't afford to swap without extensive testing first.

I would like to suggest that a few changes be made when upgrading to a new version.

First, put all Cross versions in a folder called MixVibes under applications, or Program files

Second, Name the program Cross 2.3.0, or 2.3.2 as the program name, and have separate, isolated folders for each iteration.

Third, Have the Collection and the settings file be grouped in a folder that can be location assignable, like the collection files currently are, and have the folder keep the name of the Program version number.
eg. I would have a folder called ...( { } is your folders )
Dropbox/DJ Phaidon/Settings/Mixvibes/ {Cross 2.2.0}/settings.file
Dropbox/DJ Phaidon/Settings/Mixvibes/ {Cross 2.2.0}/collection.file
Dropbox/DJ Phaidon/Settings/Mixvibes/ {Cross 2.3.0}/settings.file
Dropbox/DJ Phaidon/Settings/Mixvibes/ {Cross 2.3.0}/collection.file

Also, when updating to a new version, have a prompt to ask if you would like to import the previous versions settings.

This would also have to make a change to the current way you store settings in the user/library/Cross/settings.file, because at current, the version you run is always using the previous versions settings when you update.

[Support@MixVibes]

First, put all Cross versions in a folder called MixVibes under applications, or Program files

Already the case since early Cross versions.

cross_updates.JPG

Second, Name the program Cross 2.3.0, or 2.3.2 as the program name, and have separate, isolated folders for each iteration.

Because they're isolated by folders, they can have the same name : Cross.exe. But you can rename if needed.
If they were in a common folder then it would have been a need.

Third, Have the Collection and the settings file be grouped in a folder that can be location assignable, like the collection files currently are, and have the folder keep the name of the Program version number.
eg. I would have a folder called ...( { } is your folders )
Dropbox/DJ Phaidon/Settings/MixVibes/ {Cross 2.2.0}/settings.file
Dropbox/DJ Phaidon/Settings/MixVibes/ {Cross 2.2.0}/collection.file
Dropbox/DJ Phaidon/Settings/MixVibes/ {Cross 2.3.0}/settings.file
Dropbox/DJ Phaidon/Settings/MixVibes/ {Cross 2.3.0}/collection.file

I like this one...

Also, when updating to a new version, have a prompt to ask if you would like to import the previous versions settings.

Can be complicated sometimes, that why we end up with corrupted ones (always importing/re-reading previous one).

This would also have to make a change to the current way you store settings in the user/library/Cross/settings.file, because at current, the version you run is always using the previous versions settings when you update.

True, and this lead to too many true false bugs/crashes.

[djphaidon]

True with windows installations, but not with OSX. OSX installs one over the other in the applications folder, so that anytime you update, you are basically replacing the last version folder that you were running, and replacing it with a newer version folder. It would be awesome to have a folder setup like the windows version on OSX, especially if you could isolate the collections and the settings files.

Since you guys are constantly updating the database, it makes sense that it would be an issue between versions, especially backwards. Maybe have a way to isolate the older version from the newer after import. Tag them somehow so that a 2.2.0 collection and settings file will only work on a 2.2.0 install, but can be updated by 2.3.0 to a 2.3.0 collection and settings file which won't update backwards, only forwards maybe?

2.4.0 alpha... Mixvibes is boss! You don't know how happy it makes me to see as much work done to a program in a timely manner.

[Support@MixVibes]

True with windows installations, but not with OSX. OSX installs one over the other in the applications folder, so that anytime you update, you are basically replacing the last version folder that you were running, and replacing it with a newer version folder. It would be awesome to have a folder setup like the windows version on OSX, especially if you could isolate the collections and the settings files.

I'm not sure Apple is allowing this, I will ask the dev. Even if they allow this, it is not the working flow/mood into the mac world (same for the other competitors).
For myself, I simply rename the *.app to the name version so I can have them all on the same computer.

Since you guys are constantly updating the database, it makes sense that it would be an issue between versions, especially backwards.

Agree.

Maybe have a way to isolate the older version from the newer after import. Tag them somehow so that a 2.2.0 collection and settings file will only work on a 2.2.0 install, but can be updated by 2.3.0 to a 2.3.0 collection and settings file which won't update backwards, only forwards maybe?

Will see with the guy in touch with the Apple policies (sandboxing, Appstore and so on...).

2.4.0 alpha... MixVibes is boss! You don't know how happy it makes me to see as much work done to a program in a timely manner.

There is a 2.3.1 with some fixes, you might give it a look to see how it runs for you. I have seen some improvement for big collection (nearly 90k on mine).