This page last changed on Nov 19, 2005 by admin.

Catalog User Interface Extensions

Many of the extension points support the use of the IOp interface to define user interface needs. This represents a suitable compromise that can be maintained both by uDig and Toolkit providers.

IOp
interface IOp {
  InternationalString getName();
  InternationalString getDescription ();
  Map params( Object resource );
}

The Map params is initially a set of ?defaults? that may be used by the user to configure the activity. The Map keys are of type InternationalString that are suitable for display.
When this contribution is used to populate the context menu of a FeatureType in the Catalog UI, a small wizard will be activiated with the following workflow:
1.Based on resource selected, the appropriate IOps will be presented to the user. The user selects the desired operation.
2.If the Map params is not null, a Dialog will be created and the user can choose to modify the values. The resource is provided allowing the IOp to supply custom defaults.
3.The appropriate op method will be called.
4.If an Exception is thrown it will be sent to the Log.

  • You may wish to provide your own feedback via the issues list
    (ie. when performing data validation)

Extension net.refractions.udig.catalog.ui.service Not implemented

Supports access of services, including the creation of new spatial information.

Service Ops
interface IDataStoreOp extends Iop {
  void op( DataStore service ) throws Exception;
}
interface IWMSOp extends IOp {
  void op( WebMapServer wms ) throws Exception;
}
interface IGCE extends IOp {
  void op( GridCoverageExchange gce ) throws Exception;
}

Extension net.refractions.udig.catalog.ui.featureType

A slightly easier to use version of service, it operates at the level of a FeatureSource. Client code is responsible for doing any Transaction stuff they want.
The extension point requires an implementation of net.refractions.udig.catalog.ui.IFeatureTypeOp.
IFeatureTypeOp receives several objects during execution of its op method:

Feature Ops
interface IFeatureTypeOp extends IOp{
  FeatureType op( FeatureType schema ) throws Exception;
}
interface IfeatureSourceOp extends IFeatureTypeOp {
  void op( FeatureSource source ) throws Exception;
}
interface IFeatureStoreOp extends IFeatureTypeOp {
  void op( FeatureStore source ) throws Exception;
}
interface ILayerOp extends IOp {  
  void op( WMSLayer layer ) throws Exception;
}
interface IGridCoverageOp extends IOp {
  void op( GridCoverage grid ) throws Exception;
}

The Map params is initially contains set ?defaults? that may be used by the user to configure the activity. The Map keys are of type InternationalString and are suitable for display.
Note: When working with a FeatureStore actual data modification is expected; the FeatureStore you receive will be using a Framework supplied and managed Transaction. If your op completes without exception, the Transaction will be committed.

Document generated by Confluence on Nov 19, 2005 20:03