Re: [Qgis-developer] Processing NG/V2 - brainstorming

2016-12-09 Thread Victor Olaya
Hi, sorry for the late reply. Comments inline > > I've recently been informally chatting about possible enhancements to > processing with a few QGIS team members, and I thought it'd be worth > starting a public brainstorm about these ideas. Great to see people thinking about how to improve

Re: [Qgis-developer] Processing NG/V2 - brainstorming

2016-12-07 Thread Médéric Ribreux
Le 2016-12-05 11:42, johnrobot a écrit : Hi I would very much like to see improvements for Processing. A few additional ideas: - Display the number of features going through the model. This would help the user understand the data better. - Add comments to model components without opening

Re: [Qgis-developer] Processing NG/V2 - brainstorming

2016-12-06 Thread Matthias Kuhn
Hi Richard, On 12/06/2016 11:56 AM, Richard Duivenvoorde wrote: > On 05-12-16 10:03, Nyall Dawson wrote: >> Hi all, > > Hi Nyall et al. Good thinking, just wondering... what is NG/V2? :-) Next Generation, Version 2 Add to that: X / 2.0 / reloaded ;) > >> So here we go... a bunch of random

Re: [Qgis-developer] Processing NG/V2 - brainstorming

2016-12-06 Thread Richard Duivenvoorde
On 05-12-16 10:03, Nyall Dawson wrote: Hi all, Hi Nyall et al. Good thinking, just wondering... what is NG/V2? :-) So here we go... a bunch of random ideas on future processing enhancements: 1. Rework native algorithms to avoid layer input/outputs I have seen some people creating huge FME

Re: [Qgis-developer] Processing NG/V2 - brainstorming

2016-12-05 Thread Nyall Dawson
On 6 December 2016 at 05:46, Matthias Kuhn wrote: > Thanks for writing this up Nyall, > > This is something that I has been on my list of ideas for a long time > already and that I have never got round to get down to. > > I think you have covered the topic quite well already,

Re: [Qgis-developer] Processing NG/V2 - brainstorming

2016-12-05 Thread Matthias Kuhn
Thanks for writing this up Nyall, This is something that I has been on my list of ideas for a long time already and that I have never got round to get down to. I think you have covered the topic quite well already, so I don't think there's a lot I have to add right now. On 12/05/2016 06:41 PM,

Re: [Qgis-developer] Processing NG/V2 - brainstorming

2016-12-05 Thread Alexander Bruy
I really like the idea of having basic Processing code in the core library with Python bindings available. Regarding iterators approach... It sounds interesting, but we need to think also about possibility to work with layers, which are not loaded in QGIS. In this case as I understand we need to

Re: [Qgis-developer] Processing NG/V2 - brainstorming

2016-12-05 Thread Bernhard Ströbl
Hi Nayll and all, my ideas are more from a user's perspective and from that point of view I like your first idea most which (hopefully) increases performance and improves the output. Moreover I would like to add the following ideas 1) Selection: It would be cool to integrate QGIS' expression

Re: [Qgis-developer] Processing NG/V2 - brainstorming

2016-12-05 Thread johnrobot
Hi I would very much like to see improvements for Processing. A few additional ideas: - Display the number of features going through the model. This would help the user understand the data better. - Add comments to model components without opening each component. A chance to explain why a

[Qgis-developer] Processing NG/V2 - brainstorming

2016-12-05 Thread Nyall Dawson
Hi all, I've recently been informally chatting about possible enhancements to processing with a few QGIS team members, and I thought it'd be worth starting a public brainstorm about these ideas. This is really just "thinking aloud" about what the next logical steps are for processing and how we