com.ibm.etools.iseries.rse.ui.preferences
Class IBMiCachePreferencePage
java.lang.Object
FieldEditorPreferencePage
com.ibm.etools.iseries.rse.ui.preferences.IBMiCachePreferencePage
- All Implemented Interfaces:
- ICacheConstants
public class IBMiCachePreferencePage
- extends FieldEditorPreferencePage
- implements ICacheConstants
Preference page for the iSeries caching options
Fields inherited from interface com.ibm.etools.iseries.subsystems.qsys.cache.ICacheConstants |
CACHE_FILE_CL_COMMAND_EXTENSION, CACHE_FILE_CL_COMMAND_PROPERTIES, CACHE_FILE_CL_HELP_EXTENSION, CACHE_FILE_CL_HELP_TABLE_EXTENSION, CACHE_FILE_CORRUPTED_EXTENSION, CACHE_KEY_DELIMINATOR, MAX_SIZE_DEFAULT, PREF_ALWAYS, PREF_CACHE_LISTS, PREF_CL, PREF_CL_HOST, PREF_CL_IGNORE, PREF_CL_RELEASE, PREF_DISABLE_CACHE, PREF_LEVELCHECK, PREF_LOCATION, PREF_MAX_INMEMORY_CACHE_FILES, PREF_MAXSIZE, PREF_MAXSIZE_OPTION, PREF_NEVER, PREF_OFFLINE_UNIVERSAL, PREF_ONLINE_OPTIONS |
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
copyright
public static final String copyright
- See Also:
- Constant Field Values
IBMiCachePreferencePage
public IBMiCachePreferencePage()
- Constructor
createFieldEditors
protected void createFieldEditors()
initDefaults
public static void initDefaults(IPreferenceStore store)
performDefaults
protected void performDefaults()
- See Also:
FieldEditorPreferencePage#performDefaults()
init
public void init(IWorkbench arg0)
- See Also:
IWorkbenchPreferencePage#init(IWorkbench)
performOk
public boolean performOk()
- See Also:
FieldEditorPreferencePage#performOk()
performApply
protected void performApply()
- See Also:
PreferencePage#performApply()
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.