Cube Timers For Mac's... ????

[AvGalen]

It actually took me a while to get CCT to work on my Mac.

The thing that worked for me was going to "Java Preferences" (Spotlight it) and dragging "Java SE 6" to the top of the application versions.

On Windows I get annoyed that this happens:
1) I install Java 1.6.0 a year or so ago
2) Every once in a while it "updates" itself to 1.6.1, 1.6.2, ...., 1.6.10
3) Those updates turn out to not be updates at all. All previous versions are still there, sucking up more diskspace than a clean install of XP SP3

but at least the latest version of Java makes itself the default after installing.
Is the process of Java-on-Mac even worse than this Java-on-Windows behavior?

 

[tim]

It actually took me a while to get CCT to work on my Mac.

The thing that worked for me was going to "Java Preferences" (Spotlight it) and dragging "Java SE 6" to the top of the application versions.

On Windows I get annoyed that this happens:
1) I install Java 1.6.0 a year or so ago
2) Every once in a while it "updates" itself to 1.6.1, 1.6.2, ...., 1.6.10
3) Those updates turn out to not be updates at all. All previous versions are still there, sucking up more diskspace than a clean install of XP SP3

but at least the latest version of Java makes itself the default after installing.
Is the process of Java-on-Mac even worse than this Java-on-Windows behavior?

Nope . Mac OS X just keeps the major releases (like 1.5, 1.6, ...) and all versions in between are links to the newest 1.x release. Oh, and there's even a suitable place for the Java RE and other frameworks. Java installs itself into "Program Files" on Windows, doesn't it?

 

[AvGalen]

It actually took me a while to get CCT to work on my Mac.

The thing that worked for me was going to "Java Preferences" (Spotlight it) and dragging "Java SE 6" to the top of the application versions.

On Windows I get annoyed that this happens:
1) I install Java 1.6.0 a year or so ago
2) Every once in a while it "updates" itself to 1.6.1, 1.6.2, ...., 1.6.10
3) Those updates turn out to not be updates at all. All previous versions are still there, sucking up more diskspace than a clean install of XP SP3

but at least the latest version of Java makes itself the default after installing.
Is the process of Java-on-Mac even worse than this Java-on-Windows behavior?

Nope . Mac OS X just keeps the major releases (like 1.5, 1.6, ...) and all versions in between are links to the newest 1.x release. Oh, and there's even a suitable place for the Java RE and other frameworks. Java installs itself into "Program Files" on Windows, doesn't it?

From that picture it looks like 1.4.1 is a link (to 1.4.0?) but 1.4.2 seems to be another normal folder. I just don't understand why Java isn't nicely backwards compatible. I have seen this versioning-issue causing problems sooooooooo many times before

And it is not OSX or Windows that determines if the previous version is kept. That is up to the installer-program to decide.

And by default Java installs in Program Files (Actually in the environment variable ProgramFiles), but you can change that in the installer

 

[tim]

1.4 and 1.4.1 are links to 1.4.2 (the newest 1.4.x release).

Actually Java is nicely backwards compatible, isn't it? And that's one of the only things (besides the native/non-native types (int/Integer)) i don't like about Java. Backwards compatibility is bad for any programming language/framework.

 

[AvGalen]

1.4 and 1.4.1 are links to 1.4.2 (the newest 1.4.x release).

Actually Java is nicely backwards compatible, isn't it? And that's one of the only things (besides the native/non-native types (int/Integer)) i don't like about Java. Backwards compatibility is bad for any programming language/framework.

Thanks for clearing that up Tim. I looked at the version-linking the wrong way

But in general I don't like things that are NOT backwards compatible. I like having 1 "latest and greatest" version that can handle all the old stuff as well. With Java I have seen to many applications that require a minimum AND a maximum version of the JRE. That means that I need to have several version of the JRE on a machine and tell applications which version it should use (NOT userfriendly).
It also means that if a bug is found (in the latest-and-greatest) that has been present in previous versions as well, I need to update several JRE's to fix 1 bug. I think every programmer agrees that working/fixing 1 codebase is enough work and that most end-users shouldn't have to know about program-runtime-coupling

 

[bamman1108]

I just go on cubemania.org since I have a PPC Mac. Haven't bothered with JNetCube at all though.