Justin Deoliveira ha scritto: > Hi all, > > I dont think anyone will have any objections but I thought I would bring > it up anyways. Currently the unsupported xml stuff is structured like: > > unsupported/ > xml-xsd/ > xml-gml2/ > xml-gml3/ > xml-filter/ > xml-sld/ > > I would like to change this structure to the following: > > unsupported/ > xml-xsd/ > engine/ > gml2/ > gml3/ > filter/ > sld/ > > I figure that this will be a necessary step when it moves to supported > regardless, so may as well do it now.
By the same token, shall we create a jdbc top folder and stick every jdbc datastore in it, or do the same for file oriented ones? What about creating a plugins/grid for all grid plugins? The current trend in Geotools is to add folders to categorize things, yet I cannot say I'm too happy with this, paths are becoming increasingly long and hard to navigate both from UI and keyboard. For example: C:\progetti\geotools\trunk\modules\plugin\postgis\src\main\java\org\geotools\data\postgis\collection\PostgisFeatureCollection.java (luckily I did checkout "gt" directly, otherwise I would have it too in the path). On my disk I'm following an opposite trend, I'm trying to flatten folders as possible and leverage more sorting to find files. I mean, having 30 items in a folder is not so bad, more than 40 starts to hurt both on a terminal and on screen. Anyways, I'm not fully against either, -0 for me. Cheers Andrea ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
