[KDev4] SimpleOutputView Renewal

[Matt Rogers]

On Saturday 12 May 2007 08:10, dukju ahn wrote:
> Now is the time to make SimpleOutputView into "Complex"OutputView.
>
> What I want to implement first is some kind of integration with
> MakeBuilder. In KDev3.4, when compile error occurs we could go to the error
> spot just by clicking the gcc error string in Message tab.
> I plan to port it or rewrite it to KDev4.
>
> Now questions are
>
> 1.
> The name of output is "Simple"OutputView. Can I extend this existing
> plugin to implement integration above? Because the name suggests
> that it should be "simple", I hesitate to extend existing simpleoutputview.
> The name seems to suggest me that I should make other class
> which implements IOutputView.
>

Rename it, then extend it.

> 2.
> Do we have any special reason why the current output widget
> uses QStdModelItem instead of KTextEdit?
> If we use QStdModelItem, the user can't copy the
> outputs of commands. Also, the appearence of output is ugly IMHO.
> More severe problem is that listview gets slower when there are huge
> numbers of output lines. Think about building entire KDE project or
> entire firefox.
>

Yes, we want a model. Write a custom delegate or custom view if you don't like 
the appearance of it. I don't think KTextEdit will serve our needs here, 
since I'd like to share this particular model/view approach with the new 
equivalent of the problems tab in kdev3.

However, in my mind, it doesn't make any sense to start this unless we can 
actually compile something from within KDevelop. Can we do that yet?
-- 
Matt