> > Could we have more than one relationship? How do we handle it? You mean one parameter related to many other ones? That could be useful, but I guess it risks making it difficult to handle, since probably additional information was needed to fully describe that more complex relation. Can you put an example of a case where that could be used? To be honest, I just proposed this improvement for the "attribute-from-vector-layer" case, which is very common and I thought it should be addresed with a better semantic that what is done now if the GT processes that have that case, but I didn't think much about other possible cases, as they are not so likely to appear... In this case, many parameters representing attributes might depend on the same parameter representing a FeatureCollection, but the relationship is still simple (basically just what is needed to tell the UI that when a different FC is selected, it should change the available attributes to select from, just like it is implemented in almost every geoprocessing UI in the most common Desktop GISs...). More complex relationships should definitely require a more detailed analysis to be implemented correctly and robustly.
------------------------------------------------------------------------------ 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
