Comments on: JOGL: Applets (part 1)

By: Peter

Peter — Fri, 07 Aug 2009 09:57:07 +0000

Me again, Just interested in progress on “JOGL: Applets (part 2)”

Actually I’m just looking for a complete example using the above deployement descriptors, applet source code, what jars need to be where, what jvm flags are required, maybe newt based? Also I’m pretty useless around applets, but assuming I make use of the PersistenceService from jnlp, will my app run jogl without a certificate ‘requesting unrestricted access’. I have it signed currently because I cach some objects locally and also write a client side logfile and prefferences. Sounds like the above combination combined with applet/jnlp combination should eliminate that? or are there other sandbox restrictions that might trip a jogl app up?

PS Great to see you are so active on JOGL these days! great job!

By: Peter

Peter — Mon, 06 Jul 2009 19:18:44 +0000

Sounds Very interesting! The NEWT only plugin sounds really interesting, especially if it’s running on mac

By: Sven Gothel

Sven Gothel — Sun, 05 Jul 2009 14:13:23 +0000

@Peter: I know .. 1 tab 4 all
Fullscreen applets ? Well, I don’t want to speak for AWT here ,
but I will show a NEWT-AWT applet demo, and later, after finishing the AWT-Less plugin feature,
we don’t even need to use AWT anymore.

By: Peter

Peter — Sun, 05 Jul 2009 12:34:22 +0000

Nice that you are considering the OSX cases The applet/tab bug you mentioned is a bit worse under firefox since the applet in 1 tab draws over the screen real estate in all tabs and even the address/bookmarks toolbar.

Anyway, with that aside. This dual approach looks quite interesting. Will this support easy switching into full screen mode even from the applet fallback?

By: Sven Gothel

Sven Gothel — Sat, 04 Jul 2009 21:08:34 +0000

I don’t care much about the download case (empty cache), since it takes tame anyways.
The restart case is important IMHO and that’s where it is faster as well,
as you said check-date, verify, ..

By: michael

michael — Sat, 04 Jul 2009 14:13:05 +0000

btw. tested it with a clean cache and its noticeable faster now.

By: michael

michael — Sat, 04 Jul 2009 14:09:26 +0000

wow that was fast. thanks!

By: Sven Gothel

Sven Gothel — Sat, 04 Jul 2009 12:23:46 +0000

Ok .. changed the applet tags, so only one JVM is started, added a note as well.
Also changed the jnlp files ‘jogl-all-awt.jnlp’ and ‘nativewindow-awt.jnlp’
to use the *.all.jar archives and not to load more jogl/nativewindow extensions.

By: mbien

mbien — Sat, 04 Jul 2009 10:41:06 +0000

thank you for the update. First startup experience is not as good as it could be since webstart scales not very well with increasing jar count. It is a sequential (and not parallel) download -> verify jar -> download process which slows everything down (already filed an bug at least one year ago but i can’t find it in the db). Jogl1 had 2 jars, Jogl2 has a lot more

Preventing two jvms from boot would be cool too (sometimes it worked for me when i duplicated all jvm args in the applet tag), but i fear this is an feature rather than a bug…
(tested on ubuntu 32, ping me if you need more info)