[TYPO3-ect] Error Object

[Daniel Brüßler]

Hi Elmar,

== error-handler ==
you used the word "ErrorMessenger" - this is a bigger context than just
an ErrorObject. So I got a question about the "vision" of the
ErrorObject now:

This could also have a mode to send a red-alert-message by email to the
admin.

For example:
Instead of writing a simple "die" message to the FE-user who normally
does _not care_ about messages like this the error-handler could send a
red-alert-message and just show a "temporary unavailable - admin
contacted - you can come again in x hours" to the FE-user.

Is this what you also would like to have?


== team-homepage ==
All right. we take the "light"-version to high-prio and the
"full"-version as low-prio. That's the wiki-wiki-way :-)

kind regards
Daniel Brüßler


Elmar Hinz schrieb:
> Am Tue, 06 Feb 2007 11:42:33 +0100 schrieb Daniel Brüßler:
> 
>> Hi Elmar,
>>
>> yes, great! I'm shure this helps much with code-quality of TYPO3-extensions.
>>
>> My aim with error-handling is always, that I need not to search for
>> hours why "something" isn't working anymore. I like to see very fast
>> what was the original problem and where must I fix it.
>>
>> I create a wiki-page wiki.typo3.org/index.php/MVC_Framework/ErrorObject
>> for it and write down what I think. So we can merge and then I can start
>> to create the class.
>>
>> What is the priority for the ErrorObject? Shall the ECT-homepage be
> 
> Priorities lib/div:
> 
> High: 
> 
> * ErrorMessanger
> * Documentation
> * ResultBrowser
> 
> Medium:
> 
> * Predifined checks for the validator
> * DebuggingErrorObject
> * Pear Repository for forms lib, etc.
> * Hooks, Services etc. 
> 
> Low:
> 
> * Different helper tools for tables etc.
> 
> 
>> available very fast or in two steps (first the main-stuff, then the full
>> version)?
> 
> I guess a culture of regular simple, small steps is better for this, than
> one big step that is out-dated after a few monthes.
> 
> 
> Regards
> 
> Elmar
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>