proposal for extension of KTextEditor interface

[Joseph Wenninger]

Hi

Am Don, 2003-01-09 um 21.23 schrieb F at lk Brettschneider:
> Eray Ozkural wrote:
> 
> >On Wednesday 08 January 2003 12:41 am, F at lk Brettschneider wrote:
> >  
> >
> >>What do you mean with "scale up"?
> >>I can suppose jowenn is now working on the KTextEditor extension (as
> >>promised ;). Probably I'm going to try the implementation for QEditor...
> >>
> >>    
> >>
> >
> >Is it going to be efficient in large projects?
> >
> Speed would just depend on the speed of the debugger part to return the 
> local variable value and on the effeciency of the programming language 
> parser to analyze the dump text returned from the text editor.
> But it should be OK since tooltips have a slow response in general (1 
> second or similar)...
> 
> Jowenn, what is the news!?
> 

I'm experimenting a littlebit at the moment, but don't have much time at
the moment. I'll be committing my stuff into kdelibs at the begin of the
next week though. At the moment I'm believing that an interface like the
following should be enough
methods:
	void enableUserTextHints(int timeoutTime);
	void disableUserTextHints(); //that's the default state
signals:
	void needTextHint(int line, int col, QString &text);
		/*should only be emitted if line and col really changed (not inner
cell moves) when a timeout has happened.
The slot sets the text property and if it is not an emtpy string the
text editor displays it next/above/below the textcell.


Kind regards
Joseph Wenninger