Trails have this, and also shows dates as datefields, OneToMany as a working
klickable list (with new and delete below) and ManyToOne as a drop-down
Option.

It also includes aceti security, where the users and roles are also listable
and editable in the very framework, since they're also just tables.

Supports hsqldb, postgresql and mysql. I use mysql and just let trails fix
all the list and edit pages as well as the hibernation stuff, then I add
annotations until I've hidden as much as I please, then use Tapestry when
needed. Very sweet.

This is current subversion, though.

https://trails.dev.java.net/

Cheers,
PS

On 3/16/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
>
> You might want to check out the trails project, but I don't know if this
> edit page exists anywhere yet. It would be great if someone implements it
> though.
>
> See
> http://howardlewisship.com/blog/2006/03/from-fanciful-ideas-category.html.
>
> When I'm finished with 4.1 development I plan on doing a lot of things
> over
> at honeycomb if they're not already done by the time I get to it. (like
> this
> edit page idea) . Hopefully someone else will save us the trouble :)
>
> On 3/16/06, Greg Cormier <[EMAIL PROTECTED]> wrote:
> >
> > I'm writing a web app that's used to manage a lot of tables in a
> database.
> > So we'll have some simple tables, like a table for contact information,
> a
> > table for department listings, a table for this, for that.
> >
> > They all have an "edit" page, which at the moment, I usually copy/paste
> > one of the other page/html/BasePage, and modify them for the different
> > fields. So I'll change "firstName" and "lastName" on two textboxes to
> > "departmentTitle" and "departmentBranch", change the "selectedObject"
> > property's type to whatever that page is editing.
> >
> > Basically, a lot of simple forms with a textbox for every column (except
> > the primary key).
> >
> > So my question, is there some neat way to do this dynamically with
> > reflection?
> >
> > I could look up every property of the object, then auto-generate this
> edit
> > page? The "save" button would just call a hibernate saveOrUpdate()
> method
> > which can take any object. I've done something like this with my
> > confirmation page when someone wants to delete something. I pass a
> > "selectedObject" and "objectDAO" to the page, so the page says "Are you
> sure
> > you want to delete?", if they hit yes, it just calls the DAO's delete
> > method. So if they're browsing a department, when they select and hit
> > Delete, the delete handler sets the objectDAO to the DepartmentDAO
> object. I
> > thought that was really cool how I can use 1 page everywhere, and if I
> could
> > find a way to get some crazy editing page (obviously I'd need some
> > properties to pass to it, like which fields to hide), I'd eliminate a
> TON of
> > pages!!!
> >
> > Thanks!
> > Greg
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>

Reply via email to