Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[DelazJ]

Hi,

Thanks to this thread a new repository for UI/UX issues has been created
and several issues have already been reported (https://github.com/qgis/
qgis3_UIX_discussion/issues).
One of the objectives of that repository is to have people without
particular coding skills join and help on what they could. BUT as mentioned
also in the discussion, some work could not be moved forward without devs
inputs and guidings. I know that you are all busy but it'd be nice if, from
time to time, some devs could give a look to that repository and help for
questions or add their opinions.

Some questions are raised at:
https://github.com/qgis/qgis3_UIX_discussion/issues/19
https://github.com/qgis/qgis3_UIX_discussion/issues/14
https://github.com/qgis/qgis3_UIX_discussion/issues/11
and many others... that could be of interest for you..

Thanks for your availability,
Harrissou


2016-12-05 22:22 GMT+01:00 Chris Nicholas :

> I would really like an option to allow advanced users to manually just SET
> the extents of a vector layer when first adding it, so that a full
> table-scan can be avoided to derive that result.
>
> This still seems to happen, even though the “use estimated metadata” flag
> is checked, when first adding a layer.
>
> Gotta say that I too have built the new QGIS3 from source and it does seem
> quite usable … EXCELLENT work folks!!
>
> thanks -
> Chris
>
>
>
> On Dec 2, 2016, at 7:54 PM, Nyall Dawson  wrote:
>
>
>
> On 25 Nov 2016 9:22 PM, "Alexandre Neto"  wrote:
>
> Hello all,
>
> QGIS 3 is getting lots of love, and we are seeing new features being
> added, some legacy code being clean up, and so on. We are all aware that
> this will break the 2.x API, but now it's the time for it.
>
> So I wondered if this is not the perfect time to think about some UI/UX
> changes as well, as it will lead to more work in translation and
> Documentation. Could we do a list of UI/UX stuff that we could improve?
>
> I can think of a few things:
>
> *Consistency*
>  - "search", "select" and "browse" for browsing files;
> - "Add saved file to map", "Load into canvas when finished", "Open output
> file after running algorithm";
> - there is more of these for sure;
>
> *Help and Documentation*
> - Most of our help buttons lead to nowhere, we already talked about
> pointing them to the User's Manual online (although we would need a
> solution for working with it offline and in different languages)
>
> *Defaults*
> - Should default selection color not be opaque?
> - Showing only selected features vertexes by default?
> - Map template, we could provide a very simple template as default (I
> think there was already some discussion about this); Most people I see gets
> very confused when they see a completely empty page.
>
>
>
> Here's another idea for a great project t which doesn't involve
> c++/python: check through and delete unused png icons.
>
> A lot of the old png icons have been replaced with proper svg versions,
> but the pngs are still included and in some cases they are incorrectly used
> instead of the svg replacements.
>
> Identifying these would be a matter of going though each png icon in the
> repo and searching through the code (eg via "git grep mactionrefresh.png")
> to see if they are still used anywhere. (Ignore any hits in the resources
> files!) . If they aren't they can be safely removed. If they are, you could
> check whether a suitable svg replacement can be used.
>
> The more pngs we remove the easier it will be to identify which remaining
> icons require vector versions.
>
> Nyall
>
>
> Alexandre Neto
> --
> Alexandre Neto
> -
> @AlexNetoGeo
> http://sigsemgrilhetas.wordpress.com
> http://gisunchained.wordpress.com
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Chris Nicholas]

I would really like an option to allow advanced users to manually just SET the 
extents of a vector layer when first adding it, so that a full table-scan can 
be avoided to derive that result.

This still seems to happen, even though the “use estimated metadata” flag is 
checked, when first adding a layer.

Gotta say that I too have built the new QGIS3 from source and it does seem 
quite usable … EXCELLENT work folks!!

thanks -
Chris



> On Dec 2, 2016, at 7:54 PM, Nyall Dawson  wrote:
> 
> 
> 
> On 25 Nov 2016 9:22 PM, "Alexandre Neto"  > wrote:
> Hello all,
> 
> QGIS 3 is getting lots of love, and we are seeing new features being added, 
> some legacy code being clean up, and so on. We are all aware that this will 
> break the 2.x API, but now it's the time for it.
> 
> So I wondered if this is not the perfect time to think about some UI/UX 
> changes as well, as it will lead to more work in translation and 
> Documentation. Could we do a list of UI/UX stuff that we could improve?
> 
> I can think of a few things:
> 
> Consistency
>  - "search", "select" and "browse" for browsing files;
> - "Add saved file to map", "Load into canvas when finished", "Open output 
> file after running algorithm";
> - there is more of these for sure;
> 
> Help and Documentation
> - Most of our help buttons lead to nowhere, we already talked about pointing 
> them to the User's Manual online (although we would need a solution for 
> working with it offline and in different languages)
> 
> Defaults
> - Should default selection color not be opaque?
> - Showing only selected features vertexes by default?
> - Map template, we could provide a very simple template as default (I think 
> there was already some discussion about this); Most people I see gets very 
> confused when they see a completely empty page.
> 
> 
> Here's another idea for a great project t which doesn't involve c++/python: 
> check through and delete unused png icons.
> 
> A lot of the old png icons have been replaced with proper svg versions, but 
> the pngs are still included and in some cases they are incorrectly used 
> instead of the svg replacements.
> 
> Identifying these would be a matter of going though each png icon in the repo 
> and searching through the code (eg via "git grep mactionrefresh.png") to see 
> if they are still used anywhere. (Ignore any hits in the resources files!) . 
> If they aren't they can be safely removed. If they are, you could check 
> whether a suitable svg replacement can be used.
> 
> The more pngs we remove the easier it will be to identify which remaining 
> icons require vector versions.
> 
> Nyall
> 
> 
> Alexandre Neto
> --
> Alexandre Neto
> -
> @AlexNetoGeo
> http://sigsemgrilhetas.wordpress.com 
> http://gisunchained.wordpress.com 
> 
> 
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org 
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer 
> 
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer 
> 
> 
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Alessandro Pasotti]

Just a quick note about the bad layers handling dialog to say that it can
be fully overridden through python or C++ plugins, the API is fully exposed.

See: QgsProjectBadLayerHandler
https://qgis.org/api/classQgsProjectBadLayerHandler.html

Cheers.


Il 30/nov/2016 09:06, "Régis Haubourg"  ha
scritto:

> Hi all,
> another oldish part of our UI is the "handle bad layers" dialog.
> The UI win is having the project opened with just a warning, and the layer
> greyd + a red warning symbol + a way to change datasource in layer
> properties.
> I know, it is very ArcXX - like :)
>
> Régis
>
> 2016-11-30 8:09 GMT+01:00 Paolo Cavallini :
>
>> Hi Olivier,
>>
>> Il 29/11/2016 21:42, Olivier Dalang ha scritto:
>>
>> > - Consistency when creating layers. Currently each provider type has a
>> > slightly different ui. Also it's not possible to create certain type of
>> > layers from the ui (eg csv layers) even if they are now well supported.
>>
>> agreed. I'd add along this line that:
>> * the duality of DB layer management between the browser and the DB
>> Manager is a source of confusion; this is a complex task, but it would
>> be great to unify the two somehow
>> * the duality of adding layers through many different dedicated buttons
>> and through the Browser seems useless; my preference goes to the unified
>> Browser, adding the missing features to it.
>> 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: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Alexandre Neto]

A sáb, 3/12/2016, 03:54, Nyall Dawson  escreveu:

