Free 7 000 software for linux

CGI::Validate is an advanced CGI form parser and type validation.

SYNOPSIS

use CGI::Validate; # GetFormData() only
use CGI::Validate qw(:standard); # Normal use
use CGI::Validate qw(:subs); # Just functions
use CGI::Validate qw(:vars); # Just exception vars

## If you dont want it to check that every requested
## element arrived you can use this. But I dont recommend it
## for most users.
$CGI::Validate::Complete = 0;

## If you dont care that some fields in the form dont
## actually match what you asked for. -I dont recommend
## this unless you REALLY know what youre doing because this
## normally meens youve got typos in your HTML and we cant
## catch them if you set this.
## $CGI::Validate::IgnoreNonMatchingFields = 1;

my $FieldOne = Default String;
my $FieldTwo = 8;
my $FieldThree = some default string;
my @FieldFour = (); ## For multi-select field
my @FieldFive = (); ## Ditto
my $EmailAddress= ;

## Try...
my $Query = GetFormData (
FieldOne=s => $FieldOne, ## Required string
FieldTwo=i => $FieldTwo, ## Required int
FieldThree => $FieldThree, ## Auto converted to the ":s" type
FieldFour=s => @FieldFour, ## Multi-select field of strings
FieldFive=f => @FieldFive, ## Multi-select field of floats
Email=e => $EmailAddress, ## Must look like an email address
) or do {
## Catch... (wouldnt you just love a case statement here?)
if (%Missing) {
die "Missing form elements: " . join ( , keys %Missing);
} elsif (%Invalid) {
die "Invalid form elements: " . join ( , keys %Invalid);
} elsif (%Blank) {
die "Blank form elements: " . join ( , keys %Blank);
} elsif (%InvalidType) {
die "Invalid data types for fields: " . join ( , keys %InvalidType);
} else {
die "GetFormData() exception: $CGI::Validate::Error";
}
};

## If you only want to check the form data, but dont want to
## have CGI::Validate set anything use this. -You still have full
## access to the data via the normal B object that is returned.

use CGI::Validate qw(CheckFormData); # not exported by default
my $Query = CheckFormData (
FieldOne=s, FieldTwo=i, FieldThree, FieldFour,
FieldFive, Email,
) or do {
... Same exceptions available as GetFormData above ...
};

## Need some of your own validation code to be used? Here is how you do it.
addExtensions (
myType => sub { $_[0] =~ /test/ },
fooBar => &fooBar,
i_modify_the_actual_data => sub {
if ($_[0] =~ /test/) { ## data validation
$_[0] = whatever; ## modify the data by alias
return 1;
} else {
return 0;
}
},
);
my $Query = GetFormData (
foo=xmyType => $foo,
bar=xfooBar => $bar,
cat=xi_modify_the_actual_data => $cat,
);


## Builtin data type checks available are:
s string # Any non-zero length value
w word # Must have at least one w char
i integer # Integer value
f float # Float value
e email # Must match m/^s*]+@[^@.]+(?:.[^@.]+)+>?s*$/
x extension # User extension type. See EXTENSIONS below.

Basicly a blending of the CGI and Getopt::Long modules, and requires the CGI module to function.

The basic concept of this module is to combine the best features of the CGI and Getopt::Long modules. The CGI module is great for parsing, building, and rebuilding forms, however it lacks any real error checking abilitys such as misspelled form input names, the data types received from them, missing values, etc. This however, is something that the Getopt::Long module is vary good at doing. So, basicly this module is a layer that collects the data using the CGI module and passes it to routines to do type validation and name consistency checks all in one clean try/catch style block.

The syntax of GetFormData() is mostly the same as the GetOptions() of Getopt::Long, with a few exceptions (namely, the handling of exceptions) . See the VALUE TYPES section for detail of the available types, and the EXCEPTIONS section for exception handling options. If given without a type, fields are assumed to be type ":s" (optional string), which is normally correct.
If successful, GetFormData() returns the CGI object that it used to parse the data incase you want to use it for anything else, and undef otherwise.

If you only want to do value type and name validation, use CheckFormData() instead with a field=type list. -See the SYNOPSIS for an example.

