This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Yes, that is an issue for me. Certainly I can just work in a parallel way and always make alternate use of IE/Firefox and NB, but that's not what I want. I followed the documentation applets => running in EVERY detail, but couldn't get anything but the standard appletviewer appearing with my applet. My custom HTML file was completely disregarded. Yes, I did copy it to src folder. Yes, I also obeyed to the rule to never modify a launcher file in the build directory. Yes, it was used when I right-clicked the .java file and the IDE copied MY file to build directory. But I still was not able to either see the page title nor the text BELOW the applet. It seems this is just ignored, although the documentation definitely states that custom launcher files are supported. However, you cannot use the appletviewer then.
No, appletviewer does not support this, it just shows the applet, not the surrounding text on the page. Please use the "View" action on the launcher file in the build directory to see the page in the web browser.
Thanks for the answer, I appreciate your concern a lot. So I will consider this a workaround, since the build directory is actually for building, as the name suggests. =) Well, so I have following suggestion (as I've seen you'd marked TM as 5.5): NetBeans could detect _applet_ code and when the user uses 'run' on the .java file (right-click), the launcher file is run with the applet inside, _considering_ the fact that the user might have a custom launcher file. This is for applet mode and only this. Non-applet .java files SHOULD be run using appletviewer, but this should not be default. my 2c
... should not be default _for applets_. Sorry, forgot.
Ok, changing to ENHANCEMENT. I must say I still don't understand: "Non-applet .java files SHOULD be run using appletviewer". I think Non-applet .java files should be run using the "java" command. Appletviewer is _only_ for applets. And even with your suggestion, I don't think it solves your issue. You need the applet to be run in *browser*, not appletviewer.
OK, you have a point, sorry. I must have confused something (too much JS programming atm :)) ... sure thing, java applications which are not applets (*.java) use java _interpreter_, of course. I stand corrected.
AH ... WAIT. I'm "in" again, and trying the solution you had given. Unfortunately the 'View' workaround in Files directory turned out to break with standard settings, i. e. classes assumed in classes folder. CODEBASE in launcher file must be specified "../classes" not "classes" ( file not found ). No go without manually editing the html file. You see? Those .html files in build directory are not supposed to be launched.
Worked for me. Did you try to open the Java console in the browser to see the error?