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.
Summary: | Can't run applets with custom launcher files | ||
---|---|---|---|
Product: | obsolete | Reporter: | andreas_e <andreas_e> |
Component: | applet | Assignee: | Petr Jiricka <pjiricka> |
Status: | NEW --- | ||
Severity: | blocker | ||
Priority: | P2 | ||
Version: | 5.x | ||
Hardware: | PC | ||
OS: | Windows ME/2000 | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
andreas_e
2006-02-23 13:53:56 UTC
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? |