Rational Developer for Power Systems Software

Class NFSUDTypesEditPane

  extended by SystemUDTypeEditPane
      extended by com.ibm.etools.iseries.rse.ui.uda.NFSUDTypesEditPane

public class NFSUDTypesEditPane
extends SystemUDTypeEditPane

This subclass specializes the named-type edit pane for iSeries (objects and members) native file system named types

Field Summary
static String copyright
Constructor Summary
NFSUDTypesEditPane(NFSUDActionSubsystem udaActionSubsys, ISystemUDAEditPaneHoster parent, ISystemUDTreeView tv)
Method Summary
protected  ISystemUDTypeEditPaneTypesSelector createTypesListEditor(Composite parent, int nbrColumns)
          Overridable exit point.
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail


public static final String copyright
See Also:
Constant Field Values
Constructor Detail


public NFSUDTypesEditPane(NFSUDActionSubsystem udaActionSubsys,
                          ISystemUDAEditPaneHoster parent,
                          ISystemUDTreeView tv)
Method Detail


protected ISystemUDTypeEditPaneTypesSelector createTypesListEditor(Composite parent,
                                                                   int nbrColumns)
Overridable exit point. Create the edit widgets that will allow the user to see and edit the list of file types that constitute this named type.

To better facilitate this, the only requirement is that this "editor" meet the minimal interface com.ibm.etools.systems.core.ui.uda.ISystemUDTypeEditPaneTypesSelector

We override to supply an editor unique for iSeries objects

parent - - the parent composite where the widgets are to go
nbrColumns - - the number of columns in the parent composite, which these widgets should span
a class implementing the required interface

Rational Developer for Power Systems Software

Copyright 2011 IBM Corp. All Rights Reserved.

Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.