Java 1.5 yes - no?

[arne]

to finish this topic for now and always (ok 'till someone needs 1.6) - please vote
see also this thread for more information:
http://www.java-gaming.org/forums/index.php?topic=6054.0

[divzero]

No objections from me to switch to 1.5.

Will.

[kappa]

well if you haven’t already switched to 1.5 i’d say just skip straight to 1.6 much more improvements there!

[c_lilian]

I’d say no (I want to deploy on mac) excepted if someone can provide a 1.4 compatible jar file (I don’t know if retroweaver handles enums properly for example)

Lilian

[eMKa]

Supported 1.5 Language Features

* generics
* extended for loops
* static imports
* autoboxing/unboxing
* varargs
* enumerations
* annotations

http://retroweaver.sourceforge.net/documentation.html ;D ;D ;D ;D
Go 1.5 ! (And Mac still doesn’t have a 1.5 JVM shipped by default ??)
About 1.6 it’s not released yet…

[arne]

Ok guys, it looks like if nearly everybody is in favour of a switch to 1.5. So I think it should be no problem to switch

everybody who voted “not switch” please post why (as c_lilian did), so we can handle those issues. We don’t want anyone to be left behind!

[blahblahblahh]

[quote="<MagicSpark.org [ BlueSky ]>,post:5,topic:26944"]
Go 1.5 ! (And Mac still doesn’t have a 1.5 JVM shipped by default ??)
[/quote]
Shipped, but … for the machine’s I’ve seen so far, DISABLED by default. Argh!

[swpalmer]

@blahblahblahh

[quote="<MagicSpark.org [ BlueSky ]>,post:5,topic:26944"]
Go 1.5 ! (And Mac still doesn’t have a 1.5 JVM shipped by default ??)

Shipped, but … for the machine’s I’ve seen so far, DISABLED by default. Argh!
[/quote]
There is no case of Mac OS X where Java 5 is shipped but disabled.

You must be thinking of the command line where the path is still set to use Java 1.4 even when Java 5 is installed. That doesn’t effect Web Start or Application Bundles though, so it generally only matters to developers, and developers can just download the latest Java 5 DP in which case the command line gives you Java 5.
(You do have to be a bit careful how you construct your application bundles if you wish to fall back to Java 1.4, but use Java 5 if it is available… Apple did some dumb stuff with the version logic, but you can easily work around it for Web Start stuff. If you require Java 5, then it is not an issue.)

[eMKa]

So, no serious reason to stay 1.4, heh ?

[yvg]

Hi,

Well, I have no pbs switching to 1.5 syntax - I anyway use 1.5 in my app’s code. The major concern was (is) Mac support…

BTW, most of the new language features are just compiler features (OK, except annotations), and even when used generate extra garbage (varargs and autoboxing for example), so they should be used with great care.

Yuri

[eMKa]

Sooo I can change source-level to 1.5 in build.xml ? And include arne’s picking code in the toolkit ?

Annd about garbage, is it careful to use generics ^^ ?

[croft]

[quote="<MagicSpark.org [ BlueSky ]>,post:11,topic:26944"]
Sooo I can change source-level to 1.5 in build.xml ? And include arne’s picking code in the toolkit ?

Annd about garbage, is it careful to use generics ^^ ?
[/quote]
I plan to add the current version of the COLLADA Loader when Xith migrates to Java 5. Who is responsible for declaring when it is OK to do so?

[divzero]

@swpalmer

@blahblahblahh

[quote="<MagicSpark.org [ BlueSky ]>,post:5,topic:26944"]
Go 1.5 ! (And Mac still doesn’t have a 1.5 JVM shipped by default ??)

Shipped, but … for the machine’s I’ve seen so far, DISABLED by default. Argh!

There is no case of Mac OS X where Java 5 is shipped but disabled.

You must be thinking of the command line where the path is still set to use Java 1.4 even when Java 5 is installed. That doesn’t effect Web Start or Application Bundles though, so it generally only matters to developers, and developers can just download the latest Java 5 DP in which case the command line gives you Java 5.
(You do have to be a bit careful how you construct your application bundles if you wish to fall back to Java 1.4, but use Java 5 if it is available… Apple did some dumb stuff with the version logic, but you can easily work around it for Web Start stuff. If you require Java 5, then it is not an issue.)
[/quote]
And now version 5 is enabled by default from the command line with the latest update anyway: http://docs.info.apple.com/article.html?artnum=302983

Will.

[divzero]

@croft

[quote="<MagicSpark.org [ BlueSky ]>,post:11,topic:26944"]
Sooo I can change source-level to 1.5 in build.xml ? And include arne’s picking code in the toolkit ?

Annd about garbage, is it careful to use generics ^^ ?

I plan to add the current version of the COLLADA Loader when Xith migrates to Java 5. Who is responsible for declaring when it is OK to do so?
[/quote]
As there have been no objections and most stakeholders have replied to this thread in the positive, I think it would be fine to start including 1.5 code.

Cheers,

Will.

[eMKa]

That has been done. I forgot to include it in the first version of the release news, but Xith3D is now officially Java 1.5 The 0.7 release now have some packages in the toolkit (picking) that includes 1.5 code.

[eMKa]

@croft

[quote="<MagicSpark.org [ BlueSky ]>,post:11,topic:26944"]
Sooo I can change source-level to 1.5 in build.xml ? And include arne’s picking code in the toolkit ?

Annd about garbage, is it careful to use generics ^^ ?

I plan to add the current version of the COLLADA Loader when Xith migrates to Java 5. Who is responsible for declaring when it is OK to do so?
[/quote]
Please do.
You may want to include it in org.xith3d.loaders.collada

[croft]

[quote="<MagicSpark.org [ BlueSky ]>,post:16,topic:26944"]
You may want to include it in org.xith3d.loaders.collada
[/quote]
OK, I will start next week. Working on a demo this week.

I will probably put
the Whoola, Java 5, JAXB 1, COLLADA 1.4 implementation in package org.xith3d.loaders.collada.whoola1.*.

The Whoola, Java 5, JAXB 2, COLLADA 1.4 implementation will go in org.xith3d.loaders.collada.whoola2.*.

The Whoola, Java 5, JAXB 2, COLLADA 1.5 implementation will go in org.xith3d.loaders.collada.whoola3.*, etc.

[eMKa]

@croft

[quote="<MagicSpark.org [ BlueSky ]>,post:16,topic:26944"]
You may want to include it in org.xith3d.loaders.collada

OK, I will start next week. Working on a demo this week.

I will probably put
the Whoola, Java 5, JAXB 1, COLLADA 1.4 implementation in package org.xith3d.loaders.collada.whoola1.*.

The Whoola, Java 5, JAXB 2, COLLADA 1.4 implementation will go in org.xith3d.loaders.collada.whoola2.*.

The Whoola, Java 5, JAXB 2, COLLADA 1.5 implementation will go in org.xith3d.loaders.collada.whoola3., etc.
[/quote]
I think it’d be better to name like that :
org.xith3d.loaders.collada1.4-jaxb1.
org.xith3d.loaders.collada1.4.*
org.xith3d.loaders.collada1.5.*
But that’s only my opinion

[divzero]

[quote="<MagicSpark.org [ BlueSky ]>,post:18,topic:26944"]

@croft

[quote="<MagicSpark.org [ BlueSky ]>,post:16,topic:26944"]
You may want to include it in org.xith3d.loaders.collada

OK, I will start next week. Working on a demo this week.

I will probably put
the Whoola, Java 5, JAXB 1, COLLADA 1.4 implementation in package org.xith3d.loaders.collada.whoola1.*.

The Whoola, Java 5, JAXB 2, COLLADA 1.4 implementation will go in org.xith3d.loaders.collada.whoola2.*.

The Whoola, Java 5, JAXB 2, COLLADA 1.5 implementation will go in org.xith3d.loaders.collada.whoola3., etc.
[/quote]
I think it’d be better to name like that :
org.xith3d.loaders.collada1.4-jaxb1.
org.xith3d.loaders.collada1.4.*
org.xith3d.loaders.collada1.5.*
But that’s only my opinion
[/quote]
I agree - makes it clearer and reduces package name length. Just my 2c

Will.