<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel about="http://blog.gmane.org/gmane.comp.lang.perl.modules.formbuilder">
    <title>gmane.comp.lang.perl.modules.formbuilder</title>
    <link>http://blog.gmane.org/gmane.comp.lang.perl.modules.formbuilder</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/951"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/948"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/943"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/940"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/937"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/936"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/932"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/931"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/930"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/927"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/925"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/924"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/923"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/922"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/920"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/919"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/918"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/916"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/914"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/910"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/951">
    <title>[FormBuilder] file/directory chooser for the server side?</title>
    <link>http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/951</link>
    <description>Hello,

I use Formbuilder to create usermin modules for my company. 
Now I need a file/directory chooser but for the remote files. 

With "$form-&gt;field(name =&gt; 'inputFile', label =&gt; 'Input file', type =&gt; file);"
I get as expected only a local file chooser. 

In the user-/webmin framework I could use "&amp;file_chooser_button" which gives 
me a file/directory chooser on the the server side. 
Is it possible to use "&amp;file_chooser_button" inside formbuilder or is there an 
other way to get an file/directory chooser dialog for the server side inside 
formbuilder?

regards,
Sascha
_______________________________________________
FBusers mailing list
FBusers&lt; at &gt;formbuilder.org
http://www.formbuilder.org/mailman/listinfo/fbusers

</description>
    <dc:creator>Sascha Brechenmacher</dc:creator>
    <dc:date>2007-03-08T09:24:12</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/948">
    <title>[FormBuilder] How to validate input not in list?</title>
    <link>http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/948</link>
    <description>_______________________________________________
FBusers mailing list
FBusers&lt; at &gt;formbuilder.org
http://www.formbuilder.org/mailman/listinfo/fbusers</description>
    <dc:creator>Kevin Jordan</dc:creator>
    <dc:date>2007-03-06T18:08:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/943">
    <title>[FormBuilder] requiring any of several fields</title>
    <link>http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/943</link>
    <description>As far as I can tell, there is no way to require that any one of
several fields be present.

I have an app where I need either field1 or field2 filled out. Neither
on its own is required, and a validate method attached to either field
would not detect when both are empty because it would never get
called!

The workaround for me is to inspect the form after it is submitted,
andmake sure one of the fields is set. If not, I mark one field as
invalid and set its message to something useful, then send the form
back to the user.

What would be more useful would be a formwide_validate callback that
checks the whole form, as opposed to a particular field like normal
validate. This would be the logical place to do what I'm trying to
accomplish.

$form-&gt;formwide_validate(sub{
  my $form = shift;
  ($form-&gt;field('foo') || $form-&gt;field('bar')) or return;
  return 1;
});
_______________________________________________
FBusers mailing list
FBusers&lt; at &gt;formbuilder.org
http://www.formbuilder.org/mailman/listinfo/fbusers

</description>
    <dc:creator>Ryan Tate</dc:creator>
    <dc:date>2007-03-04T01:22:43</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/940">
    <title>[FormBuilder] ETA on new release with mem leak fix and regexvalidation with commas?</title>
    <link>http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/940</link>
    <description>_______________________________________________
FBusers mailing list
FBusers&lt; at &gt;formbuilder.org
http://www.formbuilder.org/mailman/listinfo/fbusers</description>
    <dc:creator>Troy Davis</dc:creator>
    <dc:date>2007-03-02T16:10:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/937">
    <title>[FormBuilder] Newbie, question about formbuilder</title>
    <link>http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/937</link>
    <description>_______________________________________________
FBusers mailing list
FBusers&lt; at &gt;formbuilder.org
http://www.formbuilder.org/mailman/listinfo/fbusers</description>
    <dc:creator>Daniel Vela</dc:creator>
    <dc:date>2007-02-21T21:43:34</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/936">
    <title>[FormBuilder] how to attach formbuilder?</title>
    <link>http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/936</link>
    <description>_______________________________________________
