KDEStudio code completion (was Re: KDevelop Roadmap 2001)

[William Gacquer]

There is also code completion in Wedit that is now under GPL. This is an
alternative to the crude KDEStudio code completion method.

See http://www.q-software-solutions.com/weditlinux/features.shtml

William Gacquer

PS : I really dislike to see as many IDE as developers. Kdevelop was one of
the first on the linux market and that's a good point. I believe that you
should find some kind of "commercial" guy to gather the linux community
around you product instead of letting them reinventing the wheel.



-----Original Message-----
From: Ralf Nolden [mailto:nolden at kde.org]
Sent: vendredi 2 mars 2001 12:19
To: kdevelop at kdevelop.org
Subject: Re: KDEStudio code completion (was Re: KDevelop Roadmap 2001)


Guillaume Laurent wrote:
> 
> On Friday 02 March 2001 11:44, Ralf Nolden wrote:
> 
> > -code completion (maybe) if the code of KDEStudio can fit into KDevelop.
> 
> I don't mean to sound rude but unless the KDEStudio has completely changed
> the way it performs code completion since last time I tried it (the 1.0
> release), I don't think you want to reuse that.
> 
> KDEStudio achieves code completion by running g++ and parsing the error
> messages. While this is a very neat hack, in practice it's totally
unsuable.
> 
> I strongly doubt there is a way to get code completion working in a
useable
> way without having the editor "understand" the code at the syntactical
level
> (and yes, that's a major development).

We know that and we have discussed this many times. The approaches taken
up until now lead to the result of nothing. The conclusion is:

a) kdestudio has code-completion, kdevelop doesn't
b) kdevelop is much more usable all in all but it just lacks this
feature that is more a PR issue than anything else. I've tried the
code-completion and it works halfway. 
c) the kdevelop versions following 1.4, i.e. 2.0, 2.1 etc that ship with
KDE 2.x are as said the last line of the "old" code, that is why I
pointed to HEAD for real serious work on our own code-completion etc.

result is that we don't have anything to loose except adding a feature
to 2.0 that the user can use or doesn't use. From the user's point of
view, the old users are confident with 2.0 if the rest works, the new
users and kdestudio users that are keen on this code-completion stuff
will not bother because it works and there's nothing better available at
the moment :-) 

That's the reason I vote for putting that in if someone is interested. I
repeat Werner's opinion, a half-code-completion is better than no
code-completion at all :-))

Ralf
-- 
Finally, even I have to admit that being myself was the best thing
that ever could have happened to me. - Le Grand Charmeur

**********************************
Ralf Nolden

The KDevelop Project
http://www.kdevelop.org

nolden at kde.org
rnolden at kdevelop.org
**********************************

-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org
with the following body:
unsubscribe >your-email-address<

-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«