Re: new/update form patterns
Re: new/update form patterns
- Subject: Re: new/update form patterns
- From: Geoff Hopson <email@hidden>
- Date: Fri, 27 May 2005 08:29:01 +0100
I second this. I find it much cleaner to have a formValues
NSMutableDictionary and have the key names the same as my EO attribute
names. In my WOD file I can bind text field values etc. to
'formValues.myAttribute. It also allows me to preset some defaults,
hide any hidden fields I may need, stuff like that. I can then easily
blat the dictionary into an inserted EO once I am pretty happy with
the data that has been collected.
Anyway, what do I know - I spend all my time in Tapestry, Hibernate
and HiveMind these days. You guys have it easy! :-)
Geoff
On 5/26/05, Jean-François Veillette <email@hidden> wrote:
> I forgot to mention another option that I used in some special
> situation :
>
> Instead of binding to an EO, bind to a NSMutableDictionary, then when
> you're ready to save, you can create your eo and apply the dictionary
> values to it (there is a method for that).
>
> Just thinking about it, if you put the correct type /** @Type MyEOClass
> */ before the mutabledictionary definition in your java class, you may
> (not tested) get WOBuilder to give you all the usual binding options.
>
> - jfv
>
> Le 05-05-26, à 15:52, Mike Schrag a écrit :
>
> > 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 You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
> _______________________________________________
> 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
>
_______________________________________________
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