Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.edit.ui.preferences
Class VerifierPreferencePageDDSPrtf

java.lang.Object
  extended by FieldEditorPreferencePage
      extended by com.ibm.etools.iseries.edit.ui.preferences.VerifierPreferencePageDDSPrtf
All Implemented Interfaces:
IDDSPrtfDeviceType

public class VerifierPreferencePageDDSPrtf
extends FieldEditorPreferencePage
implements IDDSPrtfDeviceType


Field Summary
static String copyright
           
 
Fields inherited from interface com.ibm.etools.iseries.edit.ui.preferences.IDDSPrtfDeviceType
ADVANCED_FUNCTION_PRINTER_DATA_STREAM, Copyright, INTELLIGENT_PRINTER_DATA_STREAM, SNA_CHARACTER_STREAM
 
Constructor Summary
VerifierPreferencePageDDSPrtf()
          Constructor
 
Method Summary
 void createControl(Composite compositeParent)
           
 void createFieldEditors()
          Create the field editors to put on the preference page.
 void init(IWorkbench arg0)
           
static void initDefaults(IPreferenceStore store)
          Initializes default values.
 
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

VerifierPreferencePageDDSPrtf

public VerifierPreferencePageDDSPrtf()
Constructor

Method Detail

createControl

public void createControl(Composite compositeParent)
See Also:
PreferencePage

createFieldEditors

public void createFieldEditors()
Create the field editors to put on the preference page.


init

public void init(IWorkbench arg0)
See Also:
IWorkbenchPreferencePage#init(IWorkbench)

initDefaults

public static void initDefaults(IPreferenceStore store)
Initializes default values.


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.