Re: Re: db_dataobject_formbuilder and checkbox

From: Date: Thu, 06 Jan 2005 20:58:30 +0000
Subject: Re: Re: db_dataobject_formbuilder and checkbox
References: 1 2 3 4 5 6 7 8  Groups: php.pear.general 
Request: Send a blank email to pear-general+get-16749@lists.php.net to get a copy of this message
On Thu, 6 Jan 2005 10:13:29 -0800, Justin Patrin <papercrane@gmail.com> wrote: > On Thu, 06 Jan 2005 17:42:48 +0100, Arne Gellhaus > <arne.gellhaus@gellhaus.de> wrote: > > Markus Wolff wrote: > > > > > Actually, I don't see the value in adding yet another option for > > > boolean fields when this can easily be done with enum. I mean, > > > configuring an enum field to accept only "yes" or "no" is not > > > that > > > hard, and you'd need similar configuration for a boolean field to > > > determine what values it should write into the database anyway (i.e. > > > 0/1 vs. 'Y'/'N' etc.). > > > > It is not about the fieldtype in the database but about the presentation > > to the user. A checkbox field is easier to handle and is the standard > > way to ask a user for yes/no descisions. I think a select field with > > only 2 entries is worthless and 2 radio buttons are harder to spot, so i > > prefer a checkbox. > > > > When I mentioned a select box or radio buttons I only meant that if we > include boolean support that people *will* ask for it. I understand > that you would rather a checkbox. > > It would be lovely if you would contribute a patch, but be forewarned > that there's lots of internal stuff to FB. If you aren't familiar with > the code it may take a while to get into it. A simple patch for > checkboxes only should be <10 lines added I think. It should also be > possible to leverage current enum support for Yes/No, Y/N support, > although the value of the field would not be right... > Oh, and always use the CVS version of a package when creating a patch. Otherwise it can make it hard to apply. -- Justin Patrin

« previous php.pear.general (#16749) next »