Re: [Qgis-developer] Future of standalone browser?

[Caio Hamamura]

Jürgen,

Yes, the integrated browser supporting what I mentioned would also be fine.

2017-02-23 12:07 GMT-03:00 Jürgen E. Fischer :

> Hi Caio,
>
> On Thu, 23. Feb 2017 at 11:58:24 -0300, Caio Hamamura wrote:
> > So, nowadays we keep an ESRI Licence just to use ArcCatalog (which is
> what
> > I expected QGIS Browser to be)
>
> The browser already was removed - if I'm not mistaken this is the first
> response from someone who likes to keep it.
>
> But it sounds like you didn't use the standalone browser yet, correct?
> The browser within QGIS should also offer what you need.
>
>
> Jürgen
>
> --
> Jürgen E. Fischer   norBIT GmbH Tel.
> +49-4931-918175-31
> Dipl.-Inf. (FH) Rheinstraße 13  Fax.
> +49-4931-918175-50
> Software Engineer   D-26506 Norden
> http://www.norbit.de
> QGIS release manager (PSC)  GermanyIRC: jef on FreeNode
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Future of standalone browser?

[Jürgen E . Fischer]

Hi Caio,

On Thu, 23. Feb 2017 at 11:58:24 -0300, Caio Hamamura wrote:
> So, nowadays we keep an ESRI Licence just to use ArcCatalog (which is what
> I expected QGIS Browser to be)

The browser already was removed - if I'm not mistaken this is the first
response from someone who likes to keep it.

But it sounds like you didn't use the standalone browser yet, correct?
The browser within QGIS should also offer what you need.


Jürgen

-- 
Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
Software Engineer   D-26506 Norden http://www.norbit.de
QGIS release manager (PSC)  GermanyIRC: jef on FreeNode 



pgp92vT38kCWn.pgp
Description: PGP signature
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Future of standalone browser?

[Caio Hamamura]

Currently I work in an organization which is very much concerned about the
quality and the structure of the file database with lots of shapefiles,
file geodatabases (ESRI), rasters. Some examples: roads, rivers, country
limits, states limits, county limits, region limits, custom regions limits,
farms limits, ...

So, nowadays we keep an ESRI Licence just to use ArcCatalog (which is what
I expected QGIS Browser to be) just to rename, preview, move stuff around
for organizing stuff around. Since there is a lot of metadata (shx, vat,
xml, ...), ArcCatalog simplifies these processes.

If QGIS Browser did support to do that kind of stuff for organizing data me
and my colleagues would be willing to migrate from ESRI ArcCatalog to QGIS
Browser. Since we are a non profit organization, it would be nice to get
off that extra load in our budgets and to use that resources in our
different projects.

2017-02-20 7:07 GMT-03:00 Mathieu Pellerin :

> I've never used the browser much, I can't say I would miss it if it's
> retired.
>
> The one thing I'd miss a bit is its capability at quickly previewing
> datasets. I'm wondering if this could be somehow integrated into the QGIS'
> browser dock (maybe now made possible following the major layer registry /
> project refactoring which has taken place prior to 3.0?). Just like the
> information panel, we could have a preview panel that renders a preview of
> the vector/raster dataset.
>
> Anyhow; +1 to see the standalone browser gone. :)
>
> Math
>
>
>
>
> On Mon, Feb 20, 2017 at 4:58 PM, Jorge Gustavo Rocha 
> wrote:
>
>> Hi,
>>
>> I never used it, and it is definitely a source of confusion in workshops.
>>
>> Regards,
>>
>> Jorge Gustavo
>>
>> Às 07:52 de 20-02-2017, Nathan Woodrow escreveu:
>> > It's the same code, just in dock form.  I find the browser dock to be
>> > super helpful but have never used the standalone version.
>> >
>> > On Mon, Feb 20, 2017 at 5:30 PM, Richard Duivenvoorde
>> > > wrote:
>> >
>> > 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
>> >
>> >
>> >
>> > ___
>> > Qgis-developer mailing list
>> > Qgis-developer@lists.osgeo.org > sgeo.org>
>> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> > 
>> > Unsubscribe: https://lists.osgeo.org/mailma
>> n/listinfo/qgis-developer
>> > 
>> >
>> >
>> >
>> >
>> > ___
>> > Qgis-developer mailing list
>> > Qgis-developer@lists.osgeo.org
>> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> >
>>
>> J. Gustavo
>> --
>> Jorge Gustavo Rocha
>> Departamento de Informática
>> Universidade do Minho
>> 4710-057 Braga
>> Tel: +351 253604480
>> Fax: +351 253604471
>> Móvel: +351 910333888
>> skype: nabocudnosor
>> ___
>> Qgis-developer mailing list
>> Qgis-developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>
>
> ___
> Qgis-developer mailing list
> 

