Yep; that is when I got frustrated and decided to document everything; even
> > with just a placeholder page :-)
> T'was a good idea.
Thanks; it really helped for collecting examples for the user list (as there
was a page to add them to).
> > One thing that is missing from simone's clean up is removing the docs for
> > plugins that have now been deleted.
> I've done that. What do you think to the unsupported page with tables added ?
> I'm not sure if it's the best format.
It looks much better with the descriptions; what do you think of a simple
bulleted list (like the other sections). We could avoid describing the plugins
for now and let people click? Since they are already grouped under headings
people can get an idea what they are about?
The other thought I had looking at that pages was taking a number of "stars"
over (to see what that would look like as a replacement to the module matrix
page)
I wish we had a cunning way to accomplish:
* PLUGIN NAME ( Status: * * * )
where plugin name was a link to the plugin docs; and status was a link to the
usual review information.
Thus far I cannot think of anything cunning; and am afraid the alternative may
be to stop complaining and do the work (multiple times in different spots).
Jody
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
