From kde-panel-devel  Tue Aug 30 20:11:31 2005
From: Matt Broadstone <mbroadst () gmail ! com>
Date: Tue, 30 Aug 2005 20:11:31 +0000
To: kde-panel-devel
Subject: Re: [Panel-devel] Using Kdevelop for KDE developement
Message-Id: <621909c70508301311143bc0a () mail ! gmail ! com>
X-MARC-Message: https://marc.info/?l=kde-panel-devel&m=112543274926290

On 8/30/05, Vinay Khaitan <vkhaitan@gmail.com> wrote:
> I like to use kdevelop for KDE programming, because of its enhanced
> Navigation techniques, code completion and other features.
> 
> KDE svn doesn't use kdevelop for developement. So, to understand the
> code flow, I needed to use the old Source-Navigator. That is extremely
> nice tool, but tool old. Kdevelop is much versatile.
> 
> The problem I see with kdevelop for KDE main developement is its very
> large codebase, which would require significant amount of time for
> parsing.
> Old Developers are used to normally vi/emacs, which are geared for
> keyboard control. So they might not bother it.
> 
> Is not it possible to improve this situation and put .kdevelop file in
> kdesvn ? So that, we can use full Kdevelop features for faster-code
> developement?
>
No. If you'd like to work with KDevelop you can actually use it's
rather advanced Import feature, and keep your kdevelop file locally.
It would not make sense to keep that in the tree though, not everyone
uses that, wants that or needs that. Why don't we have project files
for say Eclipse?
Stick with the "Import existing project," I know for a fact that it
works quite well with kicker, as I used that to do some initial
cachegrind tests.
 
> I think, some type of PCS etc would be able to improve this situation.
> _______________________________________________
> Panel-devel mailing list
> Panel-devel@kde.org
> https://mail.kde.org/mailman/listinfo/panel-devel
>
_______________________________________________
Panel-devel mailing list
Panel-devel@kde.org
https://mail.kde.org/mailman/listinfo/panel-devel