Re: [Qgis-developer] Future of standalone browser?

[Mathieu Pellerin]

I've never used the browser much, I can't say I would miss it if it's
retired.

The one thing I'd miss a bit is its capability at quickly previewing
datasets. I'm wondering if this could be somehow integrated into the QGIS'
browser dock (maybe now made possible following the major layer registry /
project refactoring which has taken place prior to 3.0?). Just like the
information panel, we could have a preview panel that renders a preview of
the vector/raster dataset.

Anyhow; +1 to see the standalone browser gone. :)

Math




On Mon, Feb 20, 2017 at 4:58 PM, Jorge Gustavo Rocha 
wrote:

> Hi,
>
> I never used it, and it is definitely a source of confusion in workshops.
>
> Regards,
>
> Jorge Gustavo
>
> Às 07:52 de 20-02-2017, Nathan Woodrow escreveu:
> > It's the same code, just in dock form.  I find the browser dock to be
> > super helpful but have never used the standalone version.
> >
> > On Mon, Feb 20, 2017 at 5:30 PM, Richard Duivenvoorde
> > > wrote:
> >
> > 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
> >
> >
> >
> > ___
> > Qgis-developer mailing list
> > Qgis-developer@lists.osgeo.org  osgeo.org>
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > 
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > 
> >
> >
> >
> >
> > ___
> > Qgis-developer mailing list
> > Qgis-developer@lists.osgeo.org
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> >
>
> J. Gustavo
> --
> Jorge Gustavo Rocha
> Departamento de Informática
> Universidade do Minho
> 4710-057 Braga
> Tel: +351 253604480
> Fax: +351 253604471
> Móvel: +351 910333888
> skype: nabocudnosor
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Future of standalone browser?

[Jorge Gustavo Rocha]

Hi,

I never used it, and it is definitely a source of confusion in workshops.

Regards,

Jorge Gustavo

Às 07:52 de 20-02-2017, Nathan Woodrow escreveu:
> It's the same code, just in dock form.  I find the browser dock to be
> super helpful but have never used the standalone version.
> 
> On Mon, Feb 20, 2017 at 5:30 PM, Richard Duivenvoorde
> > wrote:
> 
> 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
> 
> 
> 
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org 
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> 
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> 
> 
> 
> 
> 
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> 

J. Gustavo
-- 
Jorge Gustavo Rocha
Departamento de Informática
Universidade do Minho
4710-057 Braga
Tel: +351 253604480
Fax: +351 253604471
Móvel: +351 910333888
skype: nabocudnosor
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Future of standalone browser?

[Nyall Dawson]

On 20 February 2017 at 18:38, Jürgen E. Fischer  wrote:
> Hi Nyall,
>
> On Mon, 20. Feb 2017 at 08:33:13 +1000, Nyall Dawson wrote:
>> - Ignoring a tiny change I made a couple of days ago (to make the
>> preview use a pan tool), the last commit to standalone browser
>> (besides general api fixes) was... adding a new icon in may 2015.
>
> Um, one minute you request a change and the other you want to have it killed.
> I should have better used the time to finish it ;)

Sorry - that commit comment just started me thinking about what it's
future is. I actually didn't expect that there would be such strong
consensus to remove it, and thought that this discussion was more
likely to result in suggestions for improving it and several people
saying "i can't live without it!". Apologies if your effort on that
commit wasn't required...

Nyall



