> So it can be fetched like
> $datamodel.getSearch("..").getField("timedout")

Today's intention has been to use the hitcount's negative values to
indicate errors.

Query truncation doesn't belong to the search command.

Automatic broadening also doesn't belong to the search command.

But we do not have any solution for annotating errors, warnings, and
information statements back to the user.

Another idea would be to add 

 UIFeedbackDataObject extends DataObject
    String[][] getErrors()
    String[][] getWarnings()
    String[][] getMessages()

 and many of the DataModel's DataObject changed to extend this, so that
each node and object within the datamodel could store an array of i18n
keys (w/ parameters) for errors/warnings/information intended for the
user.

Would this contradict what we've done with Suggestions?

Or are is there other code we can re-use?
 - javax.faces.application.FacesMessage
 - Spring

~mck

-- 
"The future influences the present just as much as the past." Friedrich
Nietzsche 
| semb.wever.org | sesat.no | sesam.no |

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Kernel-development mailing list
[email protected]
http://sesat.no/mailman/listinfo/kernel-development

Reply via email to