Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.rse.ui.actions
Class QSYSExpandLibraryToSrcFilesAction

java.lang.Object
  extended by SystemViewExpandToBaseAction
      extended by com.ibm.etools.iseries.rse.ui.actions.QSYSExpandLibraryToBaseAction
          extended by com.ibm.etools.iseries.rse.ui.actions.QSYSExpandLibraryToSrcFilesAction

public class QSYSExpandLibraryToSrcFilesAction
extends QSYSExpandLibraryToBaseAction

Expand To -> Source Files actions for library objects.


Field Summary
static String Copyright
           
 
Constructor Summary
QSYSExpandLibraryToSrcFilesAction(Shell parent)
          Constructor for QSYSExpandLibraryToSrcFilesAction.
 
Method Summary
protected  String getFilterString(Object selectedObject)
          Overridable extension point to get the fully resolved filter string at the time action is run.
 
Methods inherited from class com.ibm.etools.iseries.rse.ui.actions.QSYSExpandLibraryToBaseAction
addExpandToActions, getExpandToActions, getTypeAttrString
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

Copyright

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

QSYSExpandLibraryToSrcFilesAction

public QSYSExpandLibraryToSrcFilesAction(Shell parent)
Constructor for QSYSExpandLibraryToSrcFilesAction.

Method Detail

getFilterString

protected String getFilterString(Object selectedObject)
Overridable extension point to get the fully resolved filter string at the time action is run.

Overrides:
getFilterString in class QSYSExpandLibraryToBaseAction

Rational Developer for Power Systems Software
V7.6

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.