>
>
> Jürgen
>
> --
> Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
> Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
> Software Engineer   D-26506 Norden http://www.norbit.de
> QGIS release manager (PSC)  GermanyIRC: jef on FreeNode
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Future of standalone browser?

[Martin Dobias]

Hi Nyall

we (Radim and me) have added it long time ago within a small contract where
people wanted a simple standalone app for preview of data files (with an
assortment of other functionality that was not yet available in qgis app at
the time). Personally I have never been too attached to the idea of a
standalone browser, but thats how they wanted it.

Nowadays, the browser dock integrated inside qgis has richer functionality
and in general much more potential, so I think it would be fine to get rid
of the standalone browser - obviously it is barely used and not really
developed by anyone...

Cheers
Martin


On 20 Feb 2017 06:33, "Nyall Dawson"  wrote:

> Hi all,
>
> Just wanted to raise the discussion about the future of the standalone
> QGIS browser.
>
> The current situation (as I see it)
>
> - Ignoring a tiny change I made a couple of days ago (to make the
> preview use a pan tool), the last commit to standalone browser
> (besides general api fixes) was... adding a new icon in may 2015.
>
> - The standalone browser is very limited. There's lots of
> functionality available in the browser panel in the main app which
> isn't available in the standalone browser, like the search filter and
> everything in the right click context menus.
>
> - The current state of the standalone browser is "schizophrenic" at
> best. It's predominantly a read-only display of data, but with some
> extra random functionality in a toolbar (add wms server (what about
> wfs/wcs/etc?), create shapefile (what about spatialite/geopackage?),
> set layer projection)
>
> - The UI is very unpolished - eg there's a "header" header over the
> browser tree (http://mappinggis.com/wp-content/uploads/2015/11/5.png)
>
> I'm guessing, given this, that there's not a lot of demand for the
> standalone browser. This may either be due to lack of interest in this
> functionality in general, or else just a reflection of the current
> limited functionality available in it.
>
> 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?
>
> Nyall
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Future of standalone browser?

[Jürgen E . Fischer]

Hi Nyall,

On Mon, 20. Feb 2017 at 08:33:13 +1000, Nyall Dawson wrote:
> - Ignoring a tiny change I made a couple of days ago (to make the
> preview use a pan tool), the last commit to standalone browser
> (besides general api fixes) was... adding a new icon in may 2015.

Um, one minute you request a change and the other you want to have it killed.
I should have better used the time to finish it ;)


Jürgen

-- 
Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
Software Engineer   D-26506 Norden http://www.norbit.de
QGIS release manager (PSC)  GermanyIRC: jef on FreeNode 



pgpSmc2YfGtiQ.pgp
Description: PGP signature
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Future of standalone browser?

[Nyall Dawson]

On 20 February 2017 at 18:17, Paolo Cavallini  wrote:
> Il 20/02/2017 09:11, Régis Haubourg ha scritto:
>> Agreed here,
>> never used it, and it sends a wrong message saying Esri UX choices are
>> good enough to be copied. Let's get rid of it :)
>
> Agreed with most people here:
> * never used it myself
> * never seen used by anyone
> * very confusing for the users (especially when it had the same desktop
> icon as main app).
> On the other hand, I find the docked version superuseful and intuitive,
> although I agree with Richard that it should be streamlined, hopefully
> replacing the (too) many "Add this and that" buttons.
> Thanks Nyall for raising the issue.

Yes - I should have stressed this more. I love the in-app browser dock
and think it's vital to using QGIS. It's not going anywhere!

Seems like quite a consensus that the standalone browser should go.
Does anyone know the history here? I'd like to hear from the original
developer as to whether this was a funded project which could cause
issues with removal or if it's no longer required by them either...

Nyall
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Future of standalone browser?

[G. Allegri]

I agree for dropping it. Never used and many partecipants to our courses
were doubtful of its usefulness.

I guess it was meant to be similar to ESRI ArcCatalog but in that case a
lot more of functionalities should be implemented to give it a reason to
exist as a standalone sw.

giovanni

Il 20 feb 2017 09:12, "Régis Haubourg"  ha
scritto:

