Skip to main content

Proposed Java 3D 1.4 API Changes

55 replies [Last post]

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
kcr
Offline
Joined: 2004-03-17

> What about the minimal JOAL sound implementation you talked about,
> should that not be in the list?...please :)

The JOAL sound implementation (JOALMixer) is independent of any particular release of Java 3D, since we plan to put it in the j3d-incubator project. As stated earlier, this will be an incomplete prototype (almost certainly a [b]*very*[/b] incomplete prototype). Unless someone outside of Sun picks the project up and takes it to completion, it will not really be useful to anyone. The version we check into the incubator will be no more functional than JavaSoundMixer is today, the difference being that the JOALMixer will be a good framework from which a functional version could be developed.

Btw, since we spent more time on fixing 1.3.2 bugs than anticipated, we aren't likely to have any time to spend on the JOAL port until after JavaOne, which is in late June this year.

-- Kevin

jeen71
Offline
Joined: 2005-01-10

In current implementation, some of the attributes of Canvas3D are getting calculated at every frame. Isn't it overkill?
Shouldn't we rather do calculation of some of these, especially the physicalwidth and height of the Canvas3D at every viewPlatform change rather than at every frame?

http://www.javadesktop.org/forums/thread.jspa?threadID=8211&tstart=30

kcr
Offline
Joined: 2004-03-17

> In current implementation, some of the attributes of Canvas3D are getting calculated at every frame.
> Isn't it overkill?

I put this on the list of possible 1.4 improvements that do not require API changes, although it isn't as easy as it sounds. We already avoid the really expensive processing if nothing changes. What we don't do is track changes and only recompute dependent state for those variables whose inputs have changed. The dependency graph would be non-trivial, and very error prone, so we decided not to do it early on. This may make more sense for a subsequent release, however.

-- Kevin

scotthong
Offline
Joined: 2006-05-05

Light weight JCanvas3D that is similar to JGLCanvas in JOGL.
Maybe , a tripple buffered JGLCanvas! PBuffer for 3D
rendering, a light weight back buffer to mix 2D drawing with
great performance and the front buffer to display the
rendered image.

-- Scott

kcr
Offline
Joined: 2004-03-17

> Light weight JCanvas3D that is similar to JGLCanvas in JOGL.

Interesting idea. We'll put it on the "medium priority" list.

-- Kevin