Thanks Eelco and Phil for your input. If there is a way to use just a panel instead of an entire page, I would welcome the change. The *one* thing I do like about using a seperate page, is that it allows you to view the autocompletion results outside of the parent form. The url generated is much like the url for a bookmarkable page, which is quite a bit nicer than the url for a component of a page. Scriptaculous demos (built using rails) have simple urls to accomplish the same thing. ex: http://script.aculo.us/demos/ajax/demos/ajax/auto_complete_for_message_to
I'm willing to give up "pretty" urls and use a simple panel though if it seems like a better overall solution. =) > Why not use IModels instead of 'public String[] getResults(String > input)' and 'protected ListView buildListView(String input)' ? You > could use the getInput method of FormComponent to get the input as the > user provided it without actually updating the component's model (thus > you won't need the input arg), and it would be more consistent with > the rest of Wicket. Otoh, the current API is very focussed, which is a > good thing too. I'd be really interested to see this API change. I'm all for making these components more inline with how Wicket works. I'm still very much a Wicket newbie, afterall. =) Returning a String[] is simply to make the return type very explicit. No confusion for the end users. Building a ListView is maybe not the best API, but I couldn't think of anything else at the time. On 9/5/05, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > Smart! So you got around the problem of not being able yet to render > just one component by just rendering a whole page. > > It is something Juergen is working on (he created a branch for it). > When that works, we could just render components directly, switch it > on/ off etc. > > Why not use IModels instead of 'public String[] getResults(String > input)' and 'protected ListView buildListView(String input)' ? You > could use the getInput method of FormComponent to get the input as the > user provided it without actually updating the component's model (thus > you won't need the input arg), and it would be more consistent with > the rest of Wicket. Otoh, the current API is very focussed, which is a > good thing too. > > Keep up the good stuff! > > Eelco > > > On 9/4/05, Ryan Sonnek <[EMAIL PROTECTED]> wrote: > > Hey Wicket AJAX developers, > > I just finished up revamping the scriptaculous autocomplete components > > and would like any feedback. I've been working on the > > wicket-contrib-prototype subproject and think it's looking pretty > > good. =) > > > > I've decided to create 3 different components for different use cases > > and I wrote up a little article on my blog to show how to use the > > different components. There are also examples in wicket-stuff for > > anyone interested. > > > > http://jroller.com/page/wireframe/?anchor=choice_is_good > > > > Any thoughts on future changes? > > > > > > ------------------------------------------------------- > > SF.Net email is Sponsored by the Better Software Conference & EXPO > > September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > > _______________________________________________ > > Wicket-user mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/wicket-user > > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