FBusers mailing list
FBusers&lt; at &gt;formbuilder.org
http://www.formbuilder.org/mailman/listinfo/fbusers</description>
    <dc:creator>Mordion Gall</dc:creator>
    <dc:date>2007-02-12T21:58:33</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/932">
    <title>[FormBuilder] CGI::FB and XHTML 1.1</title>
    <link>http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/932</link>
    <description>I've been validating some of my applications using CGI::FB with the W3C
validator, and it seems that the 'name' and 'charset' attributes are not
allowed inside the &lt;form&gt; tag. However, setting a 'name' for the form is
essential in order to get special stylesheeting over elements with id's
like FormName_Field_Element. Also, setting 'charset' is useful for
internal uses. Not dumping name= and charset= in the &lt;form&gt; tag would be
nice, since it would still allow internal methods to access those
options while being XHTML 1.1 compliant.

I've been browsing the code but I can't point where the actual &lt;form&gt;
tag is built. In Template/Builtin.pm, however, I assume it's comming
from $form-&gt;text. I tried, unsuccesfully, to track $form down the parent
methods.

Maybe a 'compat' option in the new() method could prove useful (instead
of just changing this things to make CGI::FB compliant). Another change
that is needed is the removal of the &lt;noscript&gt; part in the JS output.

This could be accomplished avoiding "push &lt; at &gt;html</description>
    <dc:creator>José Parrella</dc:creator>
    <dc:date>2007-02-10T22:55:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/931">
    <title>[FormBuilder] Using UTF-8 templates in CGI::FB</title>
    <link>http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/931</link>
    <description>Greetings,

I've been developing a UTF-8 based Web application in spanish (es_ES)
with CGI::FormBuilder, which already provides templates for this
language. However, I get weird characters in all JS messages, as well as
errors from the W3C Validator. Please note that I'm not an expert in
this topic, but I think I've narrowed the problem to:

a) The es_ES.pm messages file is encoded in ISO-8859-1 (I opened it with
a UTF-8 aware text editor and rewrote it, then checked it with `file
es_ES.pm` which says that now it is a UTF-8 file)

