Rational Developer for Power Systems Software
V7.6

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

java.lang.Object
  extended by FieldEditorPreferencePage
      extended by com.ibm.etools.iseries.edit.ui.preferences.VerifierPreferencePageRPGILEData

public class VerifierPreferencePageRPGILEData
extends FieldEditorPreferencePage


Field Summary
static String copyright
           
 
Constructor Summary
VerifierPreferencePageRPGILEData()
          Constructor
 
Method Summary
 void createControl(Composite compositeParent)
           
protected  void createFieldEditors()
          Create the field editors to put on the preference page.
 void init(IWorkbench arg0)
           
static void initDefaults(IPreferenceStore store)
          Initializes default values.
 void modifyText(ModifyEvent event)
          Declared in ModifyListener.
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

copyright

public static String copyright
Constructor Detail

VerifierPreferencePageRPGILEData

public VerifierPreferencePageRPGILEData()
Constructor

Method Detail

createControl

public void createControl(Composite compositeParent)
See Also:
PreferencePage

createFieldEditors

protected 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.


modifyText

public void modifyText(ModifyEvent event)
Declared in ModifyListener. One of the combination box text values has changed.


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.