Peter, this is a good point. I guess my idea was that this information
would be provided by documentation. Unfortunately the doc is slow
getting off the ground...
I've had some discussions about providing an "Operation" framework.
Amongst other things, this would make it more obvious which classes were
intended to be invoked as operations.
I suppose in the short term a tagging interface might do the trick.
For a rule of thumb, the packages under
com.vividsolutions.jts.operation all provide operations, and the
top-level class is the one whose name most closely matches the package name.
Peter Rushforth wrote:
Good evening,
I was looking around for how to use the new buffer styles in jts 1.9,
and I realized
that they only seem available via the Package
com.vividsolutions.jts.operation.buffer,
not in the buffer methods of com.vividsolutions.jts.geom.Geometry.
Which leads me to a general question of how to know if a class is "top-level" vs
a low-level internal-only class? Maybe there is a document which
describes this that
I've missed. Or, is there a rule of thumb to know what top-level might be?
Thanks for any advice,
Peter
_______________________________________________
jts-devel mailing list
[email protected]
http://lists.refractions.net/mailman/listinfo/jts-devel
--
Martin Davis
Senior Technical Architect
Refractions Research, Inc.
(250) 383-3022
_______________________________________________
jts-devel mailing list
[email protected]
http://lists.refractions.net/mailman/listinfo/jts-devel
