Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


On 09/12/2011 11:39 AM, Olivier Hallot wrote:
Hello all

"Error in scripting framework during Basic script execution"
"Message: The following Basic scirpt could not be found"
" bla bla bla, method,
"bla bla bla location"...

Is there a message uglier, scarier,and horrendous as this one above? Not
hard to imagine a legion of frightened users freezing and crisping jaws on
reading such cursing message!

Couldn't we write just "Oh dear, I am unable to find a macro you asked me to
execute!"?

What I would prefer to see on an error is:

<error for a dummy>
<error for a technical person>

Rather than just <error for a dummy>

The trick is to find a way to express the error such that a non-technical person is not horrified, yet, a technical person has a chance to find the actual problem. A dialog with a details button is great.

Now, that said, we would need to have a chat with the developers to make that happen

--
Andrew Pitonyak
My Macro Document: http://www.pitonyak.org/AndrewMacro.odt
Info:  http://www.pitonyak.org/oo.php


--
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.