On 01-12-16 19:48, Nyall Dawson wrote:
On 1 Dec 2016 11:28 PM, "DelazJ" <del...@gmail.com
<mailto:del...@gmail.com>> 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/
<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
