Remote Systems
v6.4.1

com.ibm.etools.systems.core.ui.view
Class SystemTableViewSorter

java.lang.Object
  extended byViewerSorter
      extended bycom.ibm.etools.systems.core.ui.view.SystemTableViewSorter

public class SystemTableViewSorter
extends ViewerSorter

This class is used for sorting in the SystemTableView. The sorter determines what and how to sort based on property descriptors.

See Also:
Serialized Form

Field Summary
static String Copyright
           
 
Constructor Summary
SystemTableViewSorter(int columnNumber, StructuredViewer view, SystemTableViewColumnManager columnManager)
           
 
Method Summary
 int category(Object element)
           
 int compare(Viewer v, Object e1, Object e2)
           
 int getColumnNumber()
           
 boolean isReversed()
           
 boolean isSorterProperty(Object element, Object property)
           
 void setReversed(boolean newReversed)
           
 
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

SystemTableViewSorter

public SystemTableViewSorter(int columnNumber,
                             StructuredViewer view,
                             SystemTableViewColumnManager columnManager)
Method Detail

isSorterProperty

public boolean isSorterProperty(Object element,
                                Object property)

category

public int category(Object element)

getColumnNumber

public int getColumnNumber()

isReversed

public boolean isReversed()

setReversed

public void setReversed(boolean newReversed)

compare

public int compare(Viewer v,
                   Object e1,
                   Object e2)

Remote Systems
v6.4.1

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.