>
>
> Here's another idea for a great project t which doesn't involve
> c++/python: check through and delete unused png icons.
>
> A lot of the old png icons have been replaced with proper svg versions,
> but the pngs are still included and in some cases they are incorrectly used
> instead of the svg replacements.
>
> Identifying these would be a matter of going though each png icon in the
> repo and searching through the code (eg via "git grep mactionrefresh.png")
> to see if they are still used anywhere. (Ignore any hits in the resources
> files!) . If they aren't they can be safely removed. If they are, you could
> check whether a suitable svg replacement can be used.
>
> The more pngs we remove the easier it will be to identify which remaining
> icons require vector versions.
>
> Nyall
>
>
Great one. I will add it to the QGIS 3 UIX issues repo.

I like the idea of having easy to follow instructions in the issue for
anyone to pick it up and solve.


-- 
Alexandre Neto
-
@AlexNetoGeo
http://sigsemgrilhetas.wordpress.com
http://gisunchained.wordpress.com
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Christophe Damour]

+1 for this one !

--
Christophe

Le 03/12/2016 à 10:31, Paolo Cavallini a écrit :

Il 03/12/2016 04:54, Nyall Dawson ha scritto:


Here's another idea for a great project t which doesn't involve
c++/python: check through and delete unused png icons.

Hi all,
love these cleanups, thanks a lot for this.
Another possible improvement: labelling now requires two actions:
* select "Show laels etc." from a dropdown
* select a field or an expression for label content.
I think this can be combined in only one menu.
Thanks again.


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

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Paolo Cavallini]

Il 03/12/2016 04:54, Nyall Dawson ha scritto:

> Here's another idea for a great project t which doesn't involve
> c++/python: check through and delete unused png icons.

Hi all,
love these cleanups, thanks a lot for this.
Another possible improvement: labelling now requires two actions:
* select "Show laels etc." from a dropdown
* select a field or an expression for label content.
I think this can be combined in only one menu.
Thanks again.
-- 
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: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Nyall Dawson]

On 25 Nov 2016 9:22 PM, "Alexandre Neto"  wrote:

Hello all,

QGIS 3 is getting lots of love, and we are seeing new features being added,
some legacy code being clean up, and so on. We are all aware that this will
break the 2.x API, but now it's the time for it.

So I wondered if this is not the perfect time to think about some UI/UX
changes as well, as it will lead to more work in translation and
Documentation. Could we do a list of UI/UX stuff that we could improve?

I can think of a few things:

*Consistency*
 - "search", "select" and "browse" for browsing files;
- "Add saved file to map", "Load into canvas when finished", "Open output
file after running algorithm";
- there is more of these for sure;

*Help and Documentation*
- Most of our help buttons lead to nowhere, we already talked about
pointing them to the User's Manual online (although we would need a
solution for working with it offline and in different languages)

*Defaults*
- Should default selection color not be opaque?
- Showing only selected features vertexes by default?
- Map template, we could provide a very simple template as default (I think
there was already some discussion about this); Most people I see gets very
confused when they see a completely empty page.



Here's another idea for a great project t which doesn't involve c++/python:
check through and delete unused png icons.

A lot of the old png icons have been replaced with proper svg versions, but
the pngs are still included and in some cases they are incorrectly used
instead of the svg replacements.

Identifying these would be a matter of going though each png icon in the
repo and searching through the code (eg via "git grep mactionrefresh.png")
to see if they are still used anywhere. (Ignore any hits in the resources
files!) . If they aren't they can be safely removed. If they are, you could
check whether a suitable svg replacement can be used.

The more pngs we remove the easier it will be to identify which remaining
icons require vector versions.

Nyall


Alexandre Neto
-- 
Alexandre Neto
-
@AlexNetoGeo
http://sigsemgrilhetas.wordpress.com
http://gisunchained.wordpress.com

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

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Alexandre Neto]

Richard, I can add issues. so we are good. thanks!

Richard Duivenvoorde  escreveu no dia sexta, 2/12/2016
às 09:05:

>
> Ok, done:
>
> https://github.com/qgis/qgis3_UIX_discussion
>
> @Alexandre, can you please check if you can add/edit issues now? Without
> giving you commit rights?
>
> Then if that is ok (and everybody can at least create issues) I give you
> commit rights so you can close issues.
>
> Let's see if this works!
>
> Regards,
>
> Richard
>
> On 02-12-16 09:47, Alexandre Neto wrote:
> > Richard,
> >
> > Thanks!
> >
> > I can do the gardening.
> >
> > Alex Neto
> >
> >
> > A sex, 2/12/2016, 08:45, Richard Duivenvoorde  > > escreveu:
> >
> > On 01-12-16 19:48, Nyall Dawson wrote:
> > >
> > >
> > > On 1 Dec 2016 11:28 PM, "DelazJ"  > 
> > > >> wrote:
> > >
> > > Hi,
> > >
> > > Apologies if I misread some comments above but I'm afraid we
> are
> > > moving from what Alexandre was mentionning in his first post
> > (in any
> > > case, the way I understood it): add consistency to the
> > features QGIS
> > > already provide (and among those features). While I'm also
> > > interested in some requests (such as "bad layers handling" - I
> > like
> > > the way InDesign manage broken links), I wonder if this kind of
> > > request should not be kept for the hub as it's a new feature.
> > >
> > > Richard mentioned a place where 3.0 requests were listed. Is
> > it this
> > > one https://github.com/qgis/qgis3.0_api/
> > >  ? While it's supposed
> to be
> > > api oriented, maybe we can extend it and allow to list/discuss
> and
> > > filter (in a more organized way) all UI/UX thingies that worth
> > a fix
> > > before 3.0 lands.
> > > In this way, anyone that wants to help can pick an issue and
> ask
> > > pointers from devs if/when needed.
> > >
> > >
> > > I'm not a fan of mixing the two. Maybe a new repo could be made
> > for 3.0
> > > ui suggestions, but just like this thread it's going to get filled
> > with
> > > a thousand unrelated feature requests ;)
> > >
> > > The api repo is a nice clean list of stuff that HAS to be done
> before
> > > 3.0 release or we miss the opportunity. Ui can always be addressed
> > in a
> > > future 3.x release.
> >
> > Ok, what about the following:
> >
> > - I create an Repo: https://github.com/qgis/qgis3.0_UIX solely for
> the
> > creation/discussion of ideas as tickets?
> >
> > 'Some people' have to do some gardening there then, like cleaning up
> > duplicates etc. Volunteers for that? I can give you on that repo
> then.
> >
> > Regards,
> >
> > Richard Duivenvoorde
> >
> >
> > ___
> > Qgis-developer mailing list
> > Qgis-developer@lists.osgeo.org  Qgis-developer@lists.osgeo.org>
> > List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> >
> > --
> > Alexandre Neto
> > -
> > @AlexNetoGeo
> > http://sigsemgrilhetas.wordpress.com
> > http://gisunchained.wordpress.com
> >
> >
> > ___
> > Qgis-developer mailing list
> > Qgis-developer@lists.osgeo.org
> > List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> >
>
> --
Alexandre Neto
-
@AlexNetoGeo
http://sigsemgrilhetas.wordpress.com
http://gisunchained.wordpress.com
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Richard Duivenvoorde]

Ok, done:

https://github.com/qgis/qgis3_UIX_discussion

@Alexandre, can you please check if you can add/edit issues now? Without 
giving you commit rights?


