The Style objects currently make use of the following:
#1 getRules()
#2 setRules( Rule[] )
#4 addRule( Rule )
I can hook those up to events:
#1- something changed
#2- something added w/ range
But we did not go for full JavaBeans indexed property compliance:
getRules( int index )
setRules( int index, Rule )
(Not to mention Rule vs Rules plays with the JavaBean convention)
An alternative would be to go for Lists, and implement a List that
intercepts modifications and fires events (this would be compatible with
the direction GeoAPI went).
- List getRules() (really List<Rule>)
At least one developer on the GeoAPI list does seem keen on SLD 1.0.20,
has anyone on this list heard of it being used? (or know if a document
based on SLD 1.0.20 will ever be public?).
So what can we do:
- List rules() - wrapped around the array
- Rule getRules( int )
- setRules( int, Rule )
and ignore GeoAPI....
Jody
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
