[Previous] [Next] [TOC] [Index]

Chapter 1
Introduction

Introduction

The Visual JavaScript Component Developer's Kit (CDK) describes how to create, tailor, package, and import Netscape ONE components for use in Visual JavaScript. A Netscape ONE component adheres to the JavaSoft Bean specification, and can be a:

To the end user of a Visual JavaScript application, the originating source of a component does not matter. Once incorporated, all components function transparently. Visual JavaScript developers, on the other hand, must either create new components, or use existing components, and package them for use in their applications. Developers can also create new components (or use existing ones) to add to the Visual JavaScript palette at design-time to aid in application development. The CDK describes the steps a developer must take to incorporate Netscape ONE components into Visual JavaScript.

Where To Find Information

The CDK is divided into the following sections:

Section Contents
Working with JavaScript Components.

Describes how to create and incorporate JavaScript components in Visual JavaScript. Provides examples and a reference for the JSB file structure.

Working with Java Beans

Describes how to incorporate and access Java Beans in Visual JavaScript. Not immediately available for initial PR2 release.

Working with CORBA Components

Describes how to incorporate CORBA-compliant components in Visual JavaScript. Not available for PR2 release.

Working with Plug-ins

Describes how to incorporate and interact with plug-in components, such as the multi-media player in Netscape Communicator 4.01. Not available for PR2 release.

Working with BeanConnect Programs

Describes how to use BeanConnect technology in Visual JavaScript. Not immediately available for initial PR2 release.

Importing Components

Describes how to package Netscape ONE components into JAR files and import them into the Visual JavaScript palette for design-time access when building applications.

JSB File Structure Reference

Provides a syntax reference for the JSB file structure used to create JavaScript components.

Each of these sections contains links, as appropriate, to related documentation.

What You Should Already Know

The CDK assumes developers are familiar with object-oriented, event-driven programming. It also assumes familiarity with the Java Beans component model, and the implementation of component properties, events, and methods. All Netscape ONE component development is based on the Java Beans component model, regardless of where a component is first implemented.

If you are developing Java objects, components, or BeanConnect programs for use in Visual JavaScript, the CDK assumes you are familiar with Java programming. If you are creating JavaScript components, the CDK builds on your knowledge of JavaScript. If you are implementing CORBA components, the CDK expects that you are familiar with CORBA requirements and IIOP.

Tools You Need

To develop and test Visual JavaScript applications, you need Visual JavaScript, PR2 and a text editor. To develop, test, and deploy components for use in the Visual JavaScript IDE and your Visual JavaScript applications, you need the CDK. To debug your components and applications, you need the Visual JavaScript debugger.

To develop Java components, you need the Java Beans Developer Kit (BDK) from Sun. If you want to develop components with the Netscape Internet Foundation Classes (IFC), you must get IFC from Netscape. In addition, you must have a Java development tool; at least Sun's JDK 1.1. You will also probably want to use a Java development tool such as Symantec Cafe or Visual Cafe.

To test client components at run-time, you need Netscape Communicator version 4.01. To test server components at run-time, you need Enterprise Server 3.0.


[Previous] [Next] [TOC] [Index]

Last Updated: 07/08/97 10:46:13


Copyright © 1997 Netscape Communications Corporation