Changeset 26 in text-formbuilder for trunk

Timestamp:

11/16/04 16:04:33 (20 years ago)

Author:

peter

Message:

updated docs and version number

File:

• trunk/lib/Text/FormBuilder.pm (modified) (6 diffs)

trunk/lib/Text/FormBuilder.pm

@@ -6 +6 @@
 use vars qw($VERSION);
 
-$VERSION = '0.06';
+$VERSION = '0.06_01';
 
 use Carp;
@@ -659 +659 @@
 inside curly braces. Whitespace between values is irrelevant.
 
-To add more descriptive display text to a vlaue in a list, add a square-bracketed
+To add more descriptive display text to a value in a list, add a square-bracketed
 ``subscript,'' as in:
 
@@ -665 +665 @@
 
 If you have a list of options that is too long to fit comfortably on one line,
-consider using the C<!list> directive:
+you should use the C<!list> directive:
 
     !list MONTHS {
@@ -690 +690 @@
 enough with the CGI::FormBuilder object directly.>
 
+If you want to have a single checkbox (e.g. for a field that says ``I want to
+recieve more information''), you can just specify the type as checkbox without
+supplying any options:
+
+    moreinfo|I want to recieve more information:checkbox
+
+The one drawback to this is that the label to the checkbox will still appear
+to the left of the field. I am leaving it this way for now, but if enough
+people would like this to change, I may make single-option checkboxes a special
+case and put the label on the right.
+
 You can also supply a default value to the field. To get a default value of
 C<green> for the color field:
@@ -746 +757 @@
 =head1 BUGS
 
+For now, checkboxes with a single value still display their labels on
+the left.
+
 =head1 SEE ALSO
 
@@ -752 +766 @@
 =head1 THANKS
 
-Thanks to eszpee for pointing out some bugs in the default value parsing.
+Thanks to eszpee for pointing out some bugs in the default value parsing,
+as well as some suggestions for i18n/l10n and splitting up long forms into
+sections (that as of this release are still on the TODO list ;-).
 
 =head1 AUTHOR