Hi Sorry I just caught up on this thread now. I share Martin's concern about dropping C++ support by adopting traits directly. Have you made a decision on this, is C++ still on the cards?
Regards Tim On Fri, Jul 8, 2011 at 7:46 AM, MALIK Julien <[email protected]> wrote: > Hello Camilo, > > Some feedback about your todo list : > > - constraints and validator is low priority to me : it can be handled by the > underlying implementation for now > - user level is low priority to me as it will probably be easy to add this > feature later when the big things will be in shape > - interactive parameters : higher priority to me. Having a way for the > implementation to tell the GUI "update every widgets". Maybe I already have > a way to do that (?) > > A few things you don't mention : > - running the processing modules programmatically > - progress reporting > - logging > - multiple values parameter type (at least to provide a "multiple input > layers" parameter type) > - parameter groups (what happen currently with the SAGA "nodes" ?) > > I agree with your analysis : being able to access the QGis layers for the > input/output is now the most important thing to focus on. > > What precisely is blocking you on this topic ? > I saw some recent updates adding a combobox with the layers but did not test > it yet. The implementations could handle the conversion into their own > internal data structure from the MapLayer objects. > I know at least that on the OTB side, a first step will be getting a > gdal/ogr compatible dataset name and pass them as input files to the > implementation. > As I can remember, SAGA has a "gdal/ogr" importer module for inputs, and the > output should be simple also as the saga file format is supported by gdal. > > Regards, > Julien > > Quoting Camilo Polymeris <[email protected]>: > >> Hello everyone, >> >> the end of GSoC's first term is nearing and while I think we have made >> a significant progress, many things are still pending. I have tried to >> identify a few and compile a short list[1], to try to keep focused >> during the next few weeks. >> I'll try to create a proper timeline with (some of) those items & >> would appreciate your comments. Anything missing? Some things more >> urgent than others? >> >> Of course, most of the work will revolve around the first item: Data >> exchange. Still no clarity on how to handle that. >> >> Regards, >> >> Camilo >> >> > > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > > _______________________________________________ > Qgis-developer mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/qgis-developer > -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) ============================================== Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Visit http://linfiniti.com to find out about: * QGIS programming and support services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net ============================================== _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
