OK,

After further review, I think both LWJGL and JoGL
may pop up security dialogs in some cases.  LWJGL
pops one up all of the time, and JoGL seems to pop
one up on some versions of Java and not others?

Some interesting behavior, but it is best to have
that pop up NOT show up, when possible in my
opinion.  I'm for any kind of mitigation of that.
There are other reasons that I would want to
use JoGL as well. Java2D integration is one.  Basically what the
JoGL Java2D integration allows you to do is to
write a game using jPCT, and then implement your
user interface in Java2D using the overlay.  This is
done at full hardware speed, and you have access
to all of Java's Font technology.  You can even
write the overlay with JavaFX.  So I still want
the JoGL integration with jPCT.

I don't know how others feel.

I don't know now.  EgonOlsen has me a little unsure of myself now.
I know that the JoGL jars are signed by sun.  What I am not sure
of is why Egon is getting a security pop up.  Maybe Sun does not
ship that certificate by default after all?

I'm still looking.  It would be funny if both Egon and I were running
in a controlled environment.  His making him think LWJGL had no
pop up and mine making me think that JoGL had no pop up.

I'm still digging on this.

The JoGL applet probably does this because somewhere along the
way, just as you accepted the Oddlabs certificate.  You probably
deleted your Sun certificate.  More probably you deleted ALL of
your certificates at some point.

The other option is that you have an old JRE.  I don't remember
the release when they started including the certificate that is used
to sign the jsr-231 jars.

Let me try to look it up.

Come to think of it . . .

It would be much simpler to just delete the certificate
from Oddlabs.  You will see it in the list in the Java
control panel certificate store.  This certificate does
not ship with Java by default, so users have to accept
it for it to be put in the store.

So just delete the Oddlabs certificate and then try
the two applets that I pointed out.

The LWJGL jars are properly signed, but with a certificate from the Oddlabs org.
You have probably at some point already accepted this certificate.  New users
coming to a jPCT site in the field don't have that certificate accepted, and will
get a security warning.  Notice the LWJGL documentation says:

"Upon release of LWJGL 1.0, we will provide proper signed packages so that
any user can run applets without having to invest in a CERTIFICATE."

The certificate is what is used to sign the jar.  The security warning is what
is used to prompt the user to accept the certificate as valid.

What they mean is that developers can write applets and run them without
having to buy a certificate to sign their jars.  What they leave out is that you
will need to accept their certificate on your machine.  This is not a problem for
most developers, but for users in the field it is an issue.

One way that I use to test my applets is to make a trip to the Apple Store.  When
running under JoGL, no certificate is prompted for, when running under LWJGL,
a certificate is prompted for.

One way to see what I am saying would be for you to remove all of your
certificates, except the default Sun Microsystems certificates.  These
can be removed from the certificate store via
the java control panel.

Your machine should now have only the certificates that a fresh install of
Java will have.  So now run the JoGL applet demo at:

https://jogl-demos.dev.java.net/applettest.html

After that run the LWJGL applet demo at:

http://lwjgl.org/applet


You will see that only the LWJGL applet will prompt for a security clearance.

Hello All,

I know that I am new here, but I have been using jPCT for
quite some time.  It is a great little engine.  Thanks to you
who make it possible.

I am writing because I use jPCT in a bit of a different fashion
than everyone else here.  I use JoGL to talk to OpenGL as
opposed to LWJGL.  I do this by supporting a JoGL shim that
masquerades as LWJGL.

My question is, is there a way that JoGL can get supported
officially?  Getting all of the shader stuff working when the
118 beta was released was a bit of a pain.  I am thinking
that as you go forward you will have stuff that I want to
work with via OpenGL as well.

The reason I use JoGL is because it makes my applets work
in a browser without a security warning.  This actually
makes users a good deal more comfortable with my product.

I am not a lazy person.  If jPCT were open source I would
create the interfaces for pluggable GL layers myself.  I have
been trying to just shadow your development, and not
burden you with requests like an ingrate.  I know how it
feels when people do that.  But now I think I am at a point
where I have to ask, or we could get wildly out of sync.

The other option is for me to do a rewrite of the core
engine blind.  This would mean that, initially anyway, I would
not have software rendering.  Frankly, there are enough
java game engines floating around out there.  We don't need
more in my opinion.

For these reasons I am writing to ask that you support
JoGL officially.  I will even write it for you if you like.  I just
would like you to put it in your engine.

By way of information, my jPCT shadow project is tracking
the main jPCT for the purposes of supporting two pieces of
functionality.  The first is a JoGL OpenGL layer.  The second
is a JBullet real time physics engine.  Right now they are
both integrated up to version 1.18 beta.  I would wager that
a lot of your users are all shadowing the main jPCT releases
in a similar fashion.  So there are probably a handful of
people out there who are all supporting their own JoGL
shim to use jPCT with JoGL.  I think this is wasted effort.

Please let me know if you think that you would be willing
to support JoGL.  If not, I thank you any way for everything
you have contributed to the gaming community so far.