Then if that is ok (and everybody can at least create issues) I give you 
commit rights so you can close issues.


Let's see if this works!

Regards,

Richard

On 02-12-16 09:47, Alexandre Neto wrote:

Richard,

Thanks!

I can do the gardening.

Alex Neto


A sex, 2/12/2016, 08:45, Richard Duivenvoorde > escreveu:

On 01-12-16 19:48, Nyall Dawson wrote:
>
>
> On 1 Dec 2016 11:28 PM, "DelazJ" 
> >> wrote:
>
> Hi,
>
> Apologies if I misread some comments above but I'm afraid we are
> moving from what Alexandre was mentionning in his first post
(in any
> case, the way I understood it): add consistency to the
features QGIS
> already provide (and among those features). While I'm also
> interested in some requests (such as "bad layers handling" - I
like
> the way InDesign manage broken links), I wonder if this kind of
> request should not be kept for the hub as it's a new feature.
>
> Richard mentioned a place where 3.0 requests were listed. Is
it this
> one https://github.com/qgis/qgis3.0_api/
>  ? While it's supposed to be
> api oriented, maybe we can extend it and allow to list/discuss and
> filter (in a more organized way) all UI/UX thingies that worth
a fix
> before 3.0 lands.
> In this way, anyone that wants to help can pick an issue and ask
> pointers from devs if/when needed.
>
>
> I'm not a fan of mixing the two. Maybe a new repo could be made
for 3.0
> ui suggestions, but just like this thread it's going to get filled
with
> a thousand unrelated feature requests ;)
>
> The api repo is a nice clean list of stuff that HAS to be done before
> 3.0 release or we miss the opportunity. Ui can always be addressed
in a
> future 3.x release.

Ok, what about the following:

- I create an Repo: https://github.com/qgis/qgis3.0_UIX solely for the
creation/discussion of ideas as tickets?

'Some people' have to do some gardening there then, like cleaning up
duplicates etc. Volunteers for that? I can give you on that repo then.

Regards,

Richard Duivenvoorde


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

--
Alexandre Neto
-
@AlexNetoGeo
http://sigsemgrilhetas.wordpress.com
http://gisunchained.wordpress.com


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



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

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Nyall Dawson]

On 2 December 2016 at 18:45, Richard Duivenvoorde  wrote:
> On 01-12-16 19:48, Nyall Dawson wrote:
>>
>>
>>
>> On 1 Dec 2016 11:28 PM, "DelazJ" > > wrote:
>>
>> Hi,
>>
>> Apologies if I misread some comments above but I'm afraid we are
>> moving from what Alexandre was mentionning in his first post (in any
>> case, the way I understood it): add consistency to the features QGIS
>> already provide (and among those features). While I'm also
>> interested in some requests (such as "bad layers handling" - I like
>> the way InDesign manage broken links), I wonder if this kind of
>> request should not be kept for the hub as it's a new feature.
>>
>> Richard mentioned a place where 3.0 requests were listed. Is it this
>> one https://github.com/qgis/qgis3.0_api/
>>  ? While it's supposed to be
>> api oriented, maybe we can extend it and allow to list/discuss and
>> filter (in a more organized way) all UI/UX thingies that worth a fix
>> before 3.0 lands.
>> In this way, anyone that wants to help can pick an issue and ask
>> pointers from devs if/when needed.
>>
>>
>> I'm not a fan of mixing the two. Maybe a new repo could be made for 3.0
>> ui suggestions, but just like this thread it's going to get filled with
>> a thousand unrelated feature requests ;)
>>
>> The api repo is a nice clean list of stuff that HAS to be done before
>> 3.0 release or we miss the opportunity. Ui can always be addressed in a
>> future 3.x release.
>
>
> Ok, what about the following:
>
> - I create an Repo: https://github.com/qgis/qgis3.0_UIX solely for the
> creation/discussion of ideas as tickets?
>
> 'Some people' have to do some gardening there then, like cleaning up
> duplicates etc. Volunteers for that? I can give you on that repo then.

Sounds good to me!

Nyall

>
> Regards,
>
> Richard Duivenvoorde
>
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Alexandre Neto]

Richard,

Thanks!

I can do the gardening.

Alex Neto

A sex, 2/12/2016, 08:45, Richard Duivenvoorde 
escreveu:

> On 01-12-16 19:48, Nyall Dawson wrote:
> >
> >
> > On 1 Dec 2016 11:28 PM, "DelazJ"  > > wrote:
> >
> > Hi,
> >
> > Apologies if I misread some comments above but I'm afraid we are
> > moving from what Alexandre was mentionning in his first post (in any
> > case, the way I understood it): add consistency to the features QGIS
> > already provide (and among those features). While I'm also
> > interested in some requests (such as "bad layers handling" - I like
> > the way InDesign manage broken links), I wonder if this kind of
> > request should not be kept for the hub as it's a new feature.
> >
> > Richard mentioned a place where 3.0 requests were listed. Is it this
> > one https://github.com/qgis/qgis3.0_api/
> >  ? While it's supposed to be
> > api oriented, maybe we can extend it and allow to list/discuss and
> > filter (in a more organized way) all UI/UX thingies that worth a fix
> > before 3.0 lands.
> > In this way, anyone that wants to help can pick an issue and ask
> > pointers from devs if/when needed.
> >
> >
> > I'm not a fan of mixing the two. Maybe a new repo could be made for 3.0
> > ui suggestions, but just like this thread it's going to get filled with
> > a thousand unrelated feature requests ;)
> >
> > The api repo is a nice clean list of stuff that HAS to be done before
> > 3.0 release or we miss the opportunity. Ui can always be addressed in a
> > future 3.x release.
>
> Ok, what about the following:
>
> - I create an Repo: https://github.com/qgis/qgis3.0_UIX solely for the
> creation/discussion of ideas as tickets?
>
> 'Some people' have to do some gardening there then, like cleaning up
> duplicates etc. Volunteers for that? I can give you on that repo then.
>
> Regards,
>
> Richard Duivenvoorde
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

-- 
Alexandre Neto
-
@AlexNetoGeo
http://sigsemgrilhetas.wordpress.com
http://gisunchained.wordpress.com
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Richard Duivenvoorde]

On 01-12-16 19:48, Nyall Dawson wrote:



On 1 Dec 2016 11:28 PM, "DelazJ" > wrote:

Hi,

Apologies if I misread some comments above but I'm afraid we are
moving from what Alexandre was mentionning in his first post (in any
case, the way I understood it): add consistency to the features QGIS
already provide (and among those features). While I'm also
interested in some requests (such as "bad layers handling" - I like
the way InDesign manage broken links), I wonder if this kind of
request should not be kept for the hub as it's a new feature.

Richard mentioned a place where 3.0 requests were listed. Is it this
one https://github.com/qgis/qgis3.0_api/
 ? While it's supposed to be
api oriented, maybe we can extend it and allow to list/discuss and
filter (in a more organized way) all UI/UX thingies that worth a fix
before 3.0 lands.
In this way, anyone that wants to help can pick an issue and ask
pointers from devs if/when needed.


I'm not a fan of mixing the two. Maybe a new repo could be made for 3.0
ui suggestions, but just like this thread it's going to get filled with
a thousand unrelated feature requests ;)

The api repo is a nice clean list of stuff that HAS to be done before
3.0 release or we miss the opportunity. Ui can always be addressed in a
future 3.x release.


Ok, what about the following:

- I create an Repo: https://github.com/qgis/qgis3.0_UIX solely for the 
creation/discussion of ideas as tickets?


