Dne pondělí 18 červen 2007 14:09 Stanislav Visnovsky napsal(a):
Dňa Po 18. Jún 2007 14:06 Michael Andres napísal:
At various locations we catch exceptions and translate them into other exceptions.
Would it be helpfull, if we'd create a simple stack of error strings in class Exception? So we could store and propagate the old Exceptions asString and/or asUserString.
Something like this:
Failed to create repository. -Reason: Failed to parse some file -Reason: Failed to provide some file -Reason: File not found
But it's only worth the efford, if the UI is willing to display such multiline stacklike error messages.
How should UI report this? Typically, user is interested in 1 and last message of the stack (reason & the overall result)
If we don't want to get the whole stack, all we need is the bottom-most line. The application always knows that it wanted to create a repository and does not need to get this message from libzypp. Having the whole stack may help in case of bug reports without log (but eg. with a screenshot). Jiri -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz