[Qt-creator] How to get your favourite feature into Qt Creator

[Daniel Teske]

> I can understand that you don't have time, that my feature is only interesting 
> for me, that my code is crap, I would be ok with an answer like: "We don't add 
> new feature untill 1.3 is released" or "this won't work", "this is buggy as 
> hell", but no answer _at all_ is really discouraging.
>   
We did discuss your merge request internally, sorry for not answering. 
Apparently someone forgot that.
In essence, yes we would like to add such a functionality, but there are 
quite a few limitations of your patch. Some of which are because we need 
to still build a good foundation for code manipulation.
As is, it can't be merged. The foundation building is ongoing, I'm not 
sure what is still missing for adding that feature, we definately have 
that on our todo list. I guess someone else could explain taht better.

Now we have multiple people looking at all merge request, and we have 
merged a great number of them into Creator already. While there seems to 
be a few where we didn't respond in time, if I'm counting corretly we 
have around 40 merge requests merged and 12 rejected and quite a few in 
a revise/resubmit state, so we did handle over 60 merge requests. It's a 
pretty new process, so it's not surprising that we have a problems, but 
I can't see that we are neglecting them.  We are currently pretty busy, 
and likely to remain so for the forseable future, but if we don't 
respond to a merge request a quick email on this mailing list is much 
appreciated.
I know of very few companies who are actually that open in their 
development process, with that many contributions[1], and so many devs 
in public irc channels.

> Another example: I found a bug in the code, asked on the mailing list, Daniel 
> Teske sent a patch to test, I tested it... and that's all.
> As far as I know, the patch is not applied and the bug is still here... 
> discouraging.
>   
The bug is on my todo list. Making the function virtual is probably not 
the right solution, or atleast it didn't seemed to be the right one when 
I looked at that code.
I need to investigate that in more detail before I can fix it. It's not 
a clear cut bug, but more that implicit assumption in the code is wrong, 
thus it probably needs some small refactoring, which is obviously not 
something I can do in a heartbeat.
I think I'll get a fix in for 1.3 though.


> I know you all have a todo list longer that what you can handle in a life-
> time, it's the same for me, I just ask for more communication (and saying "we 
> don't have time, wait until 1.3' is not really time consuming).
> Also, it would be nice to have a view of your roadmap, even if things can 
> change it would help us and avoid duplicating the work (/me needs scripts, is 
> it planed or can I start to work on it?)
Well, that noone responded was just a oversight, we looked at the patch 
and discussed it, but apparently we forgot to give you the feedback from 
our side. I'll let others comment on the exact issues.

As to our roadmap, what we are currently focusing is S60 support and 
working towards refactoring and obviously QML is one of the cornerstones 
of the future qt.

If you want to start working on something, it's best to write a small 
text about what you are trying to do, we'll surely comment on it. 
Scripts is pretty generic.

daniel

[1] I don't have the qt numbers, but they are considerably higher then 
the ones for Qt Creator