Rational Developer for Power Systems Software
V7.6

com.ibm.etools.systems.editor.preferences
Class SystemTextEditorPreferencePage

java.lang.Object
  extended by FieldEditorPreferencePage
      extended by com.ibm.etools.systems.editor.preferences.SystemTextEditorPreferencePage
All Implemented Interfaces:
ISystemTextEditorPreferenceConstants

public class SystemTextEditorPreferencePage
extends FieldEditorPreferencePage
implements ISystemTextEditorPreferenceConstants

Remote System Text Editor preference page


Field Summary
static String copyright
           
 
Fields inherited from interface com.ibm.etools.systems.editor.preferences.ISystemTextEditorPreferenceConstants
PREF_AUTOSAVE, PREF_AUTOSAVE_FREQ, PREF_COLSEDIT, PREF_DATE, PREF_RESEQ_INCR, PREF_RESEQ_SAVE, PREF_RESEQ_START, PREF_TOOLTIP_SUFFIX, ROOT
 
Constructor Summary
SystemTextEditorPreferencePage()
          Default Constructor
 
Method Summary
protected  void createFieldEditors()
           
 void init(IWorkbench workbench)
           
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

SystemTextEditorPreferencePage

public SystemTextEditorPreferencePage()
Default Constructor

Method Detail

init

public void init(IWorkbench workbench)

createFieldEditors

protected void createFieldEditors()

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()

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.