[EMAIL PROTECTED] wrote:
started with geotools, I noticed that the snippets were not working. So
after I had found out the hard way how things are to be done, I posted
two snippets myself. Out came a newer version of geotools, I think we
went from 2.1.M3 to 2.1.M5, and my snippets no longer even compiled. So
then I knew why the existing snippets did not work. What am I expected
to do, adapt my snippets after every new version of geotools? The same
happened to a graticule module I was trying to donate to the project,
after the first newer version it no longer compiled and it took me a day
to get it working again.
Hi - sorry about your frustration. The 2.1 M cycle was a mess (one we
are still cleaning up from, witness the fact StyledMapPane did not make
the trip). One thing, the only thing, I am worried about is making sure
that this is improved. I am very interested in making geotools more
accessible as part of uDig - but I have more sway there to package
things up so they make sense. I am basically happy that geotools now has
releases (at all), and stable releases are still a new experience for
everyone. This is the first time that geotools had stood still long
enough to be documented.
The big issue here is one a split, between users and developers. I want
that erased.
There are two things that can help:
- Include *use* in the Developers Guide (the only document I will
maintain, and use is a fair topic).
- Include the code examples in the source code, and make compile errors
a down-check for the the library.
Right now I have *no* idea what snippets are available, unless we have
tool support to catch errors I never will.
James had an idea for making a demo directory on trunk, and making the
compile errors work out. There was also an example of using source
code right from version control in the documentation (so the docs are
always correct). To gain room we can consider making a new confluence
space GEODOC, similar to the space GeoServer is working on.
I am willing to put time in organization, if others are willing to put
time into the writing. They key for me is any documentation effort
has to be maintainable (and maintained). I figure this can be accomplish
the two technical challenges are met, and with this amount of
interest we should have enough volunteers for collaboration.
So how about it, would the user list like to lead a documentation charge :-)
Jody
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Geotools-gt2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
