new/update form patterns
new/update form patterns
- Subject: new/update form patterns
- From: Mike Schrag <email@hidden>
- Date: Thu, 26 May 2005 15:52:24 -0400
I'm curious what pattern people use for "new-EO" forms -- that is,
when you have a form to fill in the initial values of a new EO that
the user has requested to create. For instance, do most of you
create the EO up-front and attach the form fields directly to the
attributes of the EO, or do you clone the fields into the WOComponent
and attach to those, then move them into a new EO in the "save"
action? The problem with the first route is that if someone
navigates away, you've got an empty EO inserted into the EC and the
user doesn't realize that it's still sitting in their session, but
it's obviously nicer because you can just wire up directly to the EO
attributes and you don't have to keep the Component and the EO fields
in-sync (well, other than in the html/wod).
While I'm soliciting methodologies, I'm curious how many of you use
the ObjC/WO naming for accessor methods vs the JavaBeans convention
(i.e. do you use "name()" or "getName()"). WO has made me very
schizophrenic wrt my get method naming. I feel urges to name them
like WO/ObjC now and I don't know who is on the dark side in this
battle :) The ObjC-style has definitely grown on me, though.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden