KDE/kdevelop/lib

Andreas Pakulat apaku at gmx.de
Sun May 13 13:13:37 UTC 2007


On 13.05.07 08:01:07, Matt Rogers wrote:
> 
> On May 13, 2007, at 2:31 AM, Dukju Ahn wrote:
> 
> > SVN commit 664121 by dukjuahn:
> >
> > Porting ProcessLineMaker into KDev4. This wraps signal line-by- 
> > line, rather than emitting text whenever there is incomplete stdout/ 
> > stderror.
> > To enable this, added KDEVUTIL_EXPORT macro.
> > OutputView now uses ProcessLineMaker.
> 
> hmm, I wonder if it wouldn't be better to have an interface for  
> filtering various process output so that the plugins can do their own  
> filtering. That's where it belongs, IMHO. What do others think?

Yeap, see me reply to the commit, I think this makes sense. I'm thinking
about doing it this way:

a plugin has a custom filtering class that implements IProcessFilter
OutputView has then executeProcess(command-stuff, IProcessFilter*)

I'm just not sure about the interface of IProcessFilter, but it
certainly doesn't have to be an extension interface, IMHO.

Andreas

-- 
Your boss climbed the corporate ladder, wrong by wrong.




More information about the KDevelop-devel mailing list