Skip to main content

deprecated uses in libs

8 replies [Last post]
pepe
Offline
Joined: 2003-06-10
Points: 0

Recompiling core and core-utils shows that there are lots of uses of deprecated methods and members.
Shouldn't those uses be cleaned? I feel so, but maybe there are reasons beyond my understanding that forbid that.. Any hint?

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
pepe
Offline
Joined: 2003-06-10
Points: 0

oh, i was certainly not talking about removing anything deprecated, but more making sure the libs don't use deprecated parts of themselves.
They actually do 'quite a bit'.

Kevin Rushforth

On Tue, 2004-07-13 at 12:50, java3d-interest@javadesktop.org wrote:
> oh, i was certainly not talking about removing anything deprecated,
> but more making sure the libs don't use deprecated parts of
> themselves.

This is a good idea for the utils classes, although in some instances,
such as the scene graph I/O state classes, the use of deprecated methods
is just mirroring public API. The picking behaviors and geometry info
classes are the worst offenders; they could be cleaned up pretty easily.

-- Kevin

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@java3d.dev.java.net
For additional commands, e-mail: interest-help@java3d.dev.java.net

pepe
Offline
Joined: 2003-06-10
Points: 0

> they could be cleaned up pretty easily.
okay, doing that.

Kevin Rushforth

[att1.html]

pepe
Offline
Joined: 2003-06-10
Points: 0

> [att1.html]

sorry?

kcr
Offline
Joined: 2004-03-17
Points: 0

> > [att1.html]
>
> sorry?

I'm as puzzled as you are, since I didn't send that (at least not explicitly). It's possibly the result of a very clever virus/spammer. Either that or a buggy version of Evolution.

-- Kevin

Kevin Rushforth

We can't remove any deprecated public methods from the javax.media.j3d
package (at least not without a JSR for a new API revision, and even
then it's frowned upon). Given this, there will always be a certain
number of deprecation warnings when compiling the core package.

As for the utils, these should probably be cleaned up, although removing
any deprecated public methods will need to wait until 1.4. We haven't
had the time to do this, so if someone wants to volunteer we would be
happy to discuss it.

-- Kevin

On Tue, 2004-07-13 at 10:18, java3d-interest@javadesktop.org wrote:
> Recompiling core and core-utils shows that there are lots of uses of
> deprecated methods and members.
> Shouldn't those uses be cleaned? I feel so, but maybe there are
> reasons beyond my understanding that forbid that.. Any hint?
> ---
> [Message sent by forum member 'pepe' (frederic barachant)]
>
> http://www.javadesktop.org/forums/thread.jspa?messageID=16807???
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: interest-unsubscribe@java3d.dev.java.net
> For additional commands, e-mail: interest-help@java3d.dev.java.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@java3d.dev.java.net
For additional commands, e-mail: interest-help@java3d.dev.java.net

herkules
Offline
Joined: 2003-06-12
Points: 0

I volunteer for everything around Java3D :)