Hello,
I'm currently publishing what we have (the specs we made and the code of
our "new" framework), so that we can see what can be merged and how.
More extensive inputs and reaction to current ideas this afternoon...
Julien
Le 27/04/2011 11:30, Paolo Cavallini a écrit :
Il giorno mer, 27/04/2011 alle 11.20 +0200, Martin Dobias ha scritto:
into C++ and add Python bindings. The idea is not to waste time with
writing and rewriting various c++ classes when the API is not clear
yet. Consider this as a suggestion, not a command how to do it :-)
Agreed; it will also be much easier for interested people to follow the
work.
Advanced parameters: some modules may allow users set lots of
parameters. Although this is handy, many times the default values work
well and only few basic parameters are changed regularly. It should be
possible to mark some parameters as advanced and they would be hidden
by default, they would show up after clicking a checkbox or a button.
Right, this works very well with GRASS modules.
Categorization: currently we are starting to face some trouble with
...
This list of processing modules should later get some advanced
functionality like searching, favourite modules or even attaching most
used modules on a toolbar, but that is something for the future, we
are not expecting you to do that during the summer :-) A simple tree
listing tags and modules assigned to them will suffice.
I personally like and use the filtering option of GRASS plugin a lot,
and find this the best option for all users except possibly for the very
first-timers.
Running modules from scripts: you probably have that in mind but let's
Right, this is very important, also to be able to add extra options etc.
Any news from OTB people? Their input is important.
All the best.
_______________________________________________
Qgis-developer mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-developer
