+1 from me. Docs would be nice yes, something that has been somewhat lower priority on my TODO list. My thoughts for a first shot were:
* some higher level, here is the design * here is how you write a UI module * extension point reference Anyways, not trying to mandate what is needed, rather share what I had in mind. I would be happy to help out / review any docs as well. -Justin Andrea Aime wrote: > Hi, > the Wicket UI went under a GSIP, it has been developed, it's > the only one that can be used on trunk anyways. > Time to move it to supported land? > > I looked into cobertura test coverage reports, they look like: > - core: 40% > - wms: 28% > - wfs: 68% > - wcs: 70% > - demo: 54% > - app: 44% > > So if we want to do things by the book the wms coverage has > to be pushed up another 12%. Not that I think much of these > numbers, the 40% soil is there just to ensure there is > _some_ testing, a well tested module usually has it > well over 80%, and even in that case the pure number might > not mean much. > > Also, I guess we need to write some docs on how the > UI is wired up? > > Anything else? > > Cheers > Andrea > > > -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
