I would really caution against doing this. My rule of thumb is that IF i have to explain the page to someone. I didn't do my job designing it. Your not going to be there to hold your users hand every time they come to your page.
Build your page and give it to the most non techie person you know and don't say a word. Bring duct tape if you need to. Let them "discover" whats supposed to be done. You will be amazed at what they will click on and what order they fill in forms. I found this out with an application I wrote recently. I had several pieces of information iIneed and first, last name were not the first things on the list. In fact they were auto populated from other data bits (employee ID) they filled out early on in the form. BUT nearly all of them noticed those empty *first last name fields* in the middle of the screen.... they all tried to fill those out first. Kinda blew me away, the whole coolness of my form was lost on them cuz they didn't care about 'auto fill' or 'tab order' they just knew the answer to those fields so went there first. </rant> On 5/9/08, Don L <[EMAIL PROTECTED]> wrote: > > I think there was a thread talking about two connected levels of > auto-suggest or auto-suggest chain. A quick search did not yield it. Does > anyone happen to recall something to the effect of that thread title? > > The flow would be like something like the following: > (Instruction: > a) first type an alphabetic letter in the box below to select categry; > b) press [space bar] after category select, then type the first digit of a > zipcode. > --------------------------------- > a) pick a category of interest; > b) upon selection + space bar + auto-suggest zipcode > --------------------------------- > > It shouldn't be difficult to do but am lazy (if someone has done just > 'borrow' it...)... > > Also, equally importantly, for public-facing app, how would you write the > instruction above the Select box to ensure smart or dumb users can all > understand and use it? > > Another approach to solve the above problem would be to use two > auto-suggest ajax control with two Select boxes, which might be clearer to > users (especially for the public-facing app), however, personally I prefer > the first/top approach, which seems more efficient... > > Thanks. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;192386516;25150098;k Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:304977 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
