--===============4495005671354603497== Content-Type: multipart/alternative; boundary=001a113517d2d9792304fb7d71e0 --001a113517d2d9792304fb7d71e0 Content-Type: text/plain; charset=UTF-8 On Mon, Jun 9, 2014 at 10:48 AM, Kevin Funk wrote: > Hey guys, > > Working a bit with Coverity (static analysis tool, [1]) lately, I've come > across this nice way [2] of reporting errors. Xcode has a similar way of > reporting errors [3]. > > I think, having some basic infrastructure for displaying this kind of > inline > widgets would be beneficial not just for KDevelop land. > > How hard would it be implement something like that for Kate? > > Obvious advantages of these inline widgets compared to other solutions: > * Information text is close to the range it's attached to > * The widget doesn't hide other editor contents > (as opposed to some tooltip solution) > * No user interaction required to retrieve the information text > (it's always there) > > Greets > > [1] http://www.coverity.com/ > [2] http://security.coverity.com/static/media/img/goto-fail.png > [3] > http://richarddingwall.name/wp-content/uploads2/2008/06/xcode-build-error.png > > -- > Kevin Funk > _______________________________________________ > KWrite-Devel mailing list > KWrite-Devel@kde.org > https://mail.kde.org/mailman/listinfo/kwrite-devel > What about only coloring the line and add the first line aligning it to the left? This way it wouldn't break the static line size height and the whole view won't bounce when you get new messages. We could have it expand on mouse hover. Aleix --001a113517d2d9792304fb7d71e0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On M= on, Jun 9, 2014 at 10:48 AM, Kevin Funk <kfunk@kde.org> wrote:
Hey guys,

Working a bit with Coverity (static analysis tool, [1]) lately, I've co= me
across this nice way [2] of reporting errors. Xcode has a similar way of reporting errors [3].

I think, having some basic infrastructure for displaying this kind of inlin= e
widgets would be beneficial not just for KDevelop land.

How hard would it be implement something like that for Kate?

Obvious advantages of these inline widgets compared to other solutions:
* Information text is close to the range it's attached to
* The widget doesn't hide other editor contents
=C2=A0 (as opposed to some tooltip solution)
* No user interaction required to retrieve the information text
=C2=A0 (it's always there)

Greets

[1] http://www.cover= ity.com/
[2] http://security.coverity.com/static/media/img/goto-fail.= png
[3] http://richarddingwall.name/wp-content= /uploads2/2008/06/xcode-build-error.png

--
Kevin Funk
_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel

What = about only coloring the line and add the first line aligning it to the left= ? This way it wouldn't break the static line size height and the whole = view won't bounce when you get new messages. We could have it expand on= mouse hover.

Aleix
=
--001a113517d2d9792304fb7d71e0-- --===============4495005671354603497== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ KWrite-Devel mailing list KWrite-Devel@kde.org https://mail.kde.org/mailman/listinfo/kwrite-devel --===============4495005671354603497==--