'Some people' have to do some gardening there then, like cleaning up 
duplicates etc. Volunteers for that? I can give you on that repo then.


Regards,

Richard Duivenvoorde


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

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Nyall Dawson]

On 1 Dec 2016 11:28 PM, "DelazJ"  wrote:

Hi,

Apologies if I misread some comments above but I'm afraid we are moving
from what Alexandre was mentionning in his first post (in any case, the way
I understood it): add consistency to the features QGIS already provide (and
among those features). While I'm also interested in some requests (such as
"bad layers handling" - I like the way InDesign manage broken links), I
wonder if this kind of request should not be kept for the hub as it's a new
feature.

Richard mentioned a place where 3.0 requests were listed. Is it this one
https://github.com/qgis/qgis3.0_api/ ? While it's supposed to be api
oriented, maybe we can extend it and allow to list/discuss and filter (in a
more organized way) all UI/UX thingies that worth a fix before 3.0 lands.
In this way, anyone that wants to help can pick an issue and ask pointers
from devs if/when needed.


I'm not a fan of mixing the two. Maybe a new repo could be made for 3.0 ui
suggestions, but just like this thread it's going to get filled with a
thousand unrelated feature requests ;)

The api repo is a nice clean list of stuff that HAS to be done before 3.0
release or we miss the opportunity. Ui can always be addressed in a future
3.x release.

Nyall


my2cts,
Harrissou


2016-11-30 18:56 GMT+01:00 Spencer Gardner :

> (Sorry if this double posts. Forgot subject line last time)
>
> >Actually, I don't dislike the dialog of handlings bad layers. Maybe keeping
> >the layers could be a setting in that dialog. Another cool thing is if once
> >you correct one layer data source, it would be smart enough to fix layers
> >in a similar data source.
>
> I think I'd be OK with that. My biggest problem is wanting to keep the layer 
> in my map document even if the reference is bad so that I don't lose styling 
> or other information.
>
> Also +1 for intelligent fixing of layers with similar data source.
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>


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

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[DelazJ]

Hi,

Apologies if I misread some comments above but I'm afraid we are moving
from what Alexandre was mentionning in his first post (in any case, the way
I understood it): add consistency to the features QGIS already provide (and
among those features). While I'm also interested in some requests (such as
"bad layers handling" - I like the way InDesign manage broken links), I
wonder if this kind of request should not be kept for the hub as it's a new
feature.

Richard mentioned a place where 3.0 requests were listed. Is it this one
https://github.com/qgis/qgis3.0_api/ ? While it's supposed to be api
oriented, maybe we can extend it and allow to list/discuss and filter (in a
more organized way) all UI/UX thingies that worth a fix before 3.0 lands.
In this way, anyone that wants to help can pick an issue and ask pointers
from devs if/when needed.

my2cts,
Harrissou


2016-11-30 18:56 GMT+01:00 Spencer Gardner :

> (Sorry if this double posts. Forgot subject line last time)
>
> >Actually, I don't dislike the dialog of handlings bad layers. Maybe keeping
> >the layers could be a setting in that dialog. Another cool thing is if once
> >you correct one layer data source, it would be smart enough to fix layers
> >in a similar data source.
>
> I think I'd be OK with that. My biggest problem is wanting to keep the layer 
> in my map document even if the reference is bad so that I don't lose styling 
> or other information.
>
> Also +1 for intelligent fixing of layers with similar data source.
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Spencer Gardner]

>Another one I forgot to add (a bit unrelated):
>
>- lots of the processing algorithms don't correctly handle z/m
>geometries and the changes are often trivial to allow them to. I'd
>love to see someone generate a list (based off master) of all the
>algorithms which currently don't maintain z and m values and which
>should.
>
>Nyall

Am I remembering correctly that imports via DBManager also don't
handle z/m geometries? Seems like that should be an easy fix too.

I'll volunteer to identify the offending processing algorithms. We're
talking QGIS algorithms, right? Not from GRASS or other providers? I
might need some guidance but it seems pretty straightforward.

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

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Spencer Gardner]

>Hi all,
>another oldish part of our UI is the "handle bad layers" dialog.
>The UI win is having the project opened with just a warning, and the layer
>greyd + a red warning symbol + a way to change datasource in layer
>properties.
>I know, it is very ArcXX - like :)
>
>Régis

+1. I'm OK with a solution other than the Arc way, but the current
handling of bad layers is definitely in need of a rethink.
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Régis Haubourg]

Hi all,
another oldish part of our UI is the "handle bad layers" dialog.
The UI win is having the project opened with just a warning, and the layer
greyd + a red warning symbol + a way to change datasource in layer
properties.
I know, it is very ArcXX - like :)

Régis

2016-11-30 8:09 GMT+01:00 Paolo Cavallini :

> Hi Olivier,
>
> Il 29/11/2016 21:42, Olivier Dalang ha scritto:
>
> > - Consistency when creating layers. Currently each provider type has a
> > slightly different ui. Also it's not possible to create certain type of
> > layers from the ui (eg csv layers) even if they are now well supported.
>
> agreed. I'd add along this line that:
> * the duality of DB layer management between the browser and the DB
> Manager is a source of confusion; this is a complex task, but it would
> be great to unify the two somehow
> * the duality of adding layers through many different dedicated buttons
> and through the Browser seems useless; my preference goes to the unified
> Browser, adding the missing features to it.
> 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: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Paolo Cavallini]

Hi Olivier,

Il 29/11/2016 21:42, Olivier Dalang ha scritto:

> - Consistency when creating layers. Currently each provider type has a
> slightly different ui. Also it's not possible to create certain type of
> layers from the ui (eg csv layers) even if they are now well supported.

agreed. I'd add along this line that:
* the duality of DB layer management between the browser and the DB
Manager is a source of confusion; this is a complex task, but it would
be great to unify the two somehow
* the duality of adding layers through many different dedicated buttons
and through the Browser seems useless; my preference goes to the unified
Browser, adding the missing features to it.
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: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Olivier Dalang]

Hi,

Yes it would really be awesome if the UI also got it's share of work. There
were so many new features added to QGIS on every last version that some
parts of the UI suffered and would really benefit from being rethought a
bit more globally.


I would add this to the list:


- Consistency when creating layers. Currently each provider type has a
slightly different ui. Also it's not possible to create certain type of
layers from the ui (eg csv layers) even if they are now well supported.

- Go through all .ui files and make sure all elements are well aligned and
have correct size policies. On small screens it happens to have windows
that don't scroll correctly (so that you can't click on the OK button).

- The style/symbol dialog for vector layers got really complex. Quite a lot
of features were added over time and the dialog is now pretty confuse.
There is an old thread were we discussed it, I think a lot of the points
still hold. The thread wes "Redesign vector layer style dialog - Was:
Redesign stylemanager", I don't find it online though ?! This issue lists
some of the points of the threads : https://hub.qgis.org/issues/7556

- We also already discussed that, but I find the difference between a layer
and a datasource is not made clear enough in the UI. The most critical
place where this confusion happen is the ability to modify columns of
vector data from within the layer properties window. I think the
distinction between these two concepts should be made more obvious in the
UI : have places where you modify data representation (the layer properties
window), and places where you modify actual data (the attribute manager).


Cheers,

Olivier

2016-11-28 22:45 GMT+00:00 Nyall Dawson :

