application view

[Daniel Franke]

> > > Alexander, if I understand your suggestion correctly, by
> > > using konsolepart you imply the following behaviour:
> > >  * an empty application view at startup (no prompt)
> The propmt wouldn't hurt.
Thinking as user: two different view but (apperently) same behaviour -
something's wrong here?

> > >  f. [together with (c)] output formats of tools may differ
> > >     significantly, user-defined pattern-matching might be reasonable
> > > (in addition to capture-output-flag in tools menu)?
>
> This can be complicated to implement. The idea is to have "tool output
> format plugins" for makeview and for appoutputview. Elsewhere you'll end
> checking regexps for all supported tools every time - we do it in make
> output now, it's not that fast.

I neither thought of plugins nor implementing any regexps myself. There
are so many tools out there, small hacks, inhouse-apps, gnu-tools,
whatever - in my eyes it's impossible to support them _all_ - even the
attempt to would be too much to ask for. The far easier way to allow all
tools to work: add an
	"Enter your regular expression to parse output here:"
widget (some examples included) and that's it. If a user want's this
feature, he has to figure the regexps out himself - but one is free to use
_any_ tool at any time (instead of writing a kdev-plugin first ;)
Additional benefit: it's fast, there will be only one expression to apply
- not many.
(The widget should most likely be placed near Configure KDevelop ->
External Tools -> Add ->Capture Output)

> The good thing about konsole is that it's fast and efficiently
> handle large output.
Can't judge about performance issues here.


	Daniel