Bear Bibeault wrote:
How is the data for the search retrieved? From a DB? What's the scale of the data? 10's? 100's? millions? Depending upon these answers, the appropriate sourcing mechanism for the data can be chosen.
I'd also ditch the whole notion of the "+" -- just let the user click on the name. Why make them click on a small "+"? I often say: "UI should not be a test of hand/eye coordination".
The data is currently being retrieved on a separate search page using ADO connections to Active Directory, AD contains around 1800 employees.
As for the + sign I am MORE than happy to ditch that and let them click on the user name or the entire column showing the user's name.
The reason for the search button and then a list pop up was to reduce what the ADO AD connection was searching for, thus speeding up the webpage response time. Even though only 1600 employees, my current concept would require 3200 data elementa (name, title per user), so the more I pull into a local data (easily generated via ASP inside the
java) the slower the page would pull up initially for an autocompleter.
An example:
On the page I use to search if I put in SMI and click search I get a list of 47 employees in about 1 second, If I put nothing (pulling everyone) the search box takes about 11 seconds to return, so logically I would assume it would take at least those 11 seconds to populate local data for the javascript.
I am open to any suggestions and if the end is to make them wait 10 seconds more that's fine, one might even argue if we change 7 people on average each time we access this, then 7 searches would be at least 1 second each, so 7 seconds total, by building local data there is of course no need to repull the data but to just autocomplete it in each circumstance.