In short, get the applet's context and tell it to show a different document: getAppletContext().showDocument(new URL("http://foo.com/whatever/blah.doc")). You can also provide a target frame string as in getAppletContext().showDocument(new URL("http://foo.com/whatever/blah.doc"), "target"). There are four special targets strings. Any other string will act as a named top-level window, if the frame doesn't exist.

Hmmm, also a good question. We fully expect we will have to split the post into manageable pages. We will monitor the usability of the page and the comment, and welcome your suggestions. If we find that splitting the post into 10 or 20 sub posts makes the project more usable or successful then we will do that. Once again, in the spirit of a volunteer community helping to make this a reality, we may need a volunteer to assist us in managing this process.

Ans: Yes, we can... but we should caution you that there are still a lot of old browsers out there that are not Java-enabled. Older AOL browsers, for example, have a devil of a time with Java. We are frankly looking forward to the time when the whole web is fully utilizing the interactive capabilities of the platform-independent language and world of Java. Ans: We have an excellent form script in our CGI Bin, written in perl.

If you click a button or link and nothing happens for an unusually long time, your browser is "hanging" or "freezing" (they're the same). This means that it is either waiting for information from a server or busy processing internally. At certain times of the day, traffic on the Internet can be very heavy, and you may have to wait a little bit longer for a response from our servers.

The LDAP Browser/Editor can be run as an applet within a web browser (Netscape Navigator or Microsoft Internet Explorer) using the Java Plugin. The Browser can be run either as a signed or unsigned applet. If the Browser is running as an unsigned applet it can only access the ldap servers on the server that the applet was downloaded from. If the Browser is running as a trusted signed applet it can access any ldap server on the network or the internet.

Author: John Zukowski (http://www.jguru.com/guru/viewbio.jsp?EID=7) Instead of specifying the CODE attribute of an <APPLET> tag, you use the OBJECT attribute, as in: <APPLET OBJECT=TheApplet.ser WIDTH=300 HEIGHT=300 > </APPLET> This allows you to preinitialize your applet to some saved state, instead of having to reinitialize your applet each time it is loaded.

It probably didn't copy correctly. Look at the code page again, and compare it to the HTML code in your page. Look carefully, and try to find where they are different. If you're using a visual HTML editor, you may have trouble pasting the code directly. I suggest using a plain text editor (like Notepad in Windows or Edit Pad) to insert the code, but Dreamweaver (in Show Code View mode), works just fine, too.

Author: Rob Edmondson (http://www.jguru.com/guru/viewbio.jsp?EID=35309) Question originally posed by NISHANT JAIN (http://www.jguru.com/guru/viewbio.jsp?EID=29836 The browser’s HTML interpreter reads the parameters from the APPLET tag. The relevant parameters used to load the applet’s class are CODE, CODEBASE, and ARCHIVE (CODEBASE and ARCHIVE are optional - OBJECT can be used instead of CODE). The CODE parameter holds the name of the applet’s class file.

Good "wiki" style suggests however that you start by editing some existing page, then insert a WikiPageName and save the page. The WikiPageName link will be displayed as a missing link (i.e. LikeThat?), and by following this link, you end up on the page creation interface. By following this practice, you tend to avoid OrphanedPages.

Author: Scott Stanchfield (http://www.jguru.com/guru/viewbio.jsp?EID=11) Question originally posed by Duane Vigue (http://www.jguru.com/guru/viewbio.jsp?EID=12977 If you add components to an Applet or JApplet, they will appear in the web page's assigned spot for the applet.

It is slow, and it is because of the way the Java applet has been designed. We are trying to create a modular applet, which is causing that the number of connections to load it to be 80-85% of the loading traffic for the page. Hopefully with some threading we will be able to at least show part of the applet while the rest loads in the background. I looked at the page from home, where I use a 486SX 33 MHz laptop, with only 8MB RAM, 250 MB HD, a 28.8 Kbps modem and a 9.

Browse to the intended location of the page, e.g. http://www.foowiki.org/index.php?title=New_page and click on the edit link.

You can easily edit the content of your site with EziEditor but you can’t easily add a new page in EziEditor, for example "Our Staff" in the main menu. The reason for this is that is a base CMS (Content Management System) and only allows basic interaction with your site because that's all you require. As a result changing content with easy editor is extremely easy and does not require any real technical experiance to use it.

The showDocument method of the AppletContext interface is overloaded - meaning that it can accept more than one parameter. It can accept a second parameter, which represents the name of the browser window that should display a page. will display the document in frame1. If there exists no window named frame1, then a brand new window will be created.

Browsers are starting to introduce support for this. Until they all have it, your best bet is to print a screendump. Using the browser to print the page may leave a blank where the applet is. Putting print support in the applet will print the applet only, not the rest of the browser page. See also Q5.2.

If you want to do this client-side-only, the applet can run JavaScript functions that are predefined in the containing, or parent window. For instance, if the applet detects a window closing event, you can call a JavaScript function to also close the parent window (This may not work on some systems, however). import netscape.javascript.*; try { JSObject win = JSObject.getWindow(this); win.eval("window.close()"); } catch (Exception e) {} Try telling the applet to call getAppletContext().

lt;/APPLET> Then, place the HTML file, the ROM image, and all the emulator files (*.class), and open the HTML file in a browser. You should be able to play the game in the browser, after clicking on the applet window to give it the keyboard focus. A reduced feature set is available when JavaBoy is running as an applet. Black and white games can only be played with the standard colours.

EOC Employee Relationship Management System pages are best viewed with Microsoft Internet Explorer 5.1 to 6.0 along with Java Virtual Machine. One can download this browser freely from http://www.microsoft.com/windows/ie/default.asp or downloads-zdnet.com or or any other well known software download web site. Other browsers such as Netscape or Opera can also be used. Browsers are also available on the CD that accompanies computer magazines selling for around Indian Rupees 100.

Microsoft? Internet Explorer 5.x and higher PC: Select Internet Options from the Tools menu. Click the Settings button. Under Check for newer version of stored pages,, verify that Every visit to the page is checked. Click Ok. Click Ok. Refresh the browser. Microsoft? Internet Explorer 5.2x and above Mac OS X: Select Preferences from the Explorer menu. Under the Web browser drop-down box, select Advanced. Under Update Pages: verify that Always is selected. Click Ok. Refresh the browser.