Bug 43873 [Viewers] ViewerSorter need not be abstract
build I20030927 Kim Horne asks: Can ViewerSorter be made concrete? It's perfectly usable as it is as an alphabetical sorter... there doesn't seem to be any reason for it to be abstract. I've attached a patch that'll do it if it's OK. If not...why not? :)
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ViewerSorter.java
* <p>
 * The default <code>compare</code> method compares elements using two steps. 
 * The first step uses the values returned from <code>category</code>. 
 * By default, all elements are in the same category. 
 * The second level is based on a case insensitive compare of the strings obtained 
 * from the content viewer's label provider via <code>ILabelProvider.getText</code>.
 * </p>
 * <p>
 * Subclasses may implement the <code>isSorterProperty</code> method;
 * they may reimplement the <code>category</code> method to provide 
 * categorization; and they may override the <code>compare</code> methods
 * to provide a totally different way of sorting elements.
 * </p>
 * @see IStructuredContentProvider
 * @see StructuredViewer
 */
public abstract class ViewerSorter {
	/**
	 * The collator used to sort strings.
	 */
	protected Collator collator;
/**
 * Creates a new viewer sorter, which uses the default collator
 * to sort strings.
 */
protected ViewerSorter() {
	this(Collator.getInstance());
}
/**
 * Creates a new viewer sorter, which uses the given collator