On Friday 10 February 2012 09:10:41 Malix wrote:
> I try again to attach the plug-in source and the core change.
>
> Can someone give me an answer?
Hey there.
I agree that the error handling could be improved, but I dislike your approach
I have to admit. Instead of requiring the host application to implement a
plugin that shows such errors to the user, I'd rather improve what we have
inside the ktexteditor implementation, i.e. kate. A simple reason is: You'll
always want to see these errors (plugins can be turned off), kwrite and other
katepart-embeddors do not have a plugin mechanism, and finally: I don't want a
plugin for that in kdevelop.
Now what could we do instead: Improve the error popup!
Example: F7 -> "map asdf"
Error popup:
~~~
Error calling map:
ReferenceError: Can't find variable: asdf
<anonymous>()@:1
~~~
error output (i.e. what you'll show in your plugin if I'm not mistaken):
~~~
asdf string
function (line) { return asdf;} function
~~~
So, what would be an improvement? Well, my take is the following popup:
~~~
Error calling map:
ReferenceError: Can't find variable: asdf
in <anonymous>()@:1
Executed script:
function (line) { return asdf; }
~~~
- also make the text of the popup selectable / copy'n'pastable
- also add a "link" that executes "help map"
Cheers
--
Milian Wolff
mail@...
http://milianw.de_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@...
https://mail.kde.org/mailman/listinfo/kwrite-devel
