thx Am 08.02.2013 um 18:05 schrieb "Thiago H de Paula Figueiredo [via Tapestry]" <ml-node+s1045711n5719890...@n5.nabble.com>:
> On Fri, 08 Feb 2013 14:19:06 -0200, sommeralex > <[hidden email]> wrote: > > > Thank you again for your answer. I guess my confusion with tapestry is > > that it does so many things (which I would never expect it to do but I > > am happy with) one the one hand. On the other hand, other things - for > > sure - have to be implemented and cant be expected. Even to cache the > > selectModel. > > That's not something you should expect. Tapestry, specifically, Select, is > expected to just use the SelectModel you pass to it, nothing more than > that. You know when stuff should be cached, not Tapestry. > > > And another reason / i hope you forgive / is just this, left to my chair: > > http://www.learnclip.com/linda.jpg :-) > > Cute! :D > > -- > Thiago H. de Paula Figueiredo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [hidden email] > For additional commands, e-mail: [hidden email] > > > > If you reply to this email, your message will be added to the discussion > below: > http://tapestry.1045711.n5.nabble.com/Dynamic-OptionModel-Implementation-How-To-tp5719875p5719890.html > To unsubscribe from Dynamic OptionModel Implementation: How To?, click here. > NAML -- View this message in context: http://tapestry.1045711.n5.nabble.com/Dynamic-OptionModel-Implementation-How-To-tp5719875p5719891.html Sent from the Tapestry - User mailing list archive at Nabble.com.