Language::Logo Perl module is an implementation of the Logo programming language.

SYNOPSIS

use Language::Logo;

my $lo = new Logo(update => 20);

$lo->command("setxy 250 256");
$lo->command("color yellow");
$lo->command("pendown");

# Draw a circle
for (my $i = 0; $i < 360; $i += 10) {
$lo->command("forward 10; right 10");
}

$lo->disconnect("Finished...")

This module provides an implementation of the Logo programming language, with all of the necessary drawing primitives in a Tk Canvas. The Canvas object is also referred to as the "screen".

The first construction of a Language::Logo object causes a server to be created in a separate process; this server then creates a Tk GUI with a Tk::Canvas for use by the clients "turtle", and responds to all requests from the clients commands. In this way, multiple clients may be constructed simultaneously -- each one with its own "turtle".

In this first release, not all of the Logo language is implemented. Rather, the primary commands available are those which directly affect the turtle, and are related to drawing on the screen. The intent is to use the Logo in conjunction with Perl as a sort of "hybrid" language; Perl us used as the higher-level language layer through which all loop constructs, conditionals, and data-manipulation is done. This allows for a substantial level of programming power.

Dabo is a three-tier, cross-platform database application development framework, written in Python with the wxPython GUI toolkit.
Dabos authors, Ed Leafe and Paul McNett, have strong backgrounds in database application development using the awesome and underrated Microsoft Visual FoxPro development environment.
While Visual FoxPro shines at developing data-centric applications, it has one limitation that cannot be ignored: it only runs on Microsoft Windows, and Ed and Paul both have clients that want their applications to run on Linux and Macintosh. We are sure we are not alone in this regard: it is a multi-platform world with more diverse needs than one vendor can fulfill.
Ed and Paul got to talking one day: Paul had been researching various multiplatform GUI toolkits for about 18 months, and Ed has lots of experience developing the Visual FoxPro Codebook framework. We decided to work together to make a framework for developing robust data-centric applications for multi-platform deployment. Weve come up with a design that is simple, flexible, and robust, and weve begun developing our own client applications using the Dabo framework.
Dabo is not complete, but is very capable now for many needs.
Currently, Dabo only supports MySQL and Firebird backends (with PostgreSQL almost done), but in the near future it will support all databases that have drivers that conform to the Python dbapi. These databases include:
- MySQL (already supported)
- PostgreSQL(already supported)
- Firebird (already supported)
- Oracle
- DB2
- MS-SQL and MSDE
- Sybase
- PySQLite
- Berkeley DB

KompoZer is Nvus unofficial bug-fix release.
Main features:
HTML Editor
- fixed: the HTML 4.01 doctype is now standard (instead of quirks)
- fixed: the editor correctly selects a tab when re-loading a file thats currently edited
- fixed: the editor correctly updates the window title when closing a tab (avoids crashes)
- added: its always possible to revert the current page
- fixed: the PHP/Comment dialog is resizable
- fixed: the current page is marked as modified after changing a PHP/Comment
- added: the format toolbar has been splitted in two
- added: relativize local URLs in the markup cleaner
- TODO: option to launch the markup cleaner before saving/publishing
- added: show id/class attributes in the status bar
- fixed: id/class attributes can be properly removed with the status bar context menu
- fixed: inline style dialogs have a localized title
- fixed: doctype prefs are kept when a new document is created
CSS Editor
- fixed: the CSS Editor becomes a real dialog box (with a OK/Cancel buttons)
- fixed: the CSS Editor fits on an SVGA screen (800*600), even on MacOS X
- added: graphical toolbar buttons
- added: modified flags on stylesheets
- added: edit style rules in text mode (CSS Editor / Advanced properties)
- added: keyboard shortcut (F11) to open the CSS Editor
- fixed: external stylesheets can be saved on the hard disk
- fixed: better serialization of CSS files
- fixed: real-time preview
- fixed: lots of UI bugs
Site Manager
- TODO: when a file is dropped onto the main panel, a relative reference is created
- TODO: local files are allowed
- TODO: more file types (with custom extension list)
- TODO: external application support
- TODO: preferences tab