> Agreed here,
> never used it, and it sends a wrong message saying Esri UX choices are
> good enough to be copied. Let's get rid of it :)
> Régis
>
> 2017-02-20 8:52 GMT+01:00 Nathan Woodrow :
>
>> It's the same code, just in dock form.  I find the browser dock to be
>> super helpful but have never used the standalone version.
>>
>> On Mon, Feb 20, 2017 at 5:30 PM, Richard Duivenvoorde <
>> rdmaili...@duif.net> wrote:
>>
>>> 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
>>>
>>>
>>>
>>> ___
>>> Qgis-developer mailing list
>>> Qgis-developer@lists.osgeo.org
>>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>>
>>
>>
>> ___
>> Qgis-developer mailing list
>> Qgis-developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Future of standalone browser?

[Paolo Cavallini]

Il 20/02/2017 09:11, Régis Haubourg ha scritto:
> Agreed here, 
> never used it, and it sends a wrong message saying Esri UX choices are
> good enough to be copied. Let's get rid of it :)

Agreed with most people here:
* never used it myself
* never seen used by anyone
* very confusing for the users (especially when it had the same desktop
icon as main app).
On the other hand, I find the docked version superuseful and intuitive,
although I agree with Richard that it should be streamlined, hopefully
replacing the (too) many "Add this and that" buttons.
Thanks Nyall for raising the issue.
All the best.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all=IT=qgis,arcgis
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Future of standalone browser?

[Marco Bernasocchi]

On Sun, Feb 19, 2017 at 11:33 PM, Nyall Dawson 
wrote:

>Hi all,
>   Just wanted to raise the discussion about the future of the
>standalone QGIS browser.


Never used and never taught how to use it

ciaö
-- 
Marco Bernasocchi
OPENGIS.ch - berna.io - 27summits.ch



signature.asc
Description: OpenPGP digital signature
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Future of standalone browser?

[Régis Haubourg]

Agreed here,
never used it, and it sends a wrong message saying Esri UX choices are good
enough to be copied. Let's get rid of it :)
Régis

2017-02-20 8:52 GMT+01:00 Nathan Woodrow :

> It's the same code, just in dock form.  I find the browser dock to be
> super helpful but have never used the standalone version.
>
> On Mon, Feb 20, 2017 at 5:30 PM, Richard Duivenvoorde  > wrote:
>
>> 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
>>
>>
>>
>> ___
>> Qgis-developer mailing list
>> Qgis-developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Future of standalone browser?

[Nathan Woodrow]

It's the same code, just in dock form.  I find the browser dock to be super
helpful but have never used the standalone version.

On Mon, Feb 20, 2017 at 5:30 PM, Richard Duivenvoorde 
wrote:

> 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
>
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Future of standalone browser?

[Luca Manganelli]

On Sun, Feb 19, 2017 at 11:33 PM, Nyall Dawson 
wrote:

> Hi all,
>
> Just wanted to raise the discussion about the future of the standalone

QGIS browser.


