Ben Caradoc-Davies ha scritto: > Thanks a lot, Andrea for your feedback. I will make the changes you > suggest, as they are good. I have commented on a few below: > > Andrea Aime wrote: >> Looked a bit into it. Some general feedback: >> - the tutorial assumes familarity with SVN, it would be nicer to provide >> a link to a zipped file with everything needed to setup the tutorial > > The config includes a build.xml to create the zip (this is the usual way > I distribute my configs), but would the zipped file need to go in SVN to > be included in the docs? I need to understand :download:.
Hmm... not much of an help here. I think David posted a mail on the subject not long ago. We should add his wisdom to the sphix guide. >> - the tutorial uses property files. Developers are comfortable with >> them, but I think no normal user has ever seen that data source in >> action. Some explanation about it is probably required > > Is there a property file tutorial or documentation for > PropertyDataSource in the user or developer manual? Hmmm... I don't think so. Actually we have a Jira somewhere requesting to remove the property datastore from the stores that ship along with GeoServer because it caused confusion. The only "documentation" that I remember is the reason why the property data store was created in the first place, that is, as a tutorial for making new datastores: http://docs.codehaus.org/display/GEOTDOC/Old+Creating+a+DataStore+Tutorial Then it was picked up for testing and became an officially supported datastore for GeoTools, but afaik there is no much extra documentation for it. Jody (cc'ed) might know more. I think we already removed it for 1.7.x, thought it still shows up in trunk. However, removing it would break your demo... hmmm.... >> - in gml:id mapping, why OCQL? I've heard of ECQL (extended) but never >> about OCQL > > Neither have I. This term was used before I joined the project. I have > emailed some likely suspects for an explanation. > >> Finally, I'm a little concerned about the many referencing to your >> wiki... as in, how long is that wiki going to be around? Plus, say you >> work on new features, how do you ensure the GeoServer 2.0 documentation >> points to the state the wiki had for 2.0, and not the current one? (in >> other terms, how to ensure the documentation is versioned?) > > Your concern is well-justified. All the configuration documentation on > the seegrid wiki has to be migrated to the GeoServer user manual. There > is no other sensible way to manage it. Now that we have a Hudson for > trunk docs, there is no reason not to move it as soon as we have time. > In my view, this piece of work is not complete until we have done so. Excellent :) Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