b) The functions in FormBuilder.pm that write the actual JavaScript code
are using "return &lt;string&gt;", and this last step is not UTF-8 aware (I
don't know why, though). If I add "use Encode;" and then return
encode_utf8(&lt;string&gt;); I get the proper code in the HTML output.

Also, most scripts I checked in were not using "use utf8;". I don't know
if this is mandatory of if it actually helps with something, but just in
case. Can somebody explain to me a proper way to do UTF-8 based for</description>
    <dc:creator>José Parrella</dc:creator>
    <dc:date>2007-02-10T22:31:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/930">
    <title>[FormBuilder] validate + commas in  FB source files</title>
    <link>http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/930</link>
    <description>
hi all -- first off, CGI::FB is a great module.  it's saved me
countless hours of tedious mind-numbing typing.  thanks a lot to
nate and anyone else responsible.

i have a question about using CGI::FormBuilder::Source::File with
regexps in the validate field: one of the things i really want to do
is make sure the length of the input is between a min and max value:

  validate: /^\w{3,32}$/

and it seems like this sort of thing would be not atypical.
unfortunately, the regex is split into two values when there's a comma
in the regex (via $source-&gt;write_module()):

  'validate' =&gt; [
                  '/^\\w{3',
                  '32}$/'

so : is there a canonical way of checking for min/max length that i'm
not aware of?  

would there be any interest in changing File.pm (~ line 155) from:

   # split commas
   &lt; at &gt;val = split /\s*,\s*/, $line;

to something like:

   # split commas
   my $split_regex = lc $term eq 'validate'
     ? qr/\s*(?&lt;!\\),\s*/ : qr/\s*,\s*/;
   &lt; at &gt;val = split $split_regex, $line;

which wou</description>
    <dc:creator>kevin montuori</dc:creator>
    <dc:date>2007-02-09T22:56:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/927">
    <title>[FormBuilder] Default Values.</title>
    <link>http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/927</link>
    <description>Hello All,

Just want to start out by saying, this is a really great API and easy
to use. Which must be my problem. Below is the code I'm working with.
The problem I'm having is that I can't get the radio button or
checkbox to be either on or off. The $notact with either be 1 or 0,
yet nothing is checked. I thought I was doing what the documentation
was telling me. Can anyone see what I'm doing wrong?

sub edituser {
&amp;noauth if !&amp;admin;
&amp;phead;
my $stmt="select Users.Username, Users.Password, Users.BmsCustId,
Users.Email, Users.FullName, Users.NotActive, Groups.Group as fGroup
from Users
        left join Groups on Groups.pkey = Users.Group
where Users.pkey=$input{edituser}";

my $h=$dbh-&gt;selectrow_hashref($stmt);
print dumper_html($h);
my $notact=$h-&gt;{NotActive};
delete $h-&gt;{NotActive};

my $group=$dbh-&gt;selectall_arrayref("select Groups.Group from Groups");

$form = CGI::FormBuilder-&gt;new(
fields =&gt;$h,
smartness =&gt; 2,
);
$form-&gt;field(name=&gt;'NotActive', value=&gt; $notact, options=&gt;"Deacti</description>
    <dc:creator>Hornet</dc:creator>
    <dc:date>2007-02-05T22:44:32</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/925">
    <title>[FormBuilder] Dynamic fields and templates</title>
    <link>http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/925</link>
    <description>Hi,

I'm tying to build a form where most of the fields are standard fields, laid 
out via a template, but with a section where some fields may or may not be 
added dynamically, depending on the record type I'm editing.

The idea was that at run time I'd do something like:

my $tmpl = HTML::Template-&gt;new( ...)
$tmpl-&gt;param('form-start'  =&gt; "&lt;tmpl_var form-start&gt;"); 
$tmpl-&gt;param('form-submit' =&gt; "&lt;tmpl_var form-submit&gt;");
# all standard field template tags get replaced by themselves
# for FormBuilder to expand ...

$tmpl-&gt;param('dynamic-controls' =&gt; \&lt; at &gt;list_of_extra_fields);

# Now create the form object
my $form-&gt;CGI::FormBuilder-&gt;new( 
  fields =&gt;\&lt; at &gt;list_of_all_fields,
  template =&gt; $tmpl,
   ....
);

This fails because $tmpl is an HTML::Template object and doesn't have a 
render() method.

Is subclassing CGI::FormBuilder::Template::HTML the only way to get something 
like this to work?   It seems odd that the template attribute can be an 
object reference but NOT an HTML::Template reference.
_______________</description>
    <dc:creator>Dan Axtell</dc:creator>
    <dc:date>2007-02-04T20:33:25</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/924">
    <title>[FormBuilder] FormBuilder and Data::FormValidator</title>
    <link>http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/924</link>
    <description>Hi all,

I've been using FormBuilder and Data::FormValidator together, but have run into
a few fairly minor problems.

1. Unless you remember to put a field in "optional" list in the
Data::FormValidator profile, it won't be checked or filtered or anything. This
logic is slightly different to FormBuilder's, where there isn't really a
difference between optional and "not required".

2. A Data::FormValidator constraint which isn't specific to just one field (for
example, a 'require_some') causes FormBuilder to create a new fictitous text
field with the name of the contraint and with the constraint's error message.
The error ought to be reported at the level of the form, rather as an error on
any one field. This I managed to correct just by using some css to hide the
field leaving the message.

3. These modules don't seem to work correctly together for fields with options
and other=&gt;1. Instead of returning the value of the "other" text field, it
returns the name of the field.

Other than these minor and avoidabl</description>
    <dc:creator>Mike Scoltock</dc:creator>
    <dc:date>2007-02-04T12:29:15</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/923">
    <title>[FormBuilder] Multipage forms in Catalyst</title>
    <link>http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/923</link>
    <description>Greetings,

I've been trying to setup a few sites which need to implement multipage
forms, under Catalyst. I've read the tutorial in formbuilder.org
regarding multipage forms, and I've tried two different ways for this:

1) Setting up the first page is easy with C::Plugin::FB, and the
YAML-based source files. Therefore I use a single Local Form method in
Catalyst, and the form posts to itself. My whole method is a:

if ($c-&gt;form-&gt;submitted &amp;&amp; $c-&gt;form-&gt;validate) {
     ... actions
}

Since I'm taking profit of the fact that using TT2, the template name is
setup by default to /root/&lt;path&gt;.tt2. When the user is entering the
first page, $c-&gt;form isn't submitted nor validated, and it opens the
default template, which has a single form.render and "calls" the .fb
file to get the form configuration. Nice.

Of course, when a user enters some information and submits the form, I
get into my if statement (the form is submitted and validates), and I
can do all my DB stuff, etc. But if I want a second form to show up, I
</description>
    <dc:creator>José Parrella</dc:creator>
    <dc:date>2007-02-03T19:16:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/922">
    <title>[FormBuilder] &lt;tr&gt; HTML attributes</title>
    <link>http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/922</link>
    <description>When using CGI::FB in a standard way to build a form, I was interested
in the jsclick option in order to provide a quick effect from
Scriptaculous in my forms: if a radio button was clicked, some rows
needed to appear.

This requires me to set an id="" attribute in the desired &lt;tr&gt;'s (which
CGI::FB already does: FormName_FieldName_label) but also to set inline
display: none; style attributes in order to "hide" the rows when the
form loads.

I can't specify them through CSS because of a del.icio.us feature, but I
didn't see an option to specify &lt;tr&gt; attributes (just &lt;td&gt;). I patched
CGI::FB in order to have this done, but I could also have used a
particular template, of course. Is there any other way to achieve this
which is currently available in FB? Would it be useful if we could
specify &lt;tr&gt; attributes through CGI::FB?

Thanks a lot,
Jose

</description>
    <dc:creator>José Parrella</dc:creator>
    <dc:date>2007-02-03T19:15:23</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/920">
    <title>[FormBuilder] CGI::FormBuilder memory leak fix</title>
    <link>http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/920</link>
    <description>_______________________________________________
FBusers mailing list
FBusers&lt; at &gt;formbuilder.org
http://www.formbuilder.org/mailman/listinfo/fbusers</description>
    <dc:creator>Victor Igumnov</dc:creator>
    <dc:date>2007-02-01T00:37:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/919">
    <title>[FormBuilder] Form With Multiple (Nested?) Submit</title>
    <link>http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/919</link>
    <description>_______________________________________________
FBusers mailing list
FBusers&lt; at &gt;formbuilder.org
http://www.formbuilder.org/mailman/listinfo/fbusers</description>
    <dc:creator>Dennis Daupert</dc:creator>
    <dc:date>2007-01-31T14:31:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/918">
    <title>[FormBuilder] Hmm, Here is a patch which will remove auto generatedcomment in result html, Also, with small enhancement. ; -)</title>
    <link>http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/918</link>
    <description>Hello,
