Oh, nevermind. I've been looking at Eelco's beanedit code, and he's already got most of it done for me. I'm just gonna give it a shot and see how it comes out.
-Phil On 7/15/05, Phil Kulak <[EMAIL PROTECTED]> wrote: > .NET has this GridView component that will display data from a table. > What's nice about it is that you can click on a row and all the labels > turn into form components, you can then edit them, and they save back > to the database. I've ported that to Wicket in the standard Wicket > way, with callbacks to populate ListItems, set column headers (and add > OrderByLinks if you want to sort on headers), and do something with > the edited row on submit. > > This seems to work nicely (I'll commit it later today), but I'm > wondering if I should try to make it as automated as it is in .NET. > Basically, this will mean allowing the component to write to the > database. I've never liked this pattern myself because it brings your > DAO right into your view layer, but it's also gratifying to just throw > a panel onto a page and have a paging, sortable, editable list for > free. It would be somewhat like Eelco's BeanEdit, and possibly sharing > a lot of its code. Anyway, I was just wondering if anyone thought this > was a worthwhile effort. > > Another idea is to not use a panel, but to have a default onSubmit() > behavior that updates the database, and a delete link that deletes > from the database. > ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
