From 84da08d7b7fcda12c85caeb5a10b4903770a6f69 Mon Sep 17 00:00:00 2001 From: toma Date: Wed, 25 Nov 2009 17:56:58 +0000 Subject: Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. BUG:215923 git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdeaddons@1054174 283d02a7-25f6-0310-bc7c-ecb5cbfe19da --- knewsticker-scripts/Readme.ErrorHandling | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 knewsticker-scripts/Readme.ErrorHandling (limited to 'knewsticker-scripts/Readme.ErrorHandling') diff --git a/knewsticker-scripts/Readme.ErrorHandling b/knewsticker-scripts/Readme.ErrorHandling new file mode 100644 index 0000000..f8d2999 --- /dev/null +++ b/knewsticker-scripts/Readme.ErrorHandling @@ -0,0 +1,19 @@ +Error Handling for Knewsticker Pre commands + +Error handling might not be a prerequisite for writing Knewsticker scripts, +yet it would be nice if you tried to introduce some comprehensive error +handling in your scripts. Knewsticker is a graphical application and as such +the user is not able to read any error output your program might produce. +Knewsticker knows a variety of error codes and each is handled in a +different way. You may look those codes up in the table provided. + +Please make sure to return those error codes properly for the development +language you are trying to use. If you are trying to use Perl, please make +sure you understand an have read the top most part of the error handling +document. It will explain to you, how it is fairly easy to catch errors and +report them back to Knewsticker. + +If you are still unsure how to do it on a system level, simply implement +your own error handling and make sure, that your return codes match the +event(s) described in the error handling document you will find in CVS as +well. -- cgit v1.2.1