​In our organization (about 100+ QGIS users), QGIS Browser is never used.​
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [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



___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Future of standalone browser?

[Frank Sokolic]

Hi all,

My feeling is that the standalone browser should be retired and not included in 
version 3.0. I don't think it provides any functionality that isn't already 
provided in QGIS and the browser panel and in my view is now obsolete.

As an aside, how easy would it be to adapt the standalone browser code to serve 
as a QGIS dialog for adding vector and raster layers? 

Frank.


- Original Message -
From: "Nyall Dawson" <nyall.daw...@gmail.com>
To: "qgis-developer" <qgis-developer@lists.osgeo.org>
Sent: Monday, 20 February, 2017 00:33:13
Subject: [Qgis-developer] Future of standalone browser?

Hi all,

Just wanted to raise the discussion about the future of the standalone
QGIS browser.

The current situation (as I see it)

- Ignoring a tiny change I made a couple of days ago (to make the
preview use a pan tool), the last commit to standalone browser
(besides general api fixes) was... adding a new icon in may 2015.

- The standalone browser is very limited. There's lots of
functionality available in the browser panel in the main app which
isn't available in the standalone browser, like the search filter and
everything in the right click context menus.

- The current state of the standalone browser is "schizophrenic" at
best. It's predominantly a read-only display of data, but with some
extra random functionality in a toolbar (add wms server (what about
wfs/wcs/etc?), create shapefile (what about spatialite/geopackage?),
set layer projection)

- The UI is very unpolished - eg there's a "header" header over the
browser tree (http://mappinggis.com/wp-content/uploads/2015/11/5.png)

I'm guessing, given this, that there's not a lot of demand for the
standalone browser. This may either be due to lack of interest in this
functionality in general, or else just a reflection of the current
limited functionality available in it.

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?

Nyall
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Future of standalone browser?

[Bo Victor Thomsen]

My POW:

Get rid of it and use developer ressources to reduce start-up time for 
the main QGIS program in stead.


Regards

Bo Victor Thomsen

Municipality of Frederikssund.


Den 19/02/17 kl. 23:33 skrev Nyall Dawson:

Hi all,

Just wanted to raise the discussion about the future of the standalone
QGIS browser.

The current situation (as I see it)

- Ignoring a tiny change I made a couple of days ago (to make the
preview use a pan tool), the last commit to standalone browser
(besides general api fixes) was... adding a new icon in may 2015.

- The standalone browser is very limited. There's lots of
functionality available in the browser panel in the main app which
isn't available in the standalone browser, like the search filter and
everything in the right click context menus.

- The current state of the standalone browser is "schizophrenic" at
best. It's predominantly a read-only display of data, but with some
extra random functionality in a toolbar (add wms server (what about
wfs/wcs/etc?), create shapefile (what about spatialite/geopackage?),
set layer projection)

- The UI is very unpolished - eg there's a "header" header over the
browser tree (http://mappinggis.com/wp-content/uploads/2015/11/5.png)

I'm guessing, given this, that there's not a lot of demand for the
standalone browser. This may either be due to lack of interest in this
functionality in general, or else just a reflection of the current
limited functionality available in it.

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?

Nyall
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Future of standalone browser?

[Tim Sutton]

Hi


> On 20 Feb 2017, at 12:33 AM, Nyall Dawson  wrote:
> 

8 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?

My (perhaps unpopular) point of view is that we should get rid of it:

* It is a regular source of confusion in training courses where people end up 
starting the browser instead of QGIS
* QGIS starts quickly enough that it is fairly trivial to use QGIS itself to 
have a quick preview of a dataset
* Whilst I regularly use the browser in QGIS itself, I have never had need to 
use it in standalone mode
* It's more stuff to maintain

I'd be far more interested in a QGIS browser based dialog that can be used as 
the basis for a unified 'add layer' dialog than the standalone version.

Maybe it would be good to hear from folks who have a good use case for keeping 
it to see what we are missing here

Regards

Tim

> 
> Nyall
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

—










Tim Sutton

Co-founder: Kartoza
Project chair: QGIS.org

Visit http://kartoza.com  to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

Skype: timlinux 
IRC: timlinux on #qgis at freenode.net

Kartoza is a merger between Linfiniti and Afrispatial

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Future of standalone browser?

[Nyall Dawson]

Hi all,

Just wanted to raise the discussion about the future of the standalone
QGIS browser.

The current situation (as I see it)

- Ignoring a tiny change I made a couple of days ago (to make the
preview use a pan tool), the last commit to standalone browser
(besides general api fixes) was... adding a new icon in may 2015.

- The standalone browser is very limited. There's lots of
functionality available in the browser panel in the main app which
isn't available in the standalone browser, like the search filter and
everything in the right click context menus.

- The current state of the standalone browser is "schizophrenic" at
best. It's predominantly a read-only display of data, but with some
extra random functionality in a toolbar (add wms server (what about
wfs/wcs/etc?), create shapefile (what about spatialite/geopackage?),
set layer projection)

- The UI is very unpolished - eg there's a "header" header over the
browser tree (http://mappinggis.com/wp-content/uploads/2015/11/5.png)

I'm guessing, given this, that there's not a lot of demand for the
standalone browser. This may either be due to lack of interest in this
functionality in general, or else just a reflection of the current
limited functionality available in it.

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?

Nyall
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer