I like the idea to. It would be useful for input masks. For instance right now the date and time component doesn't do a great job of telling the user what each field is. With this feature it would allow the user to place their cursor in the hour field and prompt them with "hh" for a two character hour. Right now I have to create a <TR> right above the date and time component and try to match up headings with the fields that are beneath it.

Aaron Bartell

Korhonen, Kalle wrote:

Definitely sounds like a useful component.

Kalle



-----Original Message-----
From: Sean Schofield [mailto:[EMAIL PROTECTED] Sent: Saturday, February 12, 2005 1:24 PM
To: MyFaces Discussion
Subject: New component idea: MyFaces Suggest


I have an idea for the next component I can contribute. I am still working on the revised tree but there is a new component that I am working on that I think would be very useful for others.

Basically it would be a "suggest" input component. So it would look like a regular input text field but once you started typing in it, it would "suggest" choices. For those of you not familiar with "google suggest" you should check that feature out for a better idea of what I mean.

Unlike google's suggest feature it would not dynamically communicate with the server to update the list. You would specify a finite list via a backing bean and those would be the choices. You could also specify whether to require the value be one of the choices listed (it would have an internal validatation method provided.)

I had the idea for this feature when our users complained about now having the "type ahead" stuff in our webapp that they were used to seeing in their otherwise lousy Oracle Forms application. (Not a slam on Oracle Forms, just this implementation.)

Anyways, I am working with someone who is doing all of the javascript and DHTML necessary. It wil work in IE and Firefox. I will port it over to JSF and offer it to MyFaces if there is interest.

sean







Reply via email to