> On 28 November 2016 at 21:59, Alexandre Neto 
> wrote:
> > Hi Nyall! Thank you for your reply.
> >
> > A sex, 25/11/2016, 22:09, Nyall Dawson 
> escreveu:
> >>
> >>
> >> I love it!
> >>
> >> Stuff like this is a great jumping in point where anyone can get
> >> involved. It's just a matter of trawling through all the dialogs and
> >> collating a list of strings which need changing. If that was done then
> >> someone with commit rights could fix these in a couple of minutes. The
> >> hard bit (and the bit where ANYONE can help) is making the list in the
> >> first place.
> >
> >
> > I will gladly work on that list, but I was hoping that, under the idea of
> > "give a man a fish and you feed him for a day; teach a man to fish and
> you
> > feed him for a lifetime", with a gentle push from a developer, I could
> > directly fix some of the problems.
>
> Even better! Just ping if you need assistance :)
>
> Nyall
>
>
> >
> >>
> >> Some more suggestions (which again, anyone could help with identifying):
> >>
> >> - replacing "non standard" icons. We still have some inconsitently
> >> used icons (such as the expression builder icon) used throughout qgis.
> >> - dialogs which violate hig conventions:
> >> - use of ":" at the end of strings
> >> - bad tab order
> >> - group boxes with just one widget
> >> - bad/inconsistent capitalisation in strings, dialog titles, and
> tooltips
> >> - widgets without tooltips (or non helpful tooltips)
> >
> >
> > Maybe I will start by gathering a list of issues to search for, before I
> > start looking into each dialog. Those above are all good candidates.
> >
> >>
> >>
> >>
> >>
> >> These are also issues for plugins, so collating lists and opening bugs
> >> against plugins would also help.
> >>
> >> >
> >> > Help and Documentation
> >> > - Most of our help buttons lead to nowhere, we already talked about
> >> > pointing
> >> > them to the User's Manual online (although we would need a solution
> for
> >> > working with it offline and in different languages)
> >> >
> >> > Defaults
> >> > - Should default selection color not be opaque?
> >> > - Showing only selected features vertexes by default?
> >> +1
> >>
> >> > - Map template, we could provide a very simple template as default (I
> >> > think
> >> > there was already some discussion about this); Most people I see gets
> >> > very
> >> > confused when they see a completely empty page.
> >>
> >> Depends how it's done. I don't think it should always open with a
> >> template, but including some nice templates with qgis would be a good
> >> start.
> >
> >
> > We could have a few options when creating a new print composition
> keeping an
> > "empty" option on the top.
> > - Empty ()
> > - A4 landscape
> > - A4 portrait
> > - plus list of recent user's templates
> >
> >>
> >>
> >> Another idea I'd love to see for 3.0 is switching the main ui to using
> >> monochrome "symbolic" icons. I think this could really refresh the
> >> interface and avoid the ui from taking attention away for the content
> >> (ie, the pretty map you're making). I tried making a script to auto
> >> convert the icons as a test and ended up with a horrendous result
> >> which had to be 

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Nyall Dawson]

On 28 November 2016 at 21:59, Alexandre Neto  wrote:
> Hi Nyall! Thank you for your reply.
>
> A sex, 25/11/2016, 22:09, Nyall Dawson  escreveu:
>>
>>
>> I love it!
>>
>> Stuff like this is a great jumping in point where anyone can get
>> involved. It's just a matter of trawling through all the dialogs and
>> collating a list of strings which need changing. If that was done then
>> someone with commit rights could fix these in a couple of minutes. The
>> hard bit (and the bit where ANYONE can help) is making the list in the
>> first place.
>
>
> I will gladly work on that list, but I was hoping that, under the idea of
> "give a man a fish and you feed him for a day; teach a man to fish and you
> feed him for a lifetime", with a gentle push from a developer, I could
> directly fix some of the problems.

Even better! Just ping if you need assistance :)

Nyall


>
>>
>> Some more suggestions (which again, anyone could help with identifying):
>>
>> - replacing "non standard" icons. We still have some inconsitently
>> used icons (such as the expression builder icon) used throughout qgis.
>> - dialogs which violate hig conventions:
>> - use of ":" at the end of strings
>> - bad tab order
>> - group boxes with just one widget
>> - bad/inconsistent capitalisation in strings, dialog titles, and tooltips
>> - widgets without tooltips (or non helpful tooltips)
>
>
> Maybe I will start by gathering a list of issues to search for, before I
> start looking into each dialog. Those above are all good candidates.
>
>>
>>
>>
>>
>> These are also issues for plugins, so collating lists and opening bugs
>> against plugins would also help.
>>
>> >
>> > Help and Documentation
>> > - Most of our help buttons lead to nowhere, we already talked about
>> > pointing
>> > them to the User's Manual online (although we would need a solution for
>> > working with it offline and in different languages)
>> >
>> > Defaults
>> > - Should default selection color not be opaque?
>> > - Showing only selected features vertexes by default?
>> +1
>>
>> > - Map template, we could provide a very simple template as default (I
>> > think
>> > there was already some discussion about this); Most people I see gets
>> > very
>> > confused when they see a completely empty page.
>>
>> Depends how it's done. I don't think it should always open with a
>> template, but including some nice templates with qgis would be a good
>> start.
>
>
> We could have a few options when creating a new print composition keeping an
> "empty" option on the top.
> - Empty ()
> - A4 landscape
> - A4 portrait
> - plus list of recent user's templates
>
>>
>>
>> Another idea I'd love to see for 3.0 is switching the main ui to using
>> monochrome "symbolic" icons. I think this could really refresh the
>> interface and avoid the ui from taking attention away for the content
>> (ie, the pretty map you're making). I tried making a script to auto
>> convert the icons as a test and ended up with a horrendous result
>> which had to be burned in a furnace and scattered on the four winds.
>
>
> It would be nice if we could get some graphic designer to make them
> distinctive enough.
>
> Also, it would be nice if special care is taken so that they work with the
> the dark theme.
>
>>
>> Nyall
>>
>>
>
> Alex Neto
> --
> Alexandre Neto
> -
> @AlexNetoGeo
> http://sigsemgrilhetas.wordpress.com
> http://gisunchained.wordpress.com
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Matthias Kuhn]

Hi Alex

On 11/28/2016 12:59 PM, Alexandre Neto wrote:
> Hi Nyall! Thank you for your reply.
> 
> A sex, 25/11/2016, 22:09, Nyall Dawson  > escreveu:
> 
> 
> I love it!
> 
> Stuff like this is a great jumping in point where anyone can get
> involved. It's just a matter of trawling through all the dialogs and
> collating a list of strings which need changing. If that was done then
> someone with commit rights could fix these in a couple of minutes. The
> hard bit (and the bit where ANYONE can help) is making the list in the
> first place.
> 
> 
> I will gladly work on that list, but I was hoping that, under the idea
> of "give a man a fish and you feed him for a day; teach a man to fish
> and you feed him for a lifetime", with a gentle push from a developer, I
> could directly fix some of the problems.

Pick your choice, try using Qt Designer and a text editor and full text
search to fix whatever you want. If you run into walls, ping me (or
someone else) here or on gitter. I'll be happy to provide you with trawl
nets if possible ;)

> 
> > - Map template, we could provide a very simple template as default
> (I think
> > there was already some discussion about this); Most people I see
> gets very
> > confused when they see a completely empty page.
> 
> Depends how it's done. I don't think it should always open with a
> template, but including some nice templates with qgis would be a good
> start.
> 
> 
> We could have a few options when creating a new print composition
> keeping an "empty" option on the top.
> - Empty ()
> - A4 landscape
> - A4 portrait
> - plus list of recent user's templates

