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
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
+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.
Justin Deoliveira ha scritto:
+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
Sounds like a good plan. http://jira.codehaus.org/browse/GEOS-3084
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.
First off, we need a place where these docs live. Time to
svn copy the documentation module to trunk?
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Andrea Aime wrote:
Justin Deoliveira ha scritto:
+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
Sounds like a good plan. http://jira.codehaus.org/browse/GEOS-3084
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.
First off, we need a place where these docs live. Time to
svn copy the documentation module to trunk?
Agreed, I can do that now unless anyone objects. I was thinking that we could slot in the user interface docs under the "Programming Guide" section. Any objections?
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Justin Deoliveira ha scritto:
Andrea Aime wrote:
Justin Deoliveira ha scritto:
+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
Sounds like a good plan. http://jira.codehaus.org/browse/GEOS-3084
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.
First off, we need a place where these docs live. Time to
svn copy the documentation module to trunk?
Agreed, I can do that now unless anyone objects. I was thinking that we could slot in the user interface docs under the "Programming Guide" section. Any objections?
+1 from me
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.