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

List:       kdevelop-devel
Subject:    Re: Code-Completion
From:       Dominik Haumann <dhdev () gmx ! de>
Date:       2006-05-02 8:46:52
Message-ID: 200605021046.53135.dhdev () gmx ! de
[Download RAW message or body]

On Monday 01 May 2006 23:52, Jens Dagerbo wrote:
> On Monday 01 May 2006 19:17, David Nolden wrote:
> > Hi! I've worked a lot on it and now when I look at it, i've completely
> > rewritten the vital parts of the cpp-code-completion. I've got it now
> > working very well with templates, even STL. It isn't completely ready
> > yet and still needs some polish..
>
> Sounds very cool. Did you manage to acquire SVN access?
>
> > but there are two other thing's I'd like to
> > ask about.
> > I've reactivated the type-display as prefix in the
> > auto-completion-box(for some reason it was disabled), and I use to show
> > the types completely template-processed. The problem is that it can
> > really get a lot of text(so one can lose the overview), and that the
> > there's a lot more to compute then until now(which takes especially
> > long when the persistent repository is used).
> >
> > So first I'd like to know if it is somehow possible to specialize the
> > popup-widget so I can vary the fonts to make the whole thing look
> > nicer, similar to the way I did it with the class-view and navigator by
> > just overriding the item-widget.. I couldn't find anything about that.
>
> I haven't really used the CodeCompletionInterface myself, but since the
> completionbox is implemented in the editor plugin I doubt you will find a
> way to changes to it.

Not possible.
Only idea: Get the pixel coordinates of the current cursor with 
ViewCursorInterface::cursorCoordinates(), and write your own code 
completion box.

--
Dominik

_______________________________________________
KDevelop-devel mailing list
KDevelop-devel@barney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
[prev in list] [next in list] [prev in thread] [next in thread]