Nice idea!

> 
> 
> 
> Another idea I'd love to see for 3.0 is switching the main ui to using
> monochrome "symbolic" icons. I think this could really refresh the
> interface and avoid the ui from taking attention away for the content
> (ie, the pretty map you're making). I tried making a script to auto
> convert the icons as a test and ended up with a horrendous result
> which had to be burned in a furnace and scattered on the four winds.
> 
> 
> It would be nice if we could get some graphic designer to make them
> distinctive enough.

Any chance to ask your employer to jump in here? IIRC they also helped
with someone for the website redesign. And after the shiny charts in a
blog post from last week this could be a nice move to live up a bit
closer to the contribution share which this post pretended they hold in
QGIS ;P

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

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Paolo Cavallini]

Il 28/11/2016 12:59, Alexandre Neto ha scritto:

> We could have a few options when creating a new print composition
> keeping an "empty" option on the top.
> - Empty ()
> - A4 landscape
> - A4 portrait
> - plus list of recent user's templates

agreed, this will make life easier for many.
thanks.

-- 
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: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Alexandre Neto]

Hi Nyall! Thank you for your reply.

A sex, 25/11/2016, 22:09, Nyall Dawson  escreveu:


I love it!

Stuff like this is a great jumping in point where anyone can get
involved. It's just a matter of trawling through all the dialogs and
collating a list of strings which need changing. If that was done then
someone with commit rights could fix these in a couple of minutes. The
hard bit (and the bit where ANYONE can help) is making the list in the
first place.


I will gladly work on that list, but I was hoping that, under the idea of
"give a man a fish and you feed him for a day; teach a man to fish and you
feed him for a lifetime", with a gentle push from a developer, I could
directly fix some of the problems.


Some more suggestions (which again, anyone could help with identifying):

- replacing "non standard" icons. We still have some inconsitently
used icons (such as the expression builder icon) used throughout qgis.
- dialogs which violate hig conventions:
- use of ":" at the end of strings
- bad tab order
- group boxes with just one widget
- bad/inconsistent capitalisation in strings, dialog titles, and tooltips
- widgets without tooltips (or non helpful tooltips)


Maybe I will start by gathering a list of issues to search for, before I
start looking into each dialog. Those above are all good candidates.





These are also issues for plugins, so collating lists and opening bugs
against plugins would also help.

>
> Help and Documentation
> - Most of our help buttons lead to nowhere, we already talked about
pointing
> them to the User's Manual online (although we would need a solution for
> working with it offline and in different languages)
>
> Defaults
> - Should default selection color not be opaque?
> - Showing only selected features vertexes by default?
+1

> - Map template, we could provide a very simple template as default (I
think
> there was already some discussion about this); Most people I see gets very
> confused when they see a completely empty page.

Depends how it's done. I don't think it should always open with a
template, but including some nice templates with qgis would be a good
start.


We could have a few options when creating a new print composition keeping
an "empty" option on the top.
- Empty ()
- A4 landscape
- A4 portrait
- plus list of recent user's templates



Another idea I'd love to see for 3.0 is switching the main ui to using
monochrome "symbolic" icons. I think this could really refresh the
interface and avoid the ui from taking attention away for the content
(ie, the pretty map you're making). I tried making a script to auto
convert the icons as a test and ended up with a horrendous result
which had to be burned in a furnace and scattered on the four winds.


It would be nice if we could get some graphic designer to make them
distinctive enough.

Also, it would be nice if special care is taken so that they work with the
the dark theme.


Nyall



Alex Neto
-- 
Alexandre Neto
-
@AlexNetoGeo
http://sigsemgrilhetas.wordpress.com
http://gisunchained.wordpress.com
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Anita Graser]

On Fri, Nov 25, 2016 at 10:40 PM, Tim Sutton  wrote:
>
> This is definately a love/hate topic, but as I got used to the ribbons in
> MS-Software, I really see them now as a way to partially reduce the
> clutter, though I have no real idea how to intelligently group the stuff
> (but I'm sure enough brilliant people around here could have good ideas)
> And this would really give QGIS3 a maximum of a "fresh" look.
>
>
> I thought I really disliked ribbons, but the ribbon interface that Marco
> and Sandro from Sourcepole demonstrated in Girona really appealed to me. I
> think if it is carefully done it could be nice. However I don't know it it
> makes sense for general use cases where users probably value screen real
> estate over big easy to click buttons. In Sourcepole's case they had a very
> well defined audience and specific activities they needed to perform I
> thought it made a lot of sense.
>

​I also liked the ​customized UI by Sourcepole but Tim is right, they had
to fit a really limited set of functionality.

Additonally, for example, the Powerpoint ribbon is as high as four rows of
toolbars on my notebook. And the ribbons cannot be arrange vertically on
the left or right side. This leaves very little map space, particularly on
notebooks.​



​Best wishes,
Anita​

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

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Tim Sutton]

Hi

> 
> 
> Another one I forgot to add (a bit unrelated):
> 
> - lots of the processing algorithms don't correctly handle z/m
> geometries and the changes are often trivial to allow them to. I'd
> love to see someone generate a list (based off master) of all the
> algorithms which currently don't maintain z and m values and which
> should.
> 

And another big one would be to make QGIS expressions the standard way for 
entering expressions (thinking about raster calculator and layer filter 
expression dialog for example). Maybe the expression dialog should have a 'SQL' 
and "QGIS' mode so that it can use the same UI but constrain expressions to 
valid SQL if the recipient of the expression requires valid SQL.

Regards

Tim


