Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.rse.ui.commands
Class IBMiSourceViewerConfiguration

java.lang.Object
  extended by SystemCommandViewerConfiguration
      extended by com.ibm.etools.iseries.rse.ui.commands.IBMiSourceViewerConfiguration

public class IBMiSourceViewerConfiguration
extends SystemCommandViewerConfiguration

This is a refinement of the DocumentViewer support for the command field, for iSeries commands in user actions. The refinements are to do with the fact iSeries substitution variables use &x style, versus ${x} style.


Field Summary
static String copyright
           
 
Constructor Summary
IBMiSourceViewerConfiguration()
          Constructor for ISeriesSourceViewerConfiguration.
 
Method Summary
protected  char[] getCompletionProposalAutoActivationCharacters()
          Return the characters which trigger the auto-display of the list substitution variables.
protected  int getStart(String string, int end)
          Guesses the start position of the completion.
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

copyright

public static final String copyright
See Also:
Constant Field Values
Constructor Detail

IBMiSourceViewerConfiguration

public IBMiSourceViewerConfiguration()
Constructor for ISeriesSourceViewerConfiguration.

Method Detail

getStart

protected int getStart(String string,
                       int end)
Guesses the start position of the completion. Backs up to the previous '&' character and starts there.


getCompletionProposalAutoActivationCharacters

protected char[] getCompletionProposalAutoActivationCharacters()
Return the characters which trigger the auto-display of the list substitution variables. We override the parent for iSeries so we can return '&' versus '$'


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.