All.
FormBuilder rocks anyway. But normally, There is something we don't want.
In any case, You don't like to see the message like
&lt;!-- Generated by CGI::FormBuilder v$VERSION available from
www.formbuilder.org --&gt;
But It seems there is no option to remove this without patching the source.
Touch symbol table works fine. But doesn't work well when we are in
Catalyst::Controller::FormBuilder.
So this patch did this. It won't show the hidden trailer if you set
debug option off.

Another small enhancement is.
I add a browser_compat option (Default is 1). The one which most
people like. ;-)
If It is set to 0.
Then, You won't see the
&lt;!-- hide from old browsers
blablabla
//--&gt;
Things in generated javascript.
Modern browsers.
Even lynx and w3m, can deal with unknown tags correctly.
And I need this feature also. ;-)

Any suggestions welcome.

Xinming
_______________________________________________
FBusers mailing list
FBusers&lt; at &gt;formbuilder.org
http://www.formbuilder.org/mailman/listinfo/fbusers</description>
    <dc:creator>Yiyi Hu</dc:creator>
    <dc:date>2007-01-29T16:26:21</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/916">
    <title>[FormBuilder] Adding paragraph/hr/password elements to FormBuilderforms</title>
    <link>http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/916</link>
    <description>Hi,

Is it possible to add paragraph/horizontalrule/password elements to
FormBuilder forms? And if so, how is this achieved?

