Thanks for the comments guys. I'll leave it in my plug-in for now. After some thought, I may move the methods to a utility class in one of the packages mentioned.
Some recent things I read have me questioning the use of static utility methods. I have decided against them completely just yet, but I'm trying not to use them as much as I did before. SS On Wed, Jan 14, 2009 at 3:25 PM, Stefan Steiniger <sst...@geo.uzh.ch> wrote: > >> If your class is quite generic and you think another plugin may need it, >> places where I would search it at first are : > > I second that > >> >> com.vividsolutions.jump.util.feature package >> or a new >> org.openjump.core.featureutils > > this package does not exist yet, but we have > openjump.core.apitools > > which contains all the helpful api classes from Pirol > > stefan > >> (there is already a >> org.openjump.core.geomutils package) >> >> there are also already some classes related to this area in >> com.vividsolutions.jump.tools >> > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
