Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.parsers
Class ISeriesEditorRPGILESQLSourceViewerConfiguration

java.lang.Object
  extended by LpexSourceViewerConfiguration
      extended by com.ibm.etools.iseries.parsers.ISeriesEditorRPGILESourceViewerConfiguration
          extended by com.ibm.etools.iseries.parsers.ISeriesEditorRPGILESQLSourceViewerConfiguration

public class ISeriesEditorRPGILESQLSourceViewerConfiguration
extends ISeriesEditorRPGILESourceViewerConfiguration

The source viewer configuration to support content assist

Since:
7.0

Constructor Summary
ISeriesEditorRPGILESQLSourceViewerConfiguration(ISeriesEditorRPGILESQLParser parser)
           
 
Method Summary
 IContentAssistant getLpexContentAssistant(ISourceViewer sourceViewer)
          Return the example content assistant ready to be used with the given LPEX source viewer.
 
Methods inherited from class com.ibm.etools.iseries.parsers.ISeriesEditorRPGILESourceViewerConfiguration
getCAInformationControlCreator, getTextHover
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Constructor Detail

ISeriesEditorRPGILESQLSourceViewerConfiguration

public ISeriesEditorRPGILESQLSourceViewerConfiguration(ISeriesEditorRPGILESQLParser parser)
Method Detail

getLpexContentAssistant

public IContentAssistant getLpexContentAssistant(ISourceViewer sourceViewer)
Return the example content assistant ready to be used with the given LPEX source viewer.

Overrides:
getLpexContentAssistant in class ISeriesEditorRPGILESourceViewerConfiguration
See Also:
com.ibm.lpex.alef.LpexSourceViewerConfiguration#getLpexContentAssistant

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.