Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.rse.ui.preferences
Class SystemCommunicationsPreferencePage

java.lang.Object
  extended by FieldEditorPreferencePage
      extended by com.ibm.etools.iseries.rse.ui.preferences.SystemCommunicationsPreferencePage

public class SystemCommunicationsPreferencePage
extends FieldEditorPreferencePage

Preference page for generic Remote System communication preferences


Field Summary
static String Copyright
           
 
Constructor Summary
SystemCommunicationsPreferencePage()
          Constructor
 
Method Summary
 void createControl(Composite parent)
          Configure the composite.
protected  void createFieldEditors()
           
 void init(IWorkbench workbench)
          Inherited method.
static void initDefaults(IPreferenceStore store)
          Set default preferences for the communications preference page.
 boolean performOk()
           
 
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

SystemCommunicationsPreferencePage

public SystemCommunicationsPreferencePage()
Constructor

Method Detail

createControl

public void createControl(Composite parent)
Configure the composite. We intercept to set the help.


createFieldEditors

protected void createFieldEditors()

init

public void init(IWorkbench workbench)
Inherited method.


initDefaults

public static void initDefaults(IPreferenceStore store)
Set default preferences for the communications preference page.

Parameters:
store - PreferenceStore used for this preference page.

performOk

public boolean performOk()
See Also:
FieldEditorPreferencePage#performOk()

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.