Sextante has a nice modeler tool - it may be a good example how it could work: http://www.gvsig.com/files/images/screenshots/gvSIG_Sextante_02.png
AFAIK it also handles saga (although most modules were reimplemented in java) and even grass modules. In fact Sextante is already a processing toolbox - it is written in java so I'm not sure if it could be integrated in qgis, but if a new framework is built in c++/python, it is nevertheless very interesting to see which design decision they took. Johan On Tue, Aug 23, 2011 at 9:45 PM, Camilo Polymeris <cpolyme...@gmail.com> wrote: >> I agree with martin - such a Modeler could be a great improvement but >> I assumed it would be somethink like the WxGUI_Modeler .. > > Yes, I also imagine something similar. > But, I prefer more ordered layouts, where you have all outputs in a > column on the left side, and all inputs in a column on the right side. > In between all connections displayed as lines of different color > depending on parameter type and such. > > A bit like qjackctl's patchbay: > http://ubuntu.allmyapps.com/data/q/j/qjackctl-jack-control/UBUNTU-9.04/qjackctlPatchbayForm1.png > > It looks tidier and would also be a bit easier to implement than > free-floating boxes. > > On the logic side: > For input and output the most flexible would be to use python scripts. > Of course, it is harder than e.g. XML, and there would be limits to > what python code it would understand on input. But still, I think it > is the best option. > > The user would then have the option of saving these "workflow presets" > and using them like any regular module. > > Camilo > _______________________________________________ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer > _______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer