com.ibm.etools.iseries.editor
Class ISeriesEditorRPGILESourceViewerConfiguration
java.lang.Object
org.eclipse.jface.text.source.SourceViewerConfiguration
com.ibm.lpex.alef.LpexSourceViewerConfiguration
com.ibm.etools.iseries.editor.ISeriesEditorRPGILESourceViewerConfiguration
- public class ISeriesEditorRPGILESourceViewerConfiguration
- extends com.ibm.lpex.alef.LpexSourceViewerConfiguration
Configuration for code assist
Methods inherited from class org.eclipse.jface.text.source.SourceViewerConfiguration |
getAnnotationHover, getAutoIndentStrategy, getConfiguredContentTypes, getConfiguredDocumentPartitioning, getConfiguredTextHoverStateMasks, getContentAssistant, getContentFormatter, getDefaultPrefixes, getDoubleClickStrategy, getIndentPrefixes, getInformationControlCreator, getInformationPresenter, getOverviewRulerAnnotationHover, getPresentationReconciler, getReconciler, getTabWidth, getTextHover, getUndoManager |
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
_parser
protected ISeriesEditorRPGILEParser _parser
_view
protected com.ibm.lpex.core.LpexView _view
ISeriesEditorRPGILESourceViewerConfiguration
public ISeriesEditorRPGILESourceViewerConfiguration(com.ibm.lpex.core.LpexView view,
ISeriesEditorRPGILEParser parser)
- Constructor.
getLpexContentAssistant
public com.ibm.lpex.alef.contentassist.IContentAssistant getLpexContentAssistant(ISourceViewer sourceViewer)
- Return the example content assistant ready to be used with the
given LPEX source viewer.
- See Also:
LpexSourceViewerConfiguration.getLpexContentAssistant(org.eclipse.jface.text.source.ISourceViewer)
getTextHover
public ITextHover getTextHover(ISourceViewer sourceViewer,
String contentType)
- See Also:
SourceViewerConfiguration.getTextHover(ISourceViewer, String)
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.