Re: Strategy for user input instructions?
Re: Strategy for user input instructions?
- Subject: Re: Strategy for user input instructions?
- From: Josh Paul <email@hidden>
- Date: Sun, 19 Oct 2008 17:29:35 -0700
I've been working with LiveValidation <http://www.livevalidation.com/>
recently. It weighs in around 12kb, but I've found it's worth it. YMMV.
On Oct 19, 2008, at 5:12 PM, Ramsey Gurley wrote:
On Oct 19, 2008, at 6:06 PM, Guido Neitzer wrote:
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
Hey Guido! :-)
I should have phrased my question differently...
I'm using D2W, so that's the trick :-) Validation happens just
fine. What I need are the hooks to tell the user what will/won't
validate _before_ they attempt to make any input. I don't even see
any way to pass a user a message without creating a message page
configuration, and that's only for one message. I'm looking for a
way to display multiple messages for multiple attributes. As far as
I can tell, I can either roll my own inputInfoForKey() type of
system or pass the messages to a custom component through the
userInfo dictionary of my ERD2WPage. I figured that giving the user
some form of input instructions would be a pretty common requirement
and located in the Wonder framework somewhere already. I'm sure I
can come up with a solution, but I don't want to waste a lot of time
reinventing the wheel if there's something readily available :-)
Ramsey
_______________________________________________
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
_______________________________________________
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