[Qgis-developer] Future of standalone browser?

[Richard Duivenvoorde]

On 19-02-17 23:33, Nyall Dawson wrote:
> Hi all,
> 
> Just wanted to raise the discussion about the future of the standalone
> QGIS browser.
...
> So what should we do with the standalone browser in 3.0 and future? is
> there a future here, or should we just drop this functionality and
> save ourselves the maintenance burden? And if there IS interest in
> keeping the browser around, is anyone able to step up and sponsor some
> investment into making browser more useful and polished?

Hi Nyall,

I would be ok too to drop de browser (mainly because I've never used it
standalone, and seeing Tim's first point in practice too).
But what I'm wondering is what code is shared between the
Browser-panel-widget and the stand alone one.
Because some of your points are also valid for the widget? And I have a
troublesome relation with the widget too:
- eating cpu when you have a WMS-node or db node open when you
stop/start QGIS
- very silent failing of drag en drop behaviour (if it works it works,
but ...)
- missing datatypes/services too

So same questions for the panel/widget?

In general I'm in favour of making QGIS as lean as possible for 3.0, it
will gain weight in near future anyway. And this is the only time in
near future that we can do such a diet :-)

Regards,

Richard D