I think you are right, it does get complex rather quickly. I've played with having a tab panel for related objects. Mine sat right below the edit form. It worked pretty well. One-to-many relationship tabs have a pageable table of related instances. One-to-one relationship tabs just have an editable form for the related object. It makes for a larger page object, but it feels natural to me to keep related stuff together on the same page.
One thing that would help is to be able to "bookmark" instances as you browse them. These can be candidates for adding to a relationship (like adding an employee to a manager, etc). Or just for speedier access to the instances you use most frequently. I'm interested in helping out since I need to do this anyways, but I'd probably push towards a more full-fledged project. - Jonathan Carlson >>> [EMAIL PROTECTED] 2005-07-11 4:45:03 PM >>> I've been thinking a bit more about the bean panel, and I'm kind of stuck. That is, there's too many possibilities! A simple bean is no problem. I have code in CVS for that now and it works (with a special case, FieldPanel, which lets you select a subset of the properties of the bean). The problem starts when you think about the more complex properties. E.g. a Person object that has an Address as a property. Usually, you'd want to give the Address its own edit form. But probably not in the same page as the Person form is (things would get messy pretty quickly). So, say you'd want to navigate to address edit from person edit. The current implementation I had was just a bunch of fields, no form, which has the advantage that you can decide to nest it in any form you like. Also it had no buttons (cancel, save), just the fields. Thing is, that we need the form and the buttons if we'd want to support the object browsing. And if we build that, we are allready halfway a Trails application. So, what do you guys think? What direction should the bean panel experiment head? Who is interested in cooperating, and where should we put it (in wicket-stuff, so that it can be a seperate full-fledged project with more people working on it, or in extensions in case we keep it really simple)? Eelco ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ______________________________________________________________________ This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Katun Corporation -- www.katun.com _____________________________________________________________________ ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
