ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzakx_5.4.0.1/rzakxhowplugswork.htm

77 lines
5.3 KiB
HTML

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2005" />
<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="concept" />
<meta name="DC.Title" content="How plug-ins work" />
<meta name="abstract" content="A detailed example of how iSeries Navigator will locate a new plug-in and install it in a new configuration" />
<meta name="description" content="A detailed example of how iSeries Navigator will locate a new plug-in and install it in a new configuration" />
<meta name="DC.Relation" scheme="URI" content="rzakxplugsuport.htm" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzakxhowplugswork" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<link rel="stylesheet" type="text/css" href="./ic.css" />
<title>How plug-ins work</title>
</head>
<body id="rzakxhowplugswork"><a name="rzakxhowplugswork"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">How plug-ins work</h1>
<div><p>A detailed example of how iSeries Navigator will locate a new plug-in
and install it in a new configuration</p>
<p><strong>The following illustration demonstrates how a Java™ plug-in
that adds a new container to the iSeries™ Navigator tree could work.</strong></p>
<p>After identifying the new plug-in to the Windows<sup>®</sup> registry, iSeries Navigator
will find the new plug-in and install it in a new configuration. Afterwards,
the new container will appear in the iSeries Navigator hierarchy. When the
user selects the container, the plug-in's Java code is called to obtain the container's
contents--in this case, a list of messages on the user's default message queue.</p>
<div class="fignone"><span class="figcap">Figure 1. iSeries Navigator dialog -- messages in the message queue</span><br /><img src="rzakx001.gif" alt="Operations Navigator message queue" /><br /></div>
<p>iSeries Navigator
communicates with the Java plug-in by calling methods defined
on a Java interface:
ListManager. This interface lets Java applications supply list data to the
Navigator's tree and list views. To integrate your application into iSeries Navigator,
you create a new Java class that implements this interface. The methods
on the new class call into your existing Java application to obtain the list data,
as shown below.</p>
<div class="fignone"><span class="figcap">Figure 2. How iSeries Navigator calls an application to obtain list data</span></div>
<br /><img src="rzakx500.gif" alt="How iSeries Navigator obtains list data" /><br /><p>What happens when the user wants to perform an action on one of your objects?
The illustration below shows what happens when the user right-mouse clicks
on a message object to display its context menu.</p>
<div class="fignone"><span class="figcap">Figure 3. iSeries Navigator object context menu</span></div>
<br /><img src="rzakx003.gif" alt="iSeries Navigator object context menu" /><br /><p>iSeries Navigator
calls a predefined method on another Java interface: ActionsManager. This interface
obtains the list of menu items supported for message objects. Once again,
you would create a new Java class that implements this interface.
This is how you make your application's specialized functions available to
your users through iSeries Navigator. When the user selects the menu
item, the Navigator calls another ActionsManager method to perform the action.
Your ActionsManager implementation calls your existing Java application,
which then can display a confirmation dialog or some other more sophisticated
user interface panel that allows the user to perform a specialized task. The iSeries Navigator
user interface is designed to let users work with lists of iSeries server
resources and to perform actions on them. The architecture of the plug-in
feature reflects this user interface design, both by defining interfaces for
working with lists of objects in a hierarchy, and for defining actions on
those objects. A third interface, DropTargetManager, handles drag-and-drop
operations.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakxplugsuport.htm" title="iSeries Navigator Plug-in support provides a convenient way to integrate your own functions and applications into a single user interface: iSeries Navigator.">Plug-in support in iSeries Navigator</a></div>
</div>
</div>
</body>
</html>