undocking/detaching toolviews to regular windows instead of tool windows

Sven Brauch mail at svenbrauch.de
Thu Oct 12 23:10:05 BST 2017

On 12/10/17 18:11, René J.V. Bertin wrote:
> Time for me to come off as a bit harsh, but I've been doing this a
> bit longer than you. I avoid cross-posting to MLs and newsgroups
> where I'm certain a majority of users will get duplicates. Qt's
> interest ML and StackOverflow don't fall under that category for me,
> and in my experience I get answers on either one or the other. I
> prefer to take my chances to getting answers by asking questions
> rather than by not asking them and trying to reinvent each wheel I
> need myself again and again. That's all the more true when dealing
> with collaborative software.

But -- sorry to say -- you end up costing a lot of people a lot of time
for reading through all the text you write, without really creating any
value. I know the feeling of thinking "what the hell is happening here?
I need to ask someone who knows what's up" all too well, but the truth
is, usually nobody knows. Everbody needs to debug it first. Thus you can
either investigate yourself, or write an email describing your problem
in three pages of text and hope for somebody else to do exactly that
work for you. Which effectively doesn't help at all.

To be completely blunt, I think this kind of general technical
discussion is only efficient if a) we're talking about a really really
complicated, annoying issue which needs a combined team effort to solve,
or b) somebody on the list has recently worked on exactly that thing or
is known to have in-depth knowledge of the code so the question can be
answered very quickly (e.g. David Nolden when it comes to the itemrepo
stuff). Most of the other threads, to phrase it in a mean way, boil down
to "can somebody else please debug this for me".


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://mail.kde.org/pipermail/kdevelop/attachments/20171013/7a9dc4ea/attachment.sig>

More information about the KDevelop mailing list