Edit D:\app\Administrator\product\11.2.0\dbhome_1\ide\src\javax\ide\package.html

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
 <meta name="GENERATOR" content="Mozilla/4.7 [en] (WinNT; I) [Netscape]">
<!--

@(#)package.html

-->
</head>
<body bgcolor="#FFFFFF">
 The ide package is where all JSR 198 packages are rooted. There 
 are two types of packages in the ide package:

<ul>
 <li>1. Extension writer packages, and</li>
 <li>2. Service provider packages.</li>
 </ul>

By convention, the latter are named spi and are located under 
 the corresponding extension writer package. The extension writer packages 
 contain interfaces and classes intended for extension writers to implement 
 and/or use, while the spi packages contain abstract classes and 
 default implementations that must be extended by IDE service providers in 
 order to support JSR 198. Extension writers should never import classes 
 from the spi packages.

The extension writer packages can be grouped into two categories:

<ul>
 <li>1. Extension hook packages, and</li>
 <li>2. Support packages.</li>
 </ul>

Extension hook packages contain the interfaces and classes 
 encapsulating an IDE's integration hooks. Integration hooks are the
 points an IDE defines where extension writers can integrate new IDE 
 functionality. These packages are:

<ul>
 <li>The command package: containing interfaces and classes
 involved in the definition and execution of commands. </li>

<li>The editor package: containing interfaces and classes
 used to define new editors and the support to manage them.</li>

<li>The event package: containing interfaces and classes for 
 listeneting to IDE specific events.

<li>The extension package: containing interfaces and classes 
 encapsulaing an extension and its hooks, and the registry to record
 all extensions.</li>

<li>The log package: containing interfaces and classes used to 
 define new log pages.</li>

<li>The menu package: containing interfaces and classes used to 
 define new actions, and menus.</li>

<li>The model package: contaning interfaces and classes used to 
 access an IDE's data model, and define new document types.</li>

<li>The preference package: containing interfaces and classes used 
 to define new IDE preferences.</li>

<li>The view package: containing interfaces and classes used to 
 define new graphical user interfaces.</li>

<li>The wizard package: containing interfaces anc classes used to 
 define new document creation wizards.</li>
 </ul>

In general, these packages contain "feature" and "listener" interfaces that 
 are usually implemented by the extension writer, and a "manager" interface 
 that must be implemented by the IDE service provider. The "manager" interface 
 provides the API to access and manipulate the extension writer "feature" 
 interface implementations. For example, the editor package declares 
 the <code>Editor</code> "feature" interface, the <code>EditorListener</code>
 "listener" interface, and the <code>EditorManager</code> "manager" interface.
 The first two are implemented by extension writers, while the third one 
 by IDE service providers. The IDE service provider implementation can be 
 found under the spi packages. A similar pattern repeats in the other 
 extension hook packages.

Support packages contain supporting interfaces and classes whose
 implementation are generally provided by IDE service providers and are 
 mainly for the use of extension writers. These packages are:
 
 <ul>
 <li>The net package: contains a virtual file system that uses 
 <code>URI</code>s to address objects on any file system.</li>

<li>The util package: contains utility classes.</li>
 </ul>

In addition to the packages described above, the ide package contains
 a number of interfaces and classes. One of those interfaces, the 
 <code>IDE</code> interface is the central repository where all other IDE
 services are accessed. Extension writers can access any of the service
 implementations using the IDE interface.

Another class in the <code>IDEConstants</code> class. Extension writers 
 can find there IDE constants identifying menus, and views.

</body>
</html>

Ms-Dos/Windows Unix Write backup

jsp File Browser version 1.2 by www.vonloesch.de