| org.geotools.event.GTComponent
All known Subclasses: org.geotools.event.AbstractGTComponent, org.geotools.event.GTConstant,
| GTComponent | | public interface GTComponent (Code) | | Provides support for Parent/Child relationships for the event system.
Several of the GeoTools objects are produced in reference to
specifications, in particular XML based specifications. Often
we try and match the same abstractions present in a specification
like SLD or Filter. But rather then make use of pure Java Beans, and
make user interface code responsible for managing a host of listeners
we are providing a single set of listeners located at the object
matching the document base.
For more Details:
- This design is similar to EMF, or JFace use (aka borrow code examples)
- Not specific to Documents, the Catalog api will use these events
- We do try and match the document structure perfectly for Feature/FeatureCollection/GML
(so that the same XPath expressions can be respected). FeatureCollection and
Feature have their own well explored structure and issues and will not be using
this event system. Given the size of FeatureCollections it is not practicle for each
child to "know" its parent.
author:
Jody Garnett |
| Method Summary | |
| void | changed(GTDelta delta)
A child has been changed (maybe added), issued after change.
This method is for use by children only it is implementor
API and should not be called by client code.
Q:Why does it exist then?
So you can implement your own Symbolizer,
and still allow the GeoTools Stroke implementation to pass change
notification onto you.
Q:GeoAPI does not support this?
No they don't, their interface are set up to match specification
for interoptability between toolkit implementations. | | public GTNote | getNote()
Small stratagy object passed in by our parent so we can call home. | | GTComponent | getParent()
Used to locate our parent. | | void | removed(GTDelta delta)
A child has been removed, issued before change.
This method is for use by children only it is implementor
API and should not be called by client code.
Q:Why does it exist then?
So you can implement your own Symbolizer,
and still allow the GeoTools Stroke implementation to pass change
notification onto you.
Q:GeoAPI does not support this?
No they don't, their interface are set up to match specification
for interoptability between toolkit implementations. | | public void | setNote(GTNote container)
Small stratagy object passed in by our parent so we can call home. |
| changed | | void changed(GTDelta delta)(Code) | | A child has been changed (maybe added), issued after change.
This method is for use by children only it is implementor
API and should not be called by client code.
Q:Why does it exist then?
So you can implement your own Symbolizer,
and still allow the GeoTools Stroke implementation to pass change
notification onto you.
Q:GeoAPI does not support this?
No they don't, their interface are set up to match specification
for interoptability between toolkit implementations. By the time
you pass a GeoAPI object around it should stop wiggling and just be
viewed as stable data. But yes we should ask them about this...
|
| getNote | | public GTNote getNote()(Code) | | Small stratagy object passed in by our parent so we can call home.
Used to pass change information "up" to our parent, to root parent
will broadcast the events out to listeners.
|
| getParent | | GTComponent getParent()(Code) | | Used to locate our parent.
This method will return a "NULLObject", called GTRoot.NO_PARENT when
no parent is present, client code should never have to be concerned
this method return null.
Parent GTComponent or GTRoot.NO_PARENT if none |
| removed | | void removed(GTDelta delta)(Code) | | A child has been removed, issued before change.
This method is for use by children only it is implementor
API and should not be called by client code.
Q:Why does it exist then?
So you can implement your own Symbolizer,
and still allow the GeoTools Stroke implementation to pass change
notification onto you.
Q:GeoAPI does not support this?
No they don't, their interface are set up to match specification
for interoptability between toolkit implementations. By the time
you pass a GeoAPI object around it should stop wiggling and just be
viewed as stable data. But yes we should ask them about this...
|
| setNote | | public void setNote(GTNote container)(Code) | | Small stratagy object passed in by our parent so we can call home.
Used to pass change information "up" to our parent, to root parent
will broadcast the events out to listeners.
Parameters:
container - |
|
|