OutputView behavior and usage

Ivan Shapovalov intelfx100 at gmail.com
Thu Dec 6 19:30:28 UTC 2012

On 06 December 2012 18:16:38 Milian Wolff wrote:
> On Thursday 06 December 2012 15:05:24 Mateusz Loskot wrote:
> > On 6 December 2012 14:37, Ivan Shapovalov <intelfx100 at gmail.com> wrote:
> > > BTW - how do you think it'd be most convenient to do "history"?
> > > Maybe a right-click on a tab which will activate a dropdown list?
> >  
> >  What about keeping it in the buffer, scrolled up and
> > 
> > visually separated?
> > Perhaps even as collapsed outlines (numbered), as code blocks in editor :)
> Yes, I think QtCreator did a fairly good job here - we should try to copy
> them in that regard imo.
> Personally, if I hit "build" with a multi item build selection, I want to
> see it all in one output view. If one job fails, the whole build job should
> be stopped.
> Regarding launches I think your idea is good. Have one output view with the
> ability to pin it, otherwise just plug in the output there and reuse an
> existing view.

Ok, thanks for your points. I'll try implementing that soon (need also to take 
a look at QtCreator, never used it for more than 10 seconds ;)).

- Ivan

More information about the KDevelop-devel mailing list