I'm a big +1 on that. I will add my notes on a QEP if one is opened (Hopefully I can be a bit more active in the project after a bit of a break)
- Nathan On Wed, Aug 31, 2016 at 4:29 PM, Neumann, Andreas <[email protected]> wrote: > Hi all, Hi Nyall, Matthias and Denis, > > After some discussion with Nyall we stumbled again over the inconvenience > that widgets in QGIS mix data (core) and GUI part. This effects many places > in QGIS where you want to address the display value of a widget instead of > the raw value: QGIS Server (e.g. GetFeatureInfo Requests), Print Composer, > Labels, Save to Spreadsheet with human readable values, and many more. > > So before people are introducing more and more widgets (which is nice) I > would suggest to first improve our widget infrastructure for QGIS 3.0 to > decouple the Core/data part from the GUI part, which would allow code to > access all widget configuration and properties without having to deal with > the GUI part of the widget. Nyall mentioned that the symbology rendering > separates this nicely, but the attribute widgets do not. > > Nyall suggested to do a QEP for that to discuss the implications and how > this can be cleanly designed. > > Matthias - since you are "the widget guy" - do you want to take a lead on > this QEP? Or should I ask Nyall? > > Thanks, > > Andreas > > > _______________________________________________ > Qgis-developer mailing list > [email protected] > List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer >
_______________________________________________ Qgis-developer mailing list [email protected] List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
