Free form software for linux

WWW::Form is a module for handling the world-wide-web form process. The project enables generating forms, filling them from user input, verifying them, and re-displaying them in case something is wrong.

IPv4 form provides a tool for making RIPE IPv4 request forms.

IPv4 form is a utility for checking the #ADDRESSING PLAN# part of a RIPE IPv4 PA request form. It makes a "totals:" row for this form and produces readable output with spaces between columns. This output can be directly copied to a RIPE form.

Tie::Form is a Perl module to access a machine readable database file that minics a hardcopy form.

SYNOPSIS

require Tie::Form;

#####
# Using support methods and file handle with
# the file subroutines such as open(), readline()
# print(), close()
#
tie *FORM_FILEHANDLE, Tie::Form, @options
$form = tied *FORM_FILEHANDLE;

#####
# Using support methods only, no file subroutines
#
$form = Tie::Form->new(@options);

$encoded_fields = $form->decode_record($record);
@fields = $form->decode_field($encoded_fields);

$encoded_fields = $form->encode_field (@fields);
$record = $form->encode_record($encoded_fields);

$record = $form->get_record();

####
# Subroutine interface
#
$encoded_fields = decode_record($record);
@fields = decode_field($encoded_fields);

$encoded_fields = encode_field (@fields);
$record = encode_record($encoded_fields);

If a subroutine or method will process a list of options, @options, that subroutine will also process an array reference, @options, [@options], or hash reference, %options, {@options}.

eformmail project is a stand-alone CGI program that accepts an HTML form and emails it. The target email address is not buried in the HTML form, making it impossible for spammers to take advantage of this email address.
The output can be formatted by an XSLT processor, and form fields can be validated against a regular expression. A comprehensive manual is available.
Main features:
- Mail the contents of a form to an email address.
- The email address does not have to be present on the form, so it can not be used by email address harvesters in order to spam it.
- The contents of the email body that will be sent is completely configurable. eformmail can pipe the form data through an XSLT processor, so any formatting is possible.
- Supports both application/x-www-form-urlencoded and multipart/form-data encodings.
- It is possible to specify which fields must be validated. The contents should conform to the specified regular expression, else the email will not be sent.
- Single binary program. No PHP, Perl or other libraries needed.
- eformmail.cgi is protected against harvesting of web pages that might use it, in order to exploit it by sending spam through that web page.
Enhancements:
- A spam trap facility has been added, so form submissions that are obviously spam can be dismissed immediately.

Tk::form is a Perl module with a geometry manager based on attachment rules.

SYNOPSIS

$widget->form?(args)?
$widget->formOption?(args)?

The form method is used to communicate with the form Geometry Manager, a geometry manager that arranges the geometry of the children in a parent window according to attachment rules. The form geometry manager is very flexible and powerful; it can be used to emulate all the existing features of the Tk packer and placer geometry managers (see pack, place). The form method can have any of several forms, depending on Option:

$slave->form?(options)?

Sets or adjusts the attachment values of the slave window according to the -option=>value argument pairs.

-b => attachment

Abbreviation for the -bottom option.

-bottom => attachment

Specifies an attachment for the bottom edge of the slave window. The attachment must specified according to "SPECIFYING ATTACHMENTS" below.

-bottomspring => weight

Specifies the weight of the spring at the bottom edge of the slave window. See "USING SPRINGS" below.

-bp => value

Abbreviation for the -padbottom option.

-bs => weight

Abbreviation for the -bottomspring option.

-fill => style

Specifies the fillings when springs are used for this widget. The value must be x, y, both or none.

-in => $master

Places the slave window into the specified $master window. If the slave was originally in another master window, all attachment values with respect to the original master window are discarded. Even if the attachment values are the same as in the original master window, they need to be specified again. The -in flag, when needed, must appear as the first flag of options. Otherwise an error is generated.

-l => attachment

Abbreviation for the -left option.

-left => attachment

Specifies an attachment for the left edge of the slave window. The attachment must specified according to "SPECIFYING ATTACHMENTS" below.

-leftspring => weight

Specifies the weight of the spring at the left edge of the slave window. See "USING SPRINGS" below.

-lp => value

Abbreviation for the -padleft option.

-ls => weight

Abbreviation for the -leftspring option.

-padbottom => value

Specifies the amount of external padding to leave on the bottom side of the slave. The value may have any of the forms acceptable to Tk_GetPixels.

-padleft => value

Specifies the amount of external padding to leave on the left side of the slave.

-padright => value

Specifies the amount of external padding to leave on the right side of the slave.

-padtop => value

Specifies the amount of external padding to leave on the top side of the slave.

-padx => value