JCommander is a next generation file manager targeted to be powerful and flexible.

Being multi-platform and distributed under an open-source license, it is freely usable on virtually any platform and operating system.

The idea behind dvbd is to make maximum use of your DVB card by allowing multiple channels on the same frequency to be tuned. It is split into a daemon (dvbd) and client programs (dvbcat, dvbsched, dvblist). It is possible to associate a priority with a connection to the daemon, so that (depending on the given priority) the tuner can be made available by dropping connections of inferior priority.

A web frontend to dvbsched, called dvbdguide, is included to facilitate the scheduling of dvbd recording activities. Please note this requires an XMLTV datafeed. Check out a captured dvbdguide page.

The daemon has a configuration file which by default is /etc/dvbd/config. The format of the file is lines of key=value. Line comments can be begun with #.

The following configuration options are available:

socket
the (unix) socket to listen on. Default is /var/run/dvbd/dvbd.socket
pid
the pid file to write to once it has become a daemon. Default is /var/run/dvbd/dvbd.pid
log
the log file to write to. Default is /var/log/dvbd.log
schedule
the schedule file to write to. Default is /var/spool/dvbd/schedule
debug
the debug level (default is 0) If a higher debug level is set, dvbd will not go into the background.
numcards
the number of DVB cards your system supports
card0
the first DVB card. The format of this field is type:frontend:channels Where

type may be one of dvb-t, dvb-s or dvb-t.
frontend is the path to the frontend (tuner) for the card
channels is the path to the tzap/szap/czap format channels.conf file for the card.

If no cards are specified, a default of one dvb-t card is assumed with channels file /etc/tzap.channels.conf and frontend /dev/dvb/adapter0/frontend0

At the moment there are three client programs. dvbcat, dvblist and dvbsched. dvbcat can be used to extract a stream from the dvbd for live TV.

For example:

$ dvbcat dvb-t "BBC ONE" | mplayer -

dvbsched is used to schedule a recording. Note that an output file must be specified whose containing directory must be owned by the user issuing the request. The directory must also be writable by the dvbd program.

The time format is in at(1) format. See ats manpage for more information about it.

For example:

mkdir /tmp/recordings
dvbsched dvb-t "ITV 2" 19.20 32 /tmp/recordings/itv2.mpg

If there is a clash the program will ask you if you want to cancel your job.

dvblist shows the channels available to tune at the given priority (default is 10).

For example:

dvblist dvb-t

If there are some existing connections the list of channels may be shorter than the full list.

ASNMTAP::Asnmtap is an object-oriented Base Class to build modules that provides a nice object oriented interface for ASNMTAP.

SYNOPSIS

use ASNMTAP::Asnmtap;

my $objectAsnmtap = ASNMTAP::Asnmtap->new (
_programName => test-asnmtap.pl,
_programDescription => "Test ASNMTAP::Asnmtap",
_programVersion => 3.000.011,
_programUsagePrefix => [--commandLineOption],
_programHelpPrefix => "--commandLineOption ...",
_programGetOptions => [commandLineOption=s],
_timeout => 30,
_debug => 1);

my $verbose = $objectAsnmtap->getOptionsArgv (verbose);
print "getOptionsArgv: verbose = $verbosen" if (defined $verbose);

my $dumpData = $objectAsnmtap->getOptionsArgv (dumpData);
$objectAsnmtap->dumpData () if (defined $dumpData);

my $commandLineOption = $objectAsnmtap->getOptionsArgv (commandLineOption);
print "getOptionsArgv : commandLineOption = $commandLineOptionn" if (defined $commandLineOption);

Xlayout is a simple utility for controlling X11 windows and pointer from the console or remotely.
It can alter the geometry of a window, the position of the pointer, hide a window or send it to the top, list all windows, and get the current pointer position.
For use in scripts, it has the ability to return a status result ("1" for error, "0" for success). It can also ease windows into location.
Enhancements:
- Beta testing has begun.
- This release includes features to display information on the current screens connected.
- Some of the convenience methods were smoothed out.
- Bugfixes were made for the user input.
- A lot of code tidy ups were done.