com.ibm.etools.iseries.editor
Class ISeriesEditorCOBOLSourceViewerConfiguration
java.lang.Object
org.eclipse.jface.text.source.SourceViewerConfiguration
com.ibm.lpex.alef.LpexSourceViewerConfiguration
com.ibm.etools.iseries.editor.ISeriesEditorCOBOLSourceViewerConfiguration
- public class ISeriesEditorCOBOLSourceViewerConfiguration
- extends com.ibm.lpex.alef.LpexSourceViewerConfiguration
This class overwrites getLpexContentAssistant
of LpexSourceViewer
for code assist of COBOL.
- See Also:
LpexSourceViewerConfiguration
Field Summary |
protected com.ibm.lpex.core.LpexParser |
parser
|
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 com.ibm.lpex.core.LpexParser parser
ISeriesEditorCOBOLSourceViewerConfiguration
public ISeriesEditorCOBOLSourceViewerConfiguration(com.ibm.lpex.core.LpexParser input)
- Constructor.
- Parameters:
input
- the input editor.
getLpexContentAssistant
public com.ibm.lpex.alef.contentassist.IContentAssistant getLpexContentAssistant(ISourceViewer sourceViewer)
- Returns the content assistant for COBOL.
- 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.