kdevelop (Re: Proposal to plan for "Milestone Releases" on the way to KDE4)

Guillaume Laurent glaurent at telegraph-road.org
Mon Jan 30 15:25:48 GMT 2006

Alexander Dymo wrote:
> We certainly have better code completion. Try to make Eclipse
> complete your Qt/KDE code ;)
I tried, it was far from satisfactory but still better than what 
kdevelop could give me. Completion features aside, code navigation in 
kdevelop is also an issue.

> PS: I spent two months improving Eclipse to make it good for
> KDE/Qt development and I see that much more is necessary
> to do before Eclipse will be good for C++. We can spent the same
> effort on KDevelop and get better results.
Fine, as long as we get something better than XEmacs in the end.
> PPS: From this thread one can make a conclusion that nothing happened
> to KDevelop during last several years. This isn't true. The fact KDevelop
> doesn't fit the developers workflow has nothing to do with the
> lack of features. Contrary, we have tons of features and sometimes
> very good internal implementation of those features.
Yet kdevelop still can't indent code properly, nor navigate code 
properly. When I registered a wish for an outline panel restricted to 
the currently edited file, I got a reply telling me to use the 'classes' 
panel which is next to useless. Perhaps before adding features you 
should get the basics right.

More information about the kde-core-devel mailing list