I've never built an app in Swing in my life...so I can't relate. I'm guessing you'll have lots of users/developers like me going forward who are in the same boat.
The basic concepts of using a model to populate and access items in List-bound widgets is very easy to understand...it's when I had to pre-populate and pre-select items that it got hairy and didn't quite behave as I would have expected. If you look through the list you'll see a rather long back and forth between Igor any myself on where I was having problems w/ this. Otherwise, models aren't that hard to grasp once you've used them a couple times. I was able to go back later and use other widgets w/ relative ease after my DropDownChoice experience. On 5/5/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
> > One thing I found particularly awkward was how models work in some of > the form widgets, i.e. DropDownChoice, ListMultipleChoice, etc. This > is where I found the Wicket learning curve was greater because it > wasn't nearly as intuitive as I had expected. Strange thing is they work exactly like Swing Comboboxes and Lists.. The selected objects are just the objects that are in the total list. And you have a Renderer that displays the objects.. (to display a text in a label that is the "toString" of the object) The only difference is is that in wicket you also need to generate a String id because we need that to send to the browser. johan
------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