> Nyall
> 
> 
>> 
>> 
>> These are also issues for plugins, so collating lists and opening bugs
>> against plugins would also help.
>> 
>> 
>>> 
>>> Help and Documentation
>>> - Most of our help buttons lead to nowhere, we already talked about pointing
>>> them to the User's Manual online (although we would need a solution for
>>> working with it offline and in different languages)
>>> 
>>> Defaults
>>> - Should default selection color not be opaque?
>>> - Showing only selected features vertexes by default?
>> +1
>> 
>>> - Map template, we could provide a very simple template as default (I think
>>> there was already some discussion about this); Most people I see gets very
>>> confused when they see a completely empty page.
>> 
>> Depends how it's done. I don't think it should always open with a
>> template, but including some nice templates with qgis would be a good
>> start.
>> 
>> 
>> Another idea I'd love to see for 3.0 is switching the main ui to using
>> monochrome "symbolic" icons. I think this could really refresh the
>> interface and avoid the ui from taking attention away for the content
>> (ie, the pretty map you're making). I tried making a script to auto
>> convert the icons as a test and ended up with a horrendous result
>> which had to be burned in a furnace and scattered on the four winds.
>> 
>> Nyall
>> 
>>> 
>>> Alexandre Neto
>>> --
>>> Alexandre Neto
>>> -
>>> @AlexNetoGeo
>>> http://sigsemgrilhetas.wordpress.com
>>> http://gisunchained.wordpress.com
>>> 
>>> ___
>>> Qgis-developer mailing list
>>> Qgis-developer@lists.osgeo.org
>>> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://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: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Nyall Dawson]

On 26 November 2016 at 08:09, Nyall Dawson  wrote:
> On 25 November 2016 at 21:22, Alexandre Neto  wrote:
>> Hello all,
>>
>> QGIS 3 is getting lots of love, and we are seeing new features being added,
>> some legacy code being clean up, and so on. We are all aware that this will
>> break the 2.x API, but now it's the time for it.
>>
>> So I wondered if this is not the perfect time to think about some UI/UX
>> changes as well, as it will lead to more work in translation and
>> Documentation. Could we do a list of UI/UX stuff that we could improve?
>>
>> I can think of a few things:
>>
>> Consistency
>>  - "search", "select" and "browse" for browsing files;
>> - "Add saved file to map", "Load into canvas when finished", "Open output
>> file after running algorithm";
>> - there is more of these for sure;
>
> I love it!
>
> Stuff like this is a great jumping in point where anyone can get
> involved. It's just a matter of trawling through all the dialogs and
> collating a list of strings which need changing. If that was done then
> someone with commit rights could fix these in a couple of minutes. The
> hard bit (and the bit where ANYONE can help) is making the list in the
> first place.
>
> Some more suggestions (which again, anyone could help with identifying):
>
> - replacing "non standard" icons. We still have some inconsitently
> used icons (such as the expression builder icon) used throughout qgis.
> - dialogs which violate hig conventions:
> - use of ":" at the end of strings
> - bad tab order
> - group boxes with just one widget
> - bad/inconsistent capitalisation in strings, dialog titles, and tooltips
> - widgets without tooltips (or non helpful tooltips)


Another one I forgot to add (a bit unrelated):

- lots of the processing algorithms don't correctly handle z/m
geometries and the changes are often trivial to allow them to. I'd
love to see someone generate a list (based off master) of all the
algorithms which currently don't maintain z and m values and which
should.

Nyall


>
>
> These are also issues for plugins, so collating lists and opening bugs
> against plugins would also help.
>
>
>>
>> Help and Documentation
>> - Most of our help buttons lead to nowhere, we already talked about pointing
>> them to the User's Manual online (although we would need a solution for
>> working with it offline and in different languages)
>>
>> Defaults
>> - Should default selection color not be opaque?
>> - Showing only selected features vertexes by default?
> +1
>
>> - Map template, we could provide a very simple template as default (I think
>> there was already some discussion about this); Most people I see gets very
>> confused when they see a completely empty page.
>
> Depends how it's done. I don't think it should always open with a
> template, but including some nice templates with qgis would be a good
> start.
>
>
> Another idea I'd love to see for 3.0 is switching the main ui to using
> monochrome "symbolic" icons. I think this could really refresh the
> interface and avoid the ui from taking attention away for the content
> (ie, the pretty map you're making). I tried making a script to auto
> convert the icons as a test and ended up with a horrendous result
> which had to be burned in a furnace and scattered on the four winds.
>
> Nyall
>
>>
>> Alexandre Neto
>> --
>> Alexandre Neto
>> -
>> @AlexNetoGeo
>> http://sigsemgrilhetas.wordpress.com
>> http://gisunchained.wordpress.com
>>
>> ___
>> Qgis-developer mailing list
>> Qgis-developer@lists.osgeo.org
>> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Nyall Dawson]

On 25 November 2016 at 21:22, Alexandre Neto  wrote:
> Hello all,
>
> QGIS 3 is getting lots of love, and we are seeing new features being added,
> some legacy code being clean up, and so on. We are all aware that this will
> break the 2.x API, but now it's the time for it.
>
> So I wondered if this is not the perfect time to think about some UI/UX
> changes as well, as it will lead to more work in translation and
> Documentation. Could we do a list of UI/UX stuff that we could improve?
>
> I can think of a few things:
>
> Consistency
>  - "search", "select" and "browse" for browsing files;
> - "Add saved file to map", "Load into canvas when finished", "Open output
> file after running algorithm";
> - there is more of these for sure;

I love it!

Stuff like this is a great jumping in point where anyone can get
involved. It's just a matter of trawling through all the dialogs and
collating a list of strings which need changing. If that was done then
someone with commit rights could fix these in a couple of minutes. The
hard bit (and the bit where ANYONE can help) is making the list in the
first place.

Some more suggestions (which again, anyone could help with identifying):

- replacing "non standard" icons. We still have some inconsitently
used icons (such as the expression builder icon) used throughout qgis.
- dialogs which violate hig conventions:
- use of ":" at the end of strings
- bad tab order
- group boxes with just one widget
- bad/inconsistent capitalisation in strings, dialog titles, and tooltips
- widgets without tooltips (or non helpful tooltips)


These are also issues for plugins, so collating lists and opening bugs
against plugins would also help.


>
> Help and Documentation
> - Most of our help buttons lead to nowhere, we already talked about pointing
> them to the User's Manual online (although we would need a solution for
> working with it offline and in different languages)
>
> Defaults
> - Should default selection color not be opaque?
> - Showing only selected features vertexes by default?
+1

> - Map template, we could provide a very simple template as default (I think
> there was already some discussion about this); Most people I see gets very
> confused when they see a completely empty page.

Depends how it's done. I don't think it should always open with a
template, but including some nice templates with qgis would be a good
start.


Another idea I'd love to see for 3.0 is switching the main ui to using
monochrome "symbolic" icons. I think this could really refresh the
interface and avoid the ui from taking attention away for the content
(ie, the pretty map you're making). I tried making a script to auto
convert the icons as a test and ended up with a horrendous result
which had to be burned in a furnace and scattered on the four winds.

Nyall

>
> Alexandre Neto
> --
> Alexandre Neto
> -
> @AlexNetoGeo
> http://sigsemgrilhetas.wordpress.com
> http://gisunchained.wordpress.com
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Tim Sutton]

Hi


> On 25 Nov 2016, at 2:01 PM, Bernd Vogelgesang  
> wrote:
> 
> I also wondered that there was no discussion about those topic for QGIS 3 so 
> far, so I dare to throw into the collection a topic that a while ago was 
> raised somewhere:
> 
> Ribbon based menues/menue groups
> 
> This is definately a love/hate topic, but as I got used to the ribbons in 
> MS-Software, I really see them now as a way to partially reduce the clutter, 
> though I have no real idea how to intelligently group the stuff (but I'm sure 
> enough brilliant people around here could have good ideas)
> And this would really give QGIS3 a maximum of a "fresh" look.

I thought I really disliked ribbons, but the ribbon interface that Marco and 
Sandro from Sourcepole demonstrated in Girona really appealed to me. I think if 
it is carefully done it could be nice. However I don't know it it makes sense 
for general use cases where users probably value screen real estate over big 
easy to click buttons. In Sourcepole's case they had a very well defined 
audience and specific activities they needed to perform I thought it made a lot 
of sense.

Regards

Tim


> 
> Cheers
> Bernd
> 
> Am 25.11.2016, 12:44 Uhr, schrieb Paolo Cavallini  >:
> 
>> Il 25/11/2016 12:37, Richard Duivenvoorde ha scritto:
>> 
>>> Would be good if somebody collects these idea's, and (given we can come
>>> to some consensus...) maybe try to do a special 'UIX'-funding round
>>> somewhere later in the QGIS-3 process (when api etc etc are settled)?
>> 
>> agreed, a targeted funding could be started. I think most of the stuff
>> is rather independent from API changes, so probably the two initiatives
>> could go largely in parallel (March is very close, as other have pointed
>> out).
>> All the best, and thanks.
>> 
> 
> 
> -- 
> Bernd Vogelgesang
> Siedlerstraße 2
> 91083 Baiersdorf/Igelsdorf
> Tel: 09133-825374
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org 
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer 
> 
> Unsubscribe: http://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: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Paolo Cavallini]

