Adrian Custer a écrit :
Read http://www.geotools.org/CreateAGeometry and tell me how
I know we are in the JTS, GeoAPI, or Geotools namespace.
This unfortunate situation come from the mix of a (very partial) ISO
19107 implementation, and the usage of JTS in most of Geotools library.
In an ideal world, users should play with only one set of API: ISO 19107
(or a simplified profile if ISO 19107 is judged too complex) and should
not need to know that theirs ISO 19107 interfaces are backed by JTS
implementation. We are not yet there, but this is the goal.
For Geotools, this admonition becomes expanded: DO NOT USE
OPENGIS NAMES FOR CODE NAMES. Many others are liable to do so;
it's not smart long term strategy. How many libraries are going
to create "Feature" objects?
Feature is a particular topic. More on it later.
On CRS, usage of OpenGIS name for Geotools implementations was
unfortunate (as Jody rightly pointed out). It was a bad choice of mine,
which we fixed in 2.1 with the deprecation of all implementation with
OGC names, and replacement by new name. The deprecated classes have been
completly removed in 2.2
On the "Gt" prefix or suffix, we had a vote on both the Geotools
developper list and user list a while ago:
http://jira.codehaus.org/browse/GEOT-490
(They were more votes than the few ones reported in this page; I just
didn't wrote down the last numbers). I proposed a GT suffix, but the
vast majority voted against it. The majority was for "Impl" suffix or
"Default" prefix. After some experience, I have the feeling that the
majority was right. "Default" / "Abstract" prefix seems to work well in CRS.
Feature is a particular case since we do not yet uses the GeoAPI
interfaces. We would like, but we feel that GeoAPI interfaces need
improvement. There is RnD page on this issue.
2) THE WEB SITE LAYOUT IS A ROYAL MESS
I agree that it is not easy to navigate in the web site. The problem (I
believe) is that we don't have any coordinator for the general layout of
this web site. The core developpers are missing time. Some volunter
share their experience in some specific page (for example Rueben wrote
usefull tutorial in CRS pages; Bryce Nordgren wrote a lot of good stuff
in Grid Coverage RnD pages), but there is no general coordinator to my
knowledge.
I you know someone who could rearange the general web site layout and
act as a coordinator, I believe that there is strong need for such help
in Geotools.
What guarantees does the Geotools PMC have that it is possible
to work from scratch to a map without using deprecated
elements?
I'm not quite sure that it is possible right now to use Geotools without
crossing some @deprecated element. I agree that it is an other weakness.
Sometime we were planing to replace a deprecated element very soon, and
it happens that the remplacement took longer that we expected (e.g. the
J2D-renderer not yet ported to the new CRS framework).
Suggested working principles:
----------------------------
* Variable names should be prefixed with Gt, Gt_ or some other
form so they should never be words used directly from any
language.
* Interfaces which are primary for users should include a comment,
KEPT UP TO DATE, explaining the default approach to instantiate
objects of this interface.
* Deprecation can only occur when there is a non-deprecated
alternative pathway for any action which is still necessary.
* All deprecated tags must include a date and information pointing
to the new pathway for preforming the same action (this will
still require users to bounce through the chain of deprecation
but at least there will be a clear chain and a clear time
order).
* The use of factories and builders should be standardized so that
user code exhibits nice parallelism. If that requires working
with other libraries, or writing wrappers to those libraries, so
be it.
* The library should include a base set of tutorials which are
guaranteed to be working in any public release. Your test suite
ought to include three or four user tutorials, including one
designed to go "from scratch" (i.e. doubles and Strings) to a
MapPane or something similar. No shortcuts using WKT or other
convenience methods. The more elegant these tutorials, the
better. (An initial attempt will follow)
I agree with the principles. We will try to go in this direction, but it
may take a while (maybe one year). This is a long term effort.
Martin.
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Geotools-gt2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
