Compiler output toolview

[Milian Wolff]

On Thursday 03 January 2013 11:54:49 Andreas Pakulat wrote:
> Hi,
> 
> On Thu, Jan 3, 2013 at 7:14 AM, Steffen Ohrendorf
> 
> <steffen.ohrendorf at gmx.de> wrote:
> > I talked with a colleague about writing a plugin that gives a better
> > display of compiler messages. We concluded that adding such a
> > functionality to the OutputView is out of scope, so that we need a
> > separate plugin for that - the idea was to have the output parsed per
> > input file so that e.g. warnings from a header file which occur multiple
> > times are detected and shown only once for that particular file.
> > 
> > We are currently facing the problem of how to receive the output, as we
> > haven't seen a way to observe the messages that are sent to the
> > OutputView. We are aware of the problems that can appear due to different
> > compilers and/or localizations.
> > 
> > Any suggestions/ideas/complaints?
> 
> Thats not possible without modifiying at least the build plugins as
> well. The architecture currently does not allow to access the stuff
> thats visible in the outputview. So you'd either have to change the
> architecture of the outputview library or adjust the build plugins to
> expose the information somehow.
> 
> However I currently don't see (without having tried or extensively
> thought about it) why a sorting-filter-proxy model between the
> outputview and the outputmodel shouldn't work to hide such duplicates.
> Such a proxy model could be an opt-in for the existing views even,
> giving the user the choice in a config dialog.

+1 This should be done in the output view.

Cheers
-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20130103/55086cbd/attachment.sig>