Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.edit.ui.dialogs
Class ISeriesEditorSystemPromptDialog

java.lang.Object
  extended by SystemPromptDialog
      extended by com.ibm.etools.iseries.rse.ui.dialogs.QSYSSystemPromptDialog
          extended by com.ibm.etools.iseries.edit.ui.dialogs.ISeriesEditorSystemPromptDialog

public class ISeriesEditorSystemPromptDialog
extends QSYSSystemPromptDialog

Dialog for prompting the user to specify a iseries connection The connection would be used by the editor to access any host information Used for local files, some actions require host information - e.g. Program verifier


Field Summary
static String copyright
           
 
Fields inherited from class com.ibm.etools.iseries.rse.ui.dialogs.QSYSSystemPromptDialog
_connectionCombo, _connectionSelected
 
Constructor Summary
ISeriesEditorSystemPromptDialog(Shell shell)
          Constructor
 
Method Summary
protected  Control createInner(Composite compositeParent)
           
 
Methods inherited from class com.ibm.etools.iseries.rse.ui.dialogs.QSYSSystemPromptDialog
getInitialFocusControl, getSelectedSystem, widgetDefaultSelected, widgetSelected
 
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

ISeriesEditorSystemPromptDialog

public ISeriesEditorSystemPromptDialog(Shell shell)
Constructor

Method Detail

createInner

protected Control createInner(Composite compositeParent)
Overrides:
createInner in class QSYSSystemPromptDialog
See Also:
SystemPromptDialog#createInner(Composite)

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.