Hi Alexandre,

Il 25/11/2016 15:07, Alexandre Neto ha scritto:

> Maybe I am over-simplifiyng things, but I think some of this issues are
> repetitive tasks that, once learned, even a non-developer could take
> care of. So maybe one needs just a gentle push from from one available
> developer, and then do the rest. I would love to help in some of these.

agreed, this kind of things fall somewhat in between the aims of a dev
and those of a normal user, and are easily overlooked.
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: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Tom Chadwin]

If Alexandre is right, I'd love to help as well, if I can.



-
Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon 
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/Any-UI-UX-plans-for-QGIS3-tp5297396p5297434.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Alexandre Neto]

Hi Richard,

Richard Duivenvoorde  escreveu no dia sexta,
25/11/2016 às 11:37:

>
> Which brings me to the point: we need devs/resources to do such things
> too. Also for me it is too easy to rethink stuff, but not able to do it
> myself it does not happen by itself...
>
>
Maybe I am over-simplifiyng things, but I think some of this issues are
repetitive tasks that, once learned, even a non-developer could take care
of. So maybe one needs just a gentle push from from one available
developer, and then do the rest. I would love to help in some of these.

Alexandre Neto
-- 
Alexandre Neto
-
@AlexNetoGeo
http://sigsemgrilhetas.wordpress.com
http://gisunchained.wordpress.com
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Paolo Cavallini]

Il 25/11/2016 13:01, Bernd Vogelgesang ha scritto:
> I also wondered that there was no discussion about those topic for QGIS
> 3 so far, so I dare to throw into the collection a topic that a while
> ago was raised somewhere:
> 
> Ribbon based menues/menue groups
> 
> This is definately a love/hate topic, but as I got used to the ribbons
> in MS-Software, I really see them now as a way to partially reduce the
> clutter, though I have no real idea how to intelligently group the stuff
> (but I'm sure enough brilliant people around here could have good ideas)
> And this would really give QGIS3 a maximum of a "fresh" look.

Interesting. In case, better having it optional.
Thanks.

-- 
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: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Bernd Vogelgesang]

I also wondered that there was no discussion about those topic for QGIS 3  
so far, so I dare to throw into the collection a topic that a while ago  
was raised somewhere:


Ribbon based menues/menue groups

This is definately a love/hate topic, but as I got used to the ribbons in  
MS-Software, I really see them now as a way to partially reduce the  
clutter, though I have no real idea how to intelligently group the stuff  
(but I'm sure enough brilliant people around here could have good ideas)

And this would really give QGIS3 a maximum of a "fresh" look.

Cheers
Bernd

Am 25.11.2016, 12:44 Uhr, schrieb Paolo Cavallini :


Il 25/11/2016 12:37, Richard Duivenvoorde ha scritto:


Would be good if somebody collects these idea's, and (given we can come
to some consensus...) maybe try to do a special 'UIX'-funding round
somewhere later in the QGIS-3 process (when api etc etc are settled)?


agreed, a targeted funding could be started. I think most of the stuff
is rather independent from API changes, so probably the two initiatives
could go largely in parallel (March is very close, as other have pointed
out).
All the best, and thanks.




--
Bernd Vogelgesang
Siedlerstraße 2
91083 Baiersdorf/Igelsdorf
Tel: 09133-825374
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Paolo Cavallini]

Il 25/11/2016 12:37, Richard Duivenvoorde ha scritto:

> Would be good if somebody collects these idea's, and (given we can come
> to some consensus...) maybe try to do a special 'UIX'-funding round
> somewhere later in the QGIS-3 process (when api etc etc are settled)?

agreed, a targeted funding could be started. I think most of the stuff
is rather independent from API changes, so probably the two initiatives
could go largely in parallel (March is very close, as other have pointed
out).
All the best, and thanks.

-- 
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: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Richard Duivenvoorde]

On 25-11-16 12:27, Paolo Cavallini wrote:

Hi Alexandre,
thanks for raising this, much appreciated.


Yep, also from me: let's make QGIS the Desktop gis with the best UIX of 
all. Now is the time indeed!


@Alexandre: note that we closed the qgis-ux mailinglist as there was 
almost no traffic, and IF there was, we often needed input from the dev 
list so everybody started cross-posting anyway. So we decided to remove 
the ux list.


Which brings me to the point: we need devs/resources to do such things 
too. Also for me it is too easy to rethink stuff, but not able to do it 
myself it does not happen by itself...



Il 25/11/2016 12:22, Alexandre Neto ha scritto:


So I wondered if this is not the perfect time to think about some UI/UX
changes as well, as it will lead to more work in translation and
Documentation. Could we do a list of UI/UX stuff that we could improve?


Yep please: I should know there is some wiki page with 'wishes and 
changes' in QGIS3 but I do not have the url with me here (anybody?).


Would be good if somebody collects these idea's, and (given we can come 
to some consensus...) maybe try to do a special 'UIX'-funding round 
somewhere later in the QGIS-3 process (when api etc etc are settled)?


Coming to a consensus is maybe best done during a (big?) user or 
developers meeting?


Regards,

Richard

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

Re: [Qgis-developer] Any UI/UX plans for QGIS3?

[Paolo Cavallini]

Hi Alexandre,
thanks for raising this, much appreciated.

Il 25/11/2016 12:22, Alexandre Neto ha scritto:

> So I wondered if this is not the perfect time to think about some UI/UX
> changes as well, as it will lead to more work in translation and
> Documentation. Could we do a list of UI/UX stuff that we could improve? 

agreed

> *Consistency*
>  - "search", "select" and "browse" for browsing files;
> - "Add saved file to map", "Load into canvas when finished", "Open
> output file after running algorithm";
> - there is more of these for sure;

agreed. the point is finding all of them

> *Help and Documentation*
> - Most of our help buttons lead to nowhere, we already talked about
> pointing them to the User's Manual online (although we would need a
> solution for working with it offline and in different languages)

agreed - there has been lots of discussion about this, time is ripe to
implement a solution

> *Defaults*
> - Should default selection color not be opaque?

+1

> - Showing only selected features vertexes by default?

-0

> - Map template, we could provide a very simple template as default (I
> think there was already some discussion about this); Most people I see
> gets very confused when they see a completely empty page.

++1

Thanks again.
-- 
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: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Any UI/UX plans for QGIS3?

[Alexandre Neto]

Hello all,

QGIS 3 is getting lots of love, and we are seeing new features being added,
some legacy code being clean up, and so on. We are all aware that this will
break the 2.x API, but now it's the time for it.

So I wondered if this is not the perfect time to think about some UI/UX
changes as well, as it will lead to more work in translation and
Documentation. Could we do a list of UI/UX stuff that we could improve?

I can think of a few things:

*Consistency*
 - "search", "select" and "browse" for browsing files;
- "Add saved file to map", "Load into canvas when finished", "Open output
file after running algorithm";
- there is more of these for sure;

*Help and Documentation*
- Most of our help buttons lead to nowhere, we already talked about
pointing them to the User's Manual online (although we would need a
solution for working with it offline and in different languages)

*Defaults*
- Should default selection color not be opaque?
- Showing only selected features vertexes by default?
- Map template, we could provide a very simple template as default (I think
there was already some discussion about this); Most people I see gets very
confused when they see a completely empty page.

Alexandre Neto
-- 
Alexandre Neto
-
@AlexNetoGeo
http://sigsemgrilhetas.wordpress.com
http://gisunchained.wordpress.com
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer