×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
From: Joe Pluta
My problem with the "all in one place" theory is that all edits, even
smiple checks, should be re-implemented in the business logic itself.
That's a good point. I'd suggest that there are at least three (3) places where validation is appropriate:
1. The browser - before a form is submitted.
2. The framework - before HTML input elements are mapped to an intermediate record (in memory).
3. The business layer - before the record is stored in the database.
If you have a bunch of "required" fields on a form, but the user submits an empty form, I think it's appropriate for the form to light up like a Christmas tree (highlight empty fields), and remind the user that the form must be filled out. I use a standard JavaScript function for that.
You made a very good point in an earlier post that "records" are a central construct in all business applications. If you define "records" with meta language and have the framework automatically map HTML input elements to records, that's a good thing. But the framework shouldn't map "Hi Bill!" to a numeric data type. It should generate an error.
Finally, I think it's clearly understood that all applications will have unique validation rules that need to be handled by custom code.
However, it would be good if 1,2,3 all used the same error mechanism, for consistency purposes.
Nathan.
midrange.com