Many thanks,

Anthony

_______________________________________________
FBusers mailing list
FBusers&lt; at &gt;formbuilder.org
http://www.formbuilder.org/mailman/listinfo/fbusers

</description>
    <dc:creator>Anthony Gladdish</dc:creator>
    <dc:date>2007-01-26T09:43:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/914">
    <title>[FormBuilder] Date fields</title>
    <link>http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/914</link>
    <description>Hey folks,

I just started playing around with FB and I wonder if you can suggest some
possibilities to include nice date fields into a form? I don't want my users
to enter error-prone MM/DD/YYYY dates in a stupid text field but rather I'd
like to have three select lists (monthnames, day, yearlist) per date field.

Before I started to use FB I had a homegrown form solution which had an
additional "date" fieldtype that spit out those three columns and
verified the date.

AFAICT from looking at the FB source this should be doable by adding something
like a CGI::FormBuilder::Field::date class, right? Has somebody here already
tried something like this?

Thanks for any suggestions!

--Tobias
_______________________________________________
FBusers mailing list
FBusers&lt; at &gt;formbuilder.org
http://www.formbuilder.org/mailman/listinfo/fbusers

</description>
    <dc:creator>Tobias Kremer</dc:creator>
    <dc:date>2007-01-23T09:57:54</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/910">
    <title>[FormBuilder] FB, Apache2 &amp; Mason</title>
    <link>http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/910</link>
    <description>I'm being forced into migrating my current FB, Apache, Mason code to  
Apache2. I'm having trouble getting FB to be able access the  
submitted form data. In the past I simply created the new form object  
with params =&gt; $r and everything was OK.This doesn't work now.

I've tried using Apache2::Request-&gt;new($r) and CGI-&gt;new($r) instead  
but neither was successful.
I get the feeling I'm missing something fairly simple so thought I'd  
ask if anyone else has a setup like this and could help me see the  
light!

Thanks,

Guy
_______________________________________________
FBusers mailing list
FBusers&lt; at &gt;formbuilder.org
http://www.formbuilder.org/mailman/listinfo/fbusers

</description>
    <dc:creator>Guy Parker</dc:creator>
    <dc:date>2007-01-16T10:23:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/909">
    <title>[FormBuilder] Showing label rather than value in select duringconfirm</title>
    <link>http://comments.gmane.org/gmane.comp.lang.perl.modules.formbuilder/909</link>
    <description>When saving a forms-worth of data to the database, one of the fields is 
derived from a SELECT pull down. This SELECT input has different values 
and labels. It looks something like

&lt;select name="employee_id"&gt;
&lt;option value="1"&gt;Able&lt;/option&gt;
&lt;option value="2"&gt;Baker&lt;/option&gt;
&lt;option value="3"&gt;Charlie&lt;/option&gt;
&lt;/select&gt;

When I get to the confirm screen I want the "employee_id" line to show 
to the user the label (e.g., "Baker") but instead it gives the value 
(e.g., "2"). How can I get the confirm screen to show the label rather 
than the value *without* having to resort to using a template?

What would be nice if there were an property of the field object that 
specified what to display in the confirm screen as override.
_______________________________________________
FBusers mailing list
FBusers&lt; at &gt;formbuilder.org
http://www.formbuilder.org/mailman/listinfo/fbusers

</description>
    <dc:creator>cgiformbuilder331&lt; at &gt;lewenberg.com</dc:creator>
    <dc:date>2007-01-11T05:40:03</dc:date>
  </item>
  <textinput about="http://search.gmane.org/?group=$group=gmane.comp.lang.perl.modules.formbuilder">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.lang.perl.modules.formbuilder</link>
  </textinput>
</rdf:RDF>
