Optimize with a SATA RAID Storage Solution
Range of capacities as low as $1250 per TB. Ideal if you currently rely on servers/disks/JBODs
onLoadevents and forward new dimensions to the applet. The applet overrides the
setSize()method to revalidate its component layout, and thus let its layout manager adjust itself to the new size. The HTML looks like this:
onLoad parameters in the
<BODY> tag specify the resize event handlers for Internet Explorer, while
window.onResize = resize; and
window.onLoad = resize; do so for Netscape Navigator. Both methods must be included in order to support the two major browsers. Whenever the browser
frame is loaded or resized, the applet's
resize() method is invoked.
Navigator and IE have different methods of accessing the browser window's dimensions. In Navigator, the window object is referenced;
in IE, the document's body object is used. These objects also return slightly different values for the window dimensions.
Thus, it is necessary to determine the browser in which the applet is running before sending the correct window dimensions.
Netscape does not include the width of the scrollbars, and does not let you access this length, so 15 pixels is used as an
offset in the
<APPLET> tag still specifies the applet's
Height parameters, but these dimensions now specify the applet's maximum bounds. The window's maximum width and height,
w_maxHeight, are checked in the
resize() method to ensure that the applet does not go beyond these bounds. The browser still takes up room for this dimension; thus,
scrollbars. The HTML page is also scrolled to the top left corner whenever it is resized to ensure that the applet is fully