Specifies the amount of external padding to leave on both the left and the right sides of the slave.

-pady => value

Specifies the amount of external padding to leave on both the top and the bottom sides of the slave.

-r => attachment

Abbreviation for the -right option.

-right => attachment

Specifies an attachment for the right edge of the slave window. The attachment must specified according to "SPECIFYING ATTACHMENTS" below.

-rightspring => weight

Specifies the weight of the spring at the right edge of the slave window. See "USING SPRINGS" below.

-rp => value

Abbreviation for the -padright option.

-rs => weight

Abbreviation for the -rightspring option.

-t => attachment

Abbreviation for the -top option.

-top => attachment

Specifies an attachment for the top edge of the slave window. The attachment must specified according to "SPECIFYING ATTACHMENTS" below.

-topspring => weight

Specifies the weight of the spring at the top edge of the slave window. See "USING SPRINGS" below.

-tp => value

Abbreviation for the -padtop option.

-ts => weight

Abbreviation for the -topspring option.

$master->formCheck

This method checks whether there is circular dependency in the attachments of the masters slaves (see "CIRCULAR DEPENDENCY" below). It returns the Boolean value TRUE if it discover circular dependency and FALSE otherwise.

$slave->formForget

Removes the slave from its master and unmaps its window. The slave will no longer be managed by form. All attachment values with respect to its master window are discarded. If another slave is attached to this slave, then the attachment of the other slave will be changed to grid attachment based on its geometry.

$master->formGrid?(x_size, y_size)?

When x_size and y_size are given, this method returns the number of grids of the $master window in a pair of integers of the form (x_size, y_size). When both x_size and y_size are given, this method changes the number of horizontal and vertical grids on the master window.

$slave->formInfo?(-option)?

Queries the attachment options of a slave window. -option can be any of the options accepted by the form method. If -option is given, only the value of that option is returned. Otherwise, this method returns a list whose elements are the current configuration state of the slave given in the same option-value form that might be specified to form. The first two elements in this list list are "-in=>$master" where $master is the slaves master window.

$master->formSlaves

Returns a list of all of the slaves for the master window. The order of the slaves in the list is the same as their order in the packing order. If master has no slaves then an empty string is returned.

NeverForms is a collection of functions that helps with HTML form manipulation. The project interfaces MySQL tables to an HTML form.

The purpose is to provide abstraction of the database schema from the PHP code. Some inspiration came from Ruby Scaffold.

Data::CGIForm is a Perl module with form data interface.

Data::CGIForm is yet another way to parse and handle CGI form data. The main motivation behind this module was a simple specification based validator that could handle multiple values.
You probably dont want to use this module. CGI::Validate is a much more feature complete take on getting this sort of work done. You may then ask why this is on the CPAN, I ask that of myself from time to time....

SYNOPSIS

my %spec = (
username => qr/^([a-z0-9]+)$/,
password => {
regexp => qr/^([a-z0-9+])$/,
filter => [qw(strip_leading_ws, strip_trailing_ws)],
},
email => {
regexp => qr/^([a-z0-9@.]+)$/,
filter => &qualify_domain,
optional => 1,
errors => {
empty => You didnt enter an email address.,
invalid => Bad [% key %]: "[% value %]",
},
extra_test => &check_email_addr,
},
email2 => {
equal_to => email,
errors => {
unequal => Both email addresses must be the same.,
},
},
);

my $r = $ENV{MOD_PERL} ? Apache::Request->instance : CGI->new;

my $form = Data::CGIForm->new(datasource => $r, spec => %spec);


my @params = $form->params;
foreach $param (@params) {
next unless my $error_string = $form->error($param);

print STDERR $error_string;
}

if ($form->error(username)) {
handle_error($form->username, $form->error(username));
}

my $email = $form->param(email);
my $password = $form->password;

PloneFormGen provides a generic Plone form generator using fields, widgets and validators from Archetypes.

Actions like mailing or saving form input are incorporated by included plug-in adapters.

This product provides a generic Plone form generator using fields, widgets and validators from Archetypes. It makes it possible to build simple contact, information-gathering or data-entry forms through Plones interface.

To use it, create a form folder, then add form fields as contents. Individual fields can display and validate themselves for testing purposes. The form folder creates a form from all the contained field content objects.

Final disposition of form input is handled via plug in action products. Action adapters included with this release include a mailer and a save-data adapter that saves input in tab-separated format for later download. When you first add a form folder, its configured as simple response form with input mailed to the owner.

Since PloneFormGenerator uses Archetypes fields, widgets and validators, its also a good tool for rapidly prototyping forms intended for use with Archetypes-derived content types.