[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 146519] Incorporating features from successfull comercial
From:       Jakob Petsovits <jpetso () gmx ! at>
Date:       2007-06-07 22:09:32
Message-ID: 20070607220932.10218.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=146519         
jpetso gmx at changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From jpetso gmx at  2007-06-08 00:09 -------
> I'm a C/C++ developer for some time already and the quality of development
> tools grows rapidly, but still, there is a huge gap between commercial (and
> even free) tools and open-source tools.

True.

> My actual feeling about this is that open source developers don't realize
> the need for good tools

My actual feeling about this is that there is not enough open source developers \
working on good tools, and so commercial tools have the advantage of some tens to \
dozens to hundreds full-time developers working on such tools. Which is not the case \
with the overwhelming majority of open source software, including KDevelop.

> (guess why Visual Studio is so cheep).

Because Microsoft finds it important to hook developers not only to their development \
tools but also to the Windows platform, and they are willing to spend a big amount on \
money and developers because of that. Access to cheap and at the same time \
high-quality development tools is a prime motivation for developers to choose one \
development system or even target platform over another, and Microsoft would be \
stupid if they didn't realize this.

> Seeing at least some features (great code-complete and syntax highlighting)
> in Kdevelop would mean a revolution for me.

Code completion is a work in progress. Syntax highlighting is excellent already today \
(thanks to Katepart).

However, this is not an item belonging in the bug tracker, even if it's marked as \
wishlist. The bug tracker is supposed to contain clearly scoped tasks, where you can \
tell exactly when the bug has been fixed, or the wish has been implemented. Your \
report, even if there is a bit of truth in it, is far too vague to be of real use for \
the project.

We know that proper code completion, syntax highlighting, project management and \
whatnot, are important. We just need people who make an implementation out of these \
visions, or the most concious realization will not lead to anything.

Concerning this matter, we would like to cordially invite you to join the development \
team, and be a small part of the grand project to create better free development \
tools. Or at least, provide your wishlist items in a bitesize way, so that we get an \
idea of how exactly you imagine KDevelop to be improved.

For starters, you could examine in detail what this Wholetomato thing does and \
KDevelop does not, as I'm pretty confident that no one in the developer team will \
care to buy and install this kind of proprietary add-on for Visual Studio, except \
maybe in the case that they use it for their work.

Excuse me if I close this bug as invalid, please be more specific in future bug \
reports. Visions like this would be very suitable for a blog entry, though.


[prev in list] [next in list] [prev in thread] [next in thread]