Catalog User Interface ExtensionsMany 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.
Extension net.refractions.udig.catalog.ui.service Not implementedSupports 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.featureTypeA 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. 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. |
(c) Copyright (c) 2004,2005 Refractions Research Inc. and others. |