Skip to main content

3D applet deployment -- download extension

11 replies [Last post]
senore100
Offline
Joined: 2007-05-10
Points: 0

Hi, I need to deploy an applet using Java3D package. Trying to avoid the installation hassle (on the client side), I want to put the three packages available on the server (j3dcore.jar, j3dutils.jar, vecmath.jar), and then add the class path of these jar files in the manifest of the applet jar file. It's not working. now I start to wonder if such an approach is feasible or not. Can anyone give me some suggestions? Thanks a lot.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
tmilard
Offline
Joined: 2004-03-25
Points: 0

Hello agin.
I just stumbled into a very nice and goodlooking "3D Web centric" game.
http://www.powerchallenge.com/

It is made with java. I do not think it in in java3D.....
It does not use JWS (java Web start) but I think "java plug in".

Anyway the installation process is quite visual and simple.

For example the download process ("% dowloaded yet", .....) is display inside the html page. I do find it cool.

Voilà, that is all. Just a positive java 3D link that shows (perhaps) a good way to have a simple install process.

Readers, If you have comments on the install processs ingeneral please fell free to do it.
I am looking forward to hear more about this issue.
Thierry

jonks
Offline
Joined: 2004-12-01
Points: 0

The end result on the installation is that "Powerfootball-OpenGL.exe" is executed.
...So it looks like they are using java to install native binaries.

tmilard
Offline
Joined: 2004-03-25
Points: 0

citation:
[i]"Yes, we understand for some applications JWS isn't the answer. Making Java 3D applet ready is high on our list for Java 3D 1.6, but we are now considering pulling it in for Java 3D 1.5.1 release. We believe we can get this done fairly soon, but we will need your help in testing it. We don't wish to push Java 3D 1.5.1 release out by too much.

See issue 257 : Java3D Applet Launcher enables the creation and deployment of applets using Java3D without requiring the applet to be signed or performing any manual installation of software on users' computers.

- Chien. [/i]"
________________
===>
1) Good news indeed ! I do happilly agree to test it because ... well I think having a 3D pane inside an html page (call it applet or something else) is ... modern. Like a minimum framework to do the "mashup" modern hype.

2) Yes it is true that having to sign .class of our application is for me an unusefull constraint. I understand some developpers want to sign for protection but for the java3d API it is just like a big sign "I do not welcome you new comer !". It is maybe my personnal fealing but I think priority is to [b]Open things[/b].
For an API like java3D, it is OK to have functions to protects things (like sign Applets)... but only as an option for cleaver and mature guys.
New comers just need simple things I believe.
And of course, let's not forget the baseline: "happy new comers make (with time ....) good java3D developpers. and of course more good java3D developpers gives a popular API"

3) I have always though that this "quite old bad sign policy" was JWS/Jnlp's team fault.
Is it not ?
May be I don't understand things. I am a bit lost: If you do an 257 issue, it does mean it will not use JWS/JNLP to install an Applet using java3D. Right ?
If so is it not possible "java web start" (JWS) team upgrades their "install API" to have
it work with unsign jars/.class ? I mean this (sign) issue is not specific to java3d .... No ?
(maybe I got it wrong)

5) issue 257 ==> "not performing a java3D software install on users' computers"
This would be wonderfull. A java/java3D Applet/Application would behave more like a Flash Application. Right ? This is a big issue because some (too rare I admit) people using my java3D program have a computer at work with "NO-RIGHT-to-install-software". Then call me to tell me "your bloody software does not work !". I those case I just keep a smile face and say ... "I am working on it....". But I do feel in those case Sun has hit me with a base ball bat in my back.... Ok, a small stick. ;)

6) Technically how can an applet "not need to install java3d API" ? Does it mean if I go back for the ten's time to the same applet, it installs again java3D API as if I had never come before ?
Or maybe you mean it is installed but without the need for admin right ?
I do need a few guideline for my personal technical culture.

Thanks
Thierry

Personal (awfull) poetic Conclusion:
- For my personal future, for java's future and ....after all for JAVA3D API, "bloody sign issue" and "dam install issue" are very old bullets-prisoners.
If tomorow they disaper, well maybe we are go back to first class web application ?

And as a java developper I sometime feel like I am a prisoner with one bit bullet called "havy weith application"leg having one smll bullet ig with the sign issue in a (perhaps nice) prison.
If golden I feel like that java developers like me one of the last things olderTomake it short : any tomake it

rkis my have
bcame bloody)the sign for Why, well I be
But I relling beli learning curve it would be very good to test it without signing.
our new programs too
minimum

jonks
Offline
Joined: 2004-12-01
Points: 0

webstart is only really good if you want you app to pop up in it's own window.
For me I could not do that because my applet requires interaction with the DOM it is embedded in.

A short while ago (2months perhaps) i put in a request for Java3D to install on demand like jogl does. To do this the Java3D jars need to be signed (prohibitively expensive for me!).
(jogl also has same the issue as j3d because it needs native libs)

You _can_ do this yourself though, there is an old tutorial out there somewhere that gives you step by step guidance for creating your own self-installing java3D.

senore100
Offline
Joined: 2007-05-10
Points: 0

Thanks very much for your reply. I assume that users will use my applet on Windows, so I've tried to put a copy of three .dll files on the server too. So far it's not working yet. Maybe I did something wrong in creating the jar file, because another little example that I created with Swing (no 3d at all) does not load properly either. I am looking into, and will try JNLP. I hope it does not come with a steep learning curve.

kazssym
Offline
Joined: 2007-04-18
Points: 0

I hope this information will help you.

http://java.sun.com/javase/6/docs/technotes/guides/plugin/developer_guid...

And I also wish [i]official[/i] installer JAR files for Java 3D would be provided.

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

Yes, we understand for some applications JWS isn't the answer. Making Java 3D applet ready is high on our list for Java 3D 1.6, but we are now considering pulling it in for Java 3D 1.5.1 release. We believe we can get this done fairly soon, but we will need your help in testing it. We don't wish to push Java 3D 1.5.1 release out by too much.

See issue 257 : Java3D Applet Launcher enables the creation and deployment of applets using Java3D without requiring the applet to be signed or performing any manual installation of software on users' computers.

- Chien.

russelleast
Offline
Joined: 2004-01-09
Points: 0

If it can be done without unduly pushing out the release time, it would certainly help us out!

senore100
Offline
Joined: 2007-05-10
Points: 0

Due to the time constraint that I have, I have decided to do it cheap and dirty. That is, I will force 3D package installed on users' local machines. As my application is only for students in the lab, it's doable. But if there's a better approach upcoming, it will be all the better! Thanks!

tmilard
Offline
Joined: 2004-03-25
Points: 0

May be you should think of using JWS (Java web start) JNLP (java Network lauching protocol) to have one easy client install.

The new version is better than it used to be.

And you use Sun' java3D automatic deployment for your 3D applet/application.

Thierry

aces
Offline
Joined: 2003-07-17
Points: 0

I agree with tmilard. Java3D uses native libs and this is not easy to deploy on client.
With JWS, it will put the right binaries (win, linux, etc), in right place, to run your Java3D.

See how to do it here:
https://j3d-webstart.dev.java.net/release/index.html

Pick the example.jnlp, edit it to follow your needs (jar filename, author, splash image, etc) and put it to run. There is no need to add any Java3d resource, just your application jar ;).