[TYPO3-ect] Error Object

[Daniel Brüßler]

Hi Elmar,

all right. I think of it - we can shurely have two different components.
So I freeze the code-error-handling for a while.

Now I see what you mean - it's a part of rendering input-forms. Instead
of an error-message I prefer to show a red icon before the input-field
or changing the css-class to show a red background-color using jQuery or
something.

What's with the frontend-part of it? Is the XHTML/JavaScript/CSS/AJAX
for it made by the user -- or shall there be help by lib/div?

Question: Will there be a migration-path to integrate tx_forms? I didn't
follow the discussion about this in detail.

++-------

Tonight (11 o'clock) I reserved time for the team-homepage, tomorrow I
can go on with the ErrorMessenger.


kind regards
Daniel Brüßler
> I think we need to keep the two things apart. I called it error messanger
> to point out the difference to a debugging error object you are thinking
> of. The "error messanger" doesn't do that much. It carries messages like
> "empty value" or "invalid email format" to a HTML form. That is regular
> feedback to the user and nothing that is of relavance for the admin or so.
> Maybe it should be combined with the validator. But the validator is only
> one source of error messages for the form user. The other source is the
> model. That's the reson I am thinking of a common error object for model
> and validator.
> 
> I want the names of the basical API functions stable before we go to beta.
> I count the basics of the FE forms into this. So we need this object
> before beta.
> 
> The debugging error object or messanger is what you have in mind. That
> would be very helpful for development and it would be a big contribution
> for the future popularity of lib/div. But it is not an elementary
> prerequest for to go to beta.