> Sounds great to me. I guess it's better to use an enum, instead of
> string, but the syntax of those examples is perfect from my point of
> view
Well I want to see it run first, to make sure we are on the right track.
> hmmm, I do not understand this one. The GROUP parameter I was
> proposing was to define a group of parameters which are mutually
> exclusive, meaning that just one of them can be used at a time to
> configure the process.
Okay we had a different idea of group then. I will think up another example
(perhaps GROUP="name", GROUP_TYPE=choice).
Another example we have (that is a real pain) is the repeating "pairs" that
occur in the INTERPOLATE function, I am really
not sure as how to best capture that …
Still it may be best to capture it at all (perhaps GROUP="range",
GROUP_TYPE=repeat
Finally I am on the verge of an idea to make the first example easier. We could
have a GROUP_RELATIONSHIP=enable - which would be used to let that boolean flag
enable the
other parameters in the group.
I think we should start a wiki page and write these examples down as we figure
them out on email here.
Jody
------------------------------------------------------------------------------
How fast is your code?
3 out of 4 devs don\\\'t know how their code performs in production.
Find out how slow your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219672;13503038;z?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
