Yes I think it's an excellent start and very useful. I'm slightly confused with using an object.
I have a list of users with a one to many relationship to a purchase request table. I gave it a value encoder and gave the tagselect value "pr.authorizor". Where I'm confused is the authorizer is just the user object and doesn't contain the list. I'm not entirely sure how to pass both the list and the object into the component. Perhaps you could show me an example of how you do it. I know with a loop we'd use source for the list and value for the object. I'd love to contribute to your project, but I don't think I know enough about custom tapestry components just yet. Not sure how to even run them locally to test. Any articles or docs would be appreciated though This could be an excellent alternative to very large select menus. I like how it has similar actions to autocomplete, but limits your choices to only what is available in the list while giving you the remove x. That would be the only reason I'd like to limit the result set to possible one. the issue I'm having when using greater than less than might end up being resolved when using object values rather than strings. When a user populates the input field and saves the form, I'd like to see the saved values reloaded back into the input field maintaining original format when updating page at a later time. -- View this message in context: http://tapestry.1045711.n5.nabble.com/ANN-Tapestry-tagselect-version-1-0-released-tp4639340p4683389.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
