iSeries Remote Systems
v6.0.1

com.ibm.etools.iseries.editor.preferences
Class AutoSyntaxCheckFieldEditor

java.lang.Object
  extended byorg.eclipse.jface.preference.FieldEditor
      extended byorg.eclipse.jface.preference.BooleanFieldEditor
          extended bycom.ibm.etools.iseries.editor.preferences.AutoSyntaxCheckFieldEditor
All Implemented Interfaces:
IISeriesEditorConstants

public class AutoSyntaxCheckFieldEditor
extends BooleanFieldEditor
implements IISeriesEditorConstants

A field editor which can be used to specify automatic syntax checking by a parser. Tooltip and info pop are included.


Field Summary
static String copyright
           
 
Fields inherited from class org.eclipse.jface.preference.BooleanFieldEditor
DEFAULT, SEPARATE_LABEL
 
Fields inherited from class org.eclipse.jface.preference.FieldEditor
HORIZONTAL_GAP, IS_VALID, VALUE
 
Fields inherited from interface com.ibm.etools.iseries.editor.IISeriesEditorConstants
ACTION_COMPILE_ID, ACTION_VERIFYPROGRAM_ID, COMPILE_ERROR_CLASS_NAME, COMPILE_ERROR_MESSAGE_STYLE, FILE_TYPE_CL, FILE_TYPE_DDS, FILE_TYPE_OTHER, FILE_TYPE_RPGILE, FILE_TYPE_RPGOPM, MAX_DS_NESTING, PREF_AUTO_FORMAT, PREF_AUTO_FORMAT_T, PREF_AUTO_UPPER, PREF_AUTO_UPPER_T, PREF_BASE_PREFIX, PREF_BLANK, PREF_BLANK_SUFFIX, PREF_BLANK_T, PREF_COLSEDIT_T, PREF_COMMAND_POS, PREF_COMMAND_POS_T, PREF_DATE, PREF_DATE_T, PREF_HIGHLIGHT, PREF_HIGHLIGHT_BACKGROUND, PREF_HIGHLIGHT_BACKGROUND_T, PREF_HIGHLIGHT_T, PREF_INDENT, PREF_INDENT_T, PREF_INDENTATION, PREF_INDENTATION_T, PREF_LABEL_ABOVE_CMD, PREF_LABEL_ABOVE_CMD_T, PREF_LABEL_POS, PREF_LABEL_POS_T, PREF_ONE_PARM_PER_LINE, PREF_ONE_PARM_PER_LINE_T, PREF_RESEQ_INCR, PREF_RESEQ_INCR_T, PREF_RESEQ_SAVE, PREF_RESEQ_SAVE_T, PREF_RESEQ_START, PREF_RESEQ_START_T, PREF_SIGNATURE_T, PREF_SQL_SYNTAX_CHECK, PREF_SQL_SYNTAX_CHECK_T, PREF_SYNTAX_CHECK, PREF_SYNTAX_CHECK_T, PREF_TAB, PREF_TAB_GENERAL, PREF_TAB_GENERAL_T, PREF_TAB_T, PREF_TOOLTIP_SUFFIX, SYNTAX_ERROR_CLASS_NAME
 
Constructor Summary
AutoSyntaxCheckFieldEditor(String name, Composite parent)
          Constructor for AutoSyntaxCheckFieldEditor.
 
Method Summary
protected  void doFillIntoGrid(Composite parent, int numColumns)
          enhanced version which adds tooltip and infopop
 
Methods inherited from class org.eclipse.jface.preference.BooleanFieldEditor
adjustForNumColumns, doLoad, doLoadDefault, doStore, getBooleanValue, getChangeControl, getNumberOfControls, setEnabled, setFocus, setLabelText, valueChanged
 
Methods inherited from class org.eclipse.jface.preference.FieldEditor
applyFont, checkParent, clearErrorMessage, clearMessage, convertHorizontalDLUsToPixels, convertVerticalDLUsToPixels, createControl, dispose, fillIntoGrid, fireStateChanged, fireValueChanged, getFieldEditorFontName, getLabelControl, getLabelControl, getLabelText, getPreferenceName, getPreferencePage, getPreferenceStore, init, isValid, load, loadDefault, presentsDefaultValue, refreshValidState, setButtonLayoutData, setPreferenceName, setPreferencePage, setPreferenceStore, setPresentsDefaultValue, setPropertyChangeListener, showErrorMessage, showMessage, store
 
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

AutoSyntaxCheckFieldEditor

public AutoSyntaxCheckFieldEditor(String name,
                                  Composite parent)
Constructor for AutoSyntaxCheckFieldEditor.

Parameters:
name - the property name for this field
parent - the parent of the field editor's control
Method Detail

doFillIntoGrid

protected void doFillIntoGrid(Composite parent,
                              int numColumns)
enhanced version which adds tooltip and infopop

See Also:
FieldEditor.doFillIntoGrid(Composite, int)

iSeries Remote Systems
v6.0.1

Copyright © 2005 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.