Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.rse.ui.propertypages
Class FieldPropertyPage

java.lang.Object
  extended by SystemBasePropertyPage
      extended by com.ibm.etools.iseries.rse.ui.propertypages.FieldPropertyPage

public class FieldPropertyPage
extends SystemBasePropertyPage

The property page for iSeries fields This is an output-only page. The plugin.xml file registers this for remote field objects


Field Summary
static String Copyright
           
protected  boolean initDone
           
 
Constructor Summary
FieldPropertyPage()
          Constructor
 
Method Summary
protected  Control createContentArea(Composite parent)
          Create the page's GUI contents.
protected  void doInitializeFields()
          Initialize values of input fields based on input
 boolean performOk()
          Called by parent when user presses OK
protected  boolean verifyPageContents()
          Validate all the widgets on the page
 
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

initDone

protected boolean initDone
Constructor Detail

FieldPropertyPage

public FieldPropertyPage()
Constructor

Method Detail

verifyPageContents

protected boolean verifyPageContents()
Validate all the widgets on the page

Subclasses should override to do full error checking on all the widgets on the page.


createContentArea

protected Control createContentArea(Composite parent)
Create the page's GUI contents.


doInitializeFields

protected void doInitializeFields()
Initialize values of input fields based on input


performOk

public boolean performOk()
Called by parent when user presses OK


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.