I don't have a problem with the name change to GPX Base, or a Java package structure that started with a prefix like org.geotools.gpxbase.
I'm not sure about merging the modules though. They take two approaches to two different problems. I believe the existing GeoTools module is more tightly integrated with the existing GeoTools feature module. I'm not sure if it would be possible to expose the low-level guts of the existing GPX module, because I'm not even sure how the parsing of the XML files works. I also took some "risks" with my module, like using Joda for time management, using JDOM for file i/o, and making direct use of JTS for GPX entity geometries. I suppose that is why this module belongs in "unsupported". Still, I understand the need to avoid muddying the water with unnecessary duplication. This excercise was really not about the code for me, but about learning the GoeTools development process. I guess I did get kind of hooked on the whole GPX idea, and wrote more code than I ever intended. Landon On Wed, Jun 25, 2008 at 12:57 AM, Martin Desruisseaux <[EMAIL PROTECTED]> wrote: > I do not known GPX at all, but if the proposed module is at a lower level, > would the following make sense? > > * Call it "gpx-base" (or something like that) instead of "gpx2" > * Refactor "gpx" so that it use "gpx-base" > * Maybe (if the modules are small enough) consider merging them together? > > Martin > ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
