| TableAndRow

Components Using TableAndRow Interfaces

The sample pages referenced below illustrate how Java, JavaScript and HTML components use standard events and interfaces to easily inter-operate on an HTML page.

Events used include:

- Java "TableChange", "RowChange", "PropertyChange" events.
- JavaScript "onChange" event.
- HTML "onchange" event.

Components use either a standard .JSB file or provide a class implementing the BeanInfo interface in order to publish their properties events and methods. JSB files allow the component to specify the "Event Model" they support, so that builder tools like Visual JavaScript can provide a common interface to configure, connect and specify event handling code for HTML, JavaScript and Java components.

All these pages were built using Visual JavaScript PR3.

NOTE: In order to run these samples you need to do the following:

- Use Netscape Communicator/Navigator 4.02 or later.
- Copy these pages to a directory accessible to a web server.
- Copy the \netscape and \netscape\peas directories under that web server directory.
- Access these pages form Netscape Communicator/Navigator 4.02 or later.

JDCtoDF.html - Java Cursor Component "two-way" connected to VJS generated HTML form elements using RowChange event, onchange event, and PropertyChangeAdapter.
JDCtoJF.html - Java Cursor Component "two-way" connected to simple Java Form Applet component using RowChange event.
JDCtoJT.html - Java Cursor Component "two-way" connected to simple Java IFC Grid component using TableChange event.
JSDCtoDF.html - JavaScript Cursor component "two-way" connected to VJS generated HTML form elements using JavaScript onChange events and HTML onchange events. (No Java or Row / Table interfaces used.)
JSDCtoJF.html - JavaScript Cursor component "two-way" connected to simple Java Form applet using the RowChange event and a RowSupport helper object.

While previewing these files as they are shipped with the CDK (in the root of the CDK so they are located just above \netscape\peas) will also work, this method does not replicate a real-world deployed application, and sometimes behaves differently.

( return to the top of the page )