Why use a JApplet instead of just the Class code?

So basically I'm looking back to the HTML class I took about year ago. One section we used a Java class that would display text like a rolling credits. So I want to know what exactly are the main differences with this? I realized that when I was making my class that I used a regular JFrame Form, but realized that there is a JApplet and Form as well. The JApplet code says Creates a new JFC (Swing) applet. An applet is a Java class that can run in any Java-enabled browser. Which I knew, and this is what I will do, but I'm curious if there is any big difference? I know Applets have things like signing certifications and such, but what else?

Thanks,

~JO

As opposed to what?

It almost sounds like you expect to be able to run Java in the browser without an Applet, and that's not going to happen.

Jay Orsaw wrote:So basically I'm looking back to the HTML class I took about year ago. One section we used a Java class that would display text like a rolling credits.

Are you sure that wasn't Javascript?

Paul Clapham wrote:

Jay Orsaw wrote:So basically I'm looking back to the HTML class I took about year ago. One section we used a Java class that would display text like a rolling credits.

Are you sure that wasn't Javascript?

I tried to attached the CreditRoll.class file, but The Ranch says they don't like .class or .zip..... Apparently it opens up as JNLP and says it's an applet in the console... I cannot open the file in my IDE it says "no sources."

I guess that answers my question about it having to be an applet. Didn't really make much sense to me at all.

@Bear not at all, I was curious exactly what was going on in the CreditRoll.class.

I couldn't edit, so sorry for the double post. I forgot to ask how exactly was this code created that I couldn't open it "without it's sources?" Is that the "classLoader" as mentioned in the Applet FAQ?