Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The way applets work in Netbeans is annoying to me. The suggested usage from the help is to run the applet as you indicate you did (Run File). NetBeans will produce an HTML file under build/classes that references the applet. You then copy the HTML file to src where your class is. You can then tweak the HTML and in subsequent runs NetBeans will use your HTML file instead of generating it. Every time you run the file NetBeans opens the applet viewer program that ships with Java. You cannot control any of the arguments passed to the applet viewer. It ignores the run-time parameters you configure in the project. To change the parameters passed to the applet you must edit the HTML file manually.</p> <p>A better way is to use the AppletWindow classes created over at the BlueJ project. It lets you host an applet on a JFrame, which means you can make a small standalone Swing app which calls your applet. The program then has a main method, you can launch an extra Swing window with buttons and text controls to simulate javascript calls to the applet and you can tweak the attributes that get passed to the applet at runtime. It's very nice for trying out new things in your code.</p> <p>Links:</p> <ul> <li><a href="http://www.bluej.org/resources/classes/appletwn.jar" rel="nofollow noreferrer">AppletWindow Download</a>: This jar contains the compiled .class files and the source.</li> <li><a href="http://www.bluej.org/resources/classes.html" rel="nofollow noreferrer">More info about BlueJ and other resources</a></li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload