Re: Strategy for user input instructions?
Re: Strategy for user input instructions?
- Subject: Re: Strategy for user input instructions?
- From: Guido Neitzer <email@hidden>
- Date: Sun, 19 Oct 2008 16:06:41 -0600
On 19.10.2008, at 15:13, Ramsey Gurley wrote:
I've been giving a lot of thought to user input instructions for the
past couple of days. WebObjects has a really awesome input
validation system, so it seems rather odd to me that there doesn't
appear to be any sort of analogous system for providing user input
instructions. I'm wondering what everyone else is doing in this
case. Are you guys just hardcoding this info into your page
templates? Is there some kind of inputInfoForKey(key) method I'm
overlooking somewhere? It seems like this would be a pretty common
requirement.
I have a super class for my pages (components) that do edits which has
an array of "validationMessages", I also create a dictionary of each
object name + attribute key as the key and a css class as the value.
That stuff is used to highlight fields / labels (custom reusable
components) with errors and I also have a MessageComponent that can
take the array of messages, can localize them if necessary, is
completely configurable on the verbosity, css classes used, and so on.
This is basically very similar to what DirectToWeb does with the
ERNeutralLook.
As an addition there is something like the RoR "Flash" messages inside
the Ajax framework in Wonder. With all that I have no need to be more
generalized. It's very long ago that I had to do anything but just
putting components on a page. On most edit pages I have less than 10
lines of custom code (besides support code for some Ajaxy stuff).
cug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden