Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.editor
Class ISeriesEditorCOBOLSourceViewerConfiguration

java.lang.Object
  extended by LpexSourceViewerConfiguration
      extended by com.ibm.etools.iseries.editor.ISeriesEditorCOBOLSourceViewerConfiguration

public class ISeriesEditorCOBOLSourceViewerConfiguration
extends LpexSourceViewerConfiguration

This class overwrites getLpexContentAssistant of LpexSourceViewer for code assist of COBOL.

See Also:
LpexSourceViewerConfiguration

Field Summary
protected  LpexParser parser
           
 
Constructor Summary
ISeriesEditorCOBOLSourceViewerConfiguration(LpexParser input)
          Constructor.
 
Method Summary
 IContentAssistant getLpexContentAssistant(ISourceViewer sourceViewer)
          Returns the content assistant for COBOL.
 ITextHover getTextHover(ISourceViewer sourceViewer, String contentType)
           
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

parser

protected LpexParser parser
Constructor Detail

ISeriesEditorCOBOLSourceViewerConfiguration

public ISeriesEditorCOBOLSourceViewerConfiguration(LpexParser input)
Constructor.

Parameters:
input - the input editor.
Method Detail

getLpexContentAssistant

public IContentAssistant getLpexContentAssistant(ISourceViewer sourceViewer)
Returns the content assistant for COBOL.

See Also:
LpexSourceViewerConfiguration#getLpexContentAssistant

getTextHover

public ITextHover getTextHover(ISourceViewer sourceViewer,
                               String contentType)
See Also:
SourceViewerConfiguration

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.