54 lines
4.9 KiB
HTML
54 lines
4.9 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="Shell plug-ins" />
|
||
|
|
<meta name="abstract" content="These registry keys map a particular node or set of nodes in the hierarchy to the type of function supplied by the plug-in, and to the CLSID of the implementation class which implements the function." />
|
||
|
|
<meta name="description" content="These registry keys map a particular node or set of nodes in the hierarchy to the type of function supplied by the plug-in, and to the CLSID of the implementation class which implements the function." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakxsmpcplusreg.htm" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzakxshellext" />
|
||
|
|
<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>Shell plug-ins</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakxshellext"><a name="rzakxshellext"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Shell plug-ins</h1>
|
||
|
|
<div><p>These registry keys map a particular node or set of nodes in the hierarchy to the type of function supplied by the plug-in, and to the CLSID of the implementation class which implements the function.</p>
|
||
|
|
<p>Remember that any number of shell plug-ins may register their intent to add function to a given object type in the Navigator hierarchy. The plug-in should never assume that it is the only server component
|
||
|
|
which is providing function for a given object type. This applies not only to existing object types, but also to any new objects that a plug-in may choose to define. If your plug-in is widely used, there
|
||
|
|
is nothing to prevent another vendor from extending object types that are defined by your plug-in.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Object type identifiers</h4><p>A pair of object type identifiers, subkeys \Sample\*\, are always expected at this level in the subkey hierarchy.</p>
|
||
|
|
<p>The first identifier
|
||
|
|
in the pair specifies the root folder for a Navigator component. For plug-ins that add new folders, this identifier should always match the registry key name for a root folder specified the previous section.
|
||
|
|
For plug-ins which add behaviors to existing object types, this subkey should generally be the object type of the first-level folder under an iSeries™ server container object. These type strings are defined under HKEY_CLASSES_ROOT\IBM.AS400.Network\TYPES in the registry.</p>
|
||
|
|
<p>The second identifier in the pair identifies the
|
||
|
|
specific object type that the plug-in wants to affect. If * is specified, the plug-in will be called the for the folder type identified in the parent subkey, plus all folders and objects which appear in
|
||
|
|
the hierarchy under that folder. Otherwise, a specific type identifier must be specified, and the plug-in will then only be called for that object type.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Checking for object types</h4><p>When performing checks for existing object types, you should use the 3-character type identifiers that are defined under the key HKEY_CLASSES_ROOT\IBM.AS400.Network\TYPES
|
||
|
|
in the registry. When performing checks for new object types that are defined by your plug-in, use a registry key. Use the registry key that identifies the folder that you specified as your junction point,
|
||
|
|
or whatever type you will return to the Navigator when serving data for a folder that is defined by your plug-in.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakxsmpcplusreg.htm" title="The sample plug-includes two registry files: SAMDBG.REG, a windows-readable registry file for use during development and SAMPRLS.REG, a registry file for distribution on the iSeries server.">Customize the C++ registry values</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|