Free dt software for linux

XML::DT is a package for down translation of XML files.

SYNOPSIS

use XML::DT;

%xml=( music => sub{"Music from: $cn"},
lyrics => sub{"Lyrics from: $v{name}n"},
title => sub{ uc($c) },
-default => sub{"$q:$c"} );

print dt($filename,%xml);

ABSTRACT

This module is a XML down processor. It maps tag (element) names to functions to process that element and respective contents.

This module processes XML files with an approach similar to OMNIMARK. As XML parser it uses XML::Parser or XML::LibXML module in an independent way. At configure stage, you should choose one of the back-ends.

DateTime::Locale is a Perl module with localization support for DateTime.pm.

SYNOPSIS

use DateTime::Locale;

my $loc = DateTime::Locale->load(en_GB);

print $loc->native_locale_name, "n",
$loc->long_datetime_format, "n";

# but mostly just things like ...

my $dt = DateTime->now( locale => fr );
print "Aujourdhui le mois est " . $dt->month_name, "n":

DateTime::Locale is primarily a factory for the various locale subclasses. It also provides some functions for getting information on available locales.

If you want to know what methods are available for locale objects, then please read the DateTime::Locale::Base documentation.

Binkd is a TCP/IP daemon which transfers files between two Fidonet systems. It supports so-called "Binkley-Style outbound", also supported by most Fidonet software.
It uses its own protocol (called Binkp), but its not a big problem, as binkd (started Nov, 96) now is maybe the most popular fidonet-over-IP technology in the former USSR.
Binkd cannot (and never will) make calls via regular telephone lines, so it should be used not instead of, but along with any other Bink-style Fidonet mailer. Its known that Binkd (at least) runs perfectly together with Ifmail, Brake!, Bink/+, McMail, T-Mail and Xenia mailers.
Binkd comes in ANSI C sources, so it can be built in almost any environment with Berkeley sockets API supported (multitasking is a plus). I know about UNIX (AIX, FreeBSD, NetBSD, Linux, Solaris), OS/2, NT, DOS, and Windows95 ports.
For install just follow these steps:
1. Edit sample binkd.cfg.
2. Run binkd.
Enhancements:
- Dont attempt to kill client manager if its not running (Michail Vidiassov ).
- Fixed bug in multithread version (win32 & os2/watcom).
- New option "temp-inbound" in binkd.cfg - directory for incomplete receiving files (.dt and .hr).
- New options "socks" and "proxy" in binkd.cfg (Dima Afanasiev )
- MD5 authorization (Dima Afanasiev )
- New commandline switch "-m" - disable MD5 authorization.
- prescan did not work on incoming sessions with send-if-pwd
- NT: new commandline parameters "-i" (install as service) and "-u" (uninstall service) (Dima Afanasiev )
- Immediate events (beginning with !) runs immediate after file receiving (Dima Afanasiev )
- Macros *F (file name), *H (host name), *A0..*A9 (remote addresses), *L (listed), *P (protected) in events (Dima Afanasiev )

DateTime::Event::Cron is a DateTime extension for generating recurrence sets from crontab lines and files.

SYNOPSIS

use DateTime::Event::Cron;

# DateTime::Set construction from crontab line
$crontab = */3 15 1-10 3,4,5 */2;
$set = DateTime::Event::Cron->from_cron($crontab);
$iter = $set->iterator(after => DateTime->now);
while (1) {
my $next = $iter->next;
my $now = DateTime->now;
sleep(($next->subtract_datetime_absolute($now))->seconds);
# do stuff...
}

# List of DateTime::Set objects from crontab file
@sets = DateTime::Event::Cron->from_crontab(file => /etc/crontab);
$now = DateTime->now;
print "Now: ", $now->datetime, "n";
foreach (@sets) {
my $next = $_->next($now);
print $next->datetime, "n";
}

# DateTime::Set parameters
$crontab = * * * * *;

$now = DateTime->now;
%set_parms = ( after => $now );
$set = DateTime::Event::Cron->from_cron(cron => $crontab, %set_parms);
$dt = $set->next;
print "Now: ", $now->datetime, " and next: ", $dt->datetime, "n";

# Spans for DateTime::Set
$crontab = * * * * *;
$now = DateTime->now;
$now2 = $now->clone;
$span = DateTime::Span->from_datetimes(
start => $now->add(minutes => 1),
end => $now2->add(hours => 1),
);
%parms = (cron => $crontab, span => $span);
$set = DateTime::Event::Cron->from_cron(%parms);
# ...do things with the DateTime::Set

# Every RTFCT relative to 12am Jan 1st this year
$crontab = 7-10 6,12-15 10-28/2 */3 3,4,5;
$date = DateTime->now->truncate(to => year);
$set = DateTime::Event::Cron->from_cron(cron => $crontab, after => $date);

# Rather than generating DateTime::Set objects, next/prev
# calculations can be made directly:

# Every day at 10am, 2pm, and 6pm. Reference date
# defaults to DateTime->now.
$crontab = 10,14,18 * * * *;
$dtc = DateTime::Event::Cron->new_from_cron(cron => $crontab);
$next_datetime = $dtc->next;
$last_datetime = $dtc->previous;
...

# List of DateTime::Event::Cron objects from
# crontab file
@dtc = DateTime::Event::Cron->new_from_crontab(file => /etc/crontab);

# Full cron lines with user, such as from /etc/crontab
# or files in /etc/cron.d, are supported and auto-detected:
$crontab = * * * * * gump /bin/date;
$dtc = DateTime::Event::Cron->new(cron => $crontab);

# Auto-detection of users is disabled if you explicitly
# enable/disable via the user_mode parameter:
$dtc = DateTime::Event::Cron->new(cron => $crontab, user_mode => 1);
my $user = $dtc->user;
my $command = $dtc->command;

# Unparsed original cron entry
my $original = $dtc->original;

trillbox is a flexible and extendable toolkit for building dynamic Web pages.
Written in Perl and based on Template::Recall, it provides "widgets" (or controls) that you can quickly integrate into your Perl Web application. trillbox widgets are designed to be independent points of control that can be easily plugged into a Web programming system, e.g. a CGI application, template-based, or included as part of an application framework.
Widgets purposely have no direct knowledge of each other in order to offer the greatest flexibility (although they may be designed so that output and input can be piped between widgets).
trillbox adds easy, "pluggable" components to your web application. By way of introduction, we will step through a simple CGI application that uses the Trillbox::DataTable component to output data from a table in a MySql database. We will start simple and get progressively more complex as we go.
Here is the script
#!C:/zangweb/perl/bin/perl.exe
use CGI qw(:standard);
use DBI;
# Load our TR widgets from here
use lib ../../;
use Trillbox::DataTable;
print header;
print start_html;
print "< h2 >Trillbox::DataTable demo< /h2 >";
my $dbh = DBI->connect(
"DBI:mysql:database=test;host=localhost", "root", "", {RaiseError => 1}
);
my $dt = Trillbox::DataTable->new();
$dt->set( table_attrs => border="1" );
$dt->set( colnames => [ ID,Product,Price ] );
# Connect DBI output to DataTable:
$dt->set(
bind_data => $dbh->selectall_arrayref("select * from trillbox_intro")
);
$dbh->disconnect();
# Output the data
print $dt->output();
print end_html;
Notice the statement
use lib ../../;
prior to use Trillbox::DataTable;. This instructs our script that we will find the trillbox components two directories above the location of the script. After this line of code, you can add any component you like simply with
use Trillbox::Component;
You may download and put trillbox in any location that is appropriate. The use lib path statement tells your code where the components may be found. This allows you to run trillbox on servers that may not have the dependent modules installed.
This is a standard CGI script, so we do the usual things like print header, and print start_html. Using DBI, we connect to a MySql server, in this case, one running on our workstation.
Then, we instantiate the Trillbox::DataTable object via its new() method. No parameters need to be passed to new(). You set properties on the object using the set() method. In the following statement, we set the attributes of the produced by $dt so that it has a border.
We use set() again, this time to set the column header names of the table. set() expects one or more name/value pairs. In this case, colnames is the property name, and the anonymous array represents the column header values.
set() is probably the most overworked method of the Trillbox core components. We now use it to set the bind_data property of $dt to the output from the DBI object. You can see that we pass our SQL statement into the $dbh->selectall_arrayref() method, and it returns a reference to an array, which is exactly what bind_data expects. Any array in your code can be "bound" to DataTable by passing a reference to it. (Note that it expects a 2-dimensional array, that is, an array of arrays.)
Whats Newin This Release:
- Added Treeview widget.
- Build nested structures of nodes, like a file system directory tree.

AxY FTP is a Gtk based FTP client. AxY FTP can be build with either Motif or GTK+ 1.0/1.2 for interface.
Lesstif is also supported.

./configure
make
make install (or make install-strip)

Name of the executable is "axyftp".

You may want to run "./configure --help" first to learn about all available
options. One of the most important are:
--with-gui=GUI where GUI is either motif or gtk. By default, configure
script first searches for Motif installation and, if not
found, for GTK.
--with-help=DIR where DIR is a directory you want to have help files
installed into.

Please not that if you are building Motif version, CDE DtWidget library is
needed. Pretty workable clone is supplied with the distribution in case you
dont have one installed. Also, XmAxy library containing Notebook and enhanced
List Motif-based widgets is also supplied. Libraries are not installed by
default. Use "./configure --enable-install-dt --enable-install-xmaxy" to
install them.

Also, you may find various AxY FTP logo icons in XPM format in icons/
subdirectory.

DateTime::Event::Sunrise is a Perl DateTime extension for computing the sunrise/sunset on a given day.

SYNOPSIS

use DateTime;
use DateTime::Event::Sunrise;

my $dt = DateTime->new( year => 2000,
month => 6,
day => 20,
);

my $sunrise = DateTime::Event::Sunrise ->sunrise (
longitude =>-118,
latitude =>33,
altitude => -0.833,
iteration => 1
);

my $sunset = DateTime::Event::Sunrise ->sunset (
longitude =>-118,
latitude =>33,
altitude => -0.833,
iteration => 1
);

my $tmp_rise = $sunrise->next( $dt );

my $dt2 = DateTime->new( year => 2000,
month => 12,
day => 31,
);

# iterator
my $dt_span = DateTime::Span->new( start =>$dt1, end=>$dt2 );
my $set = $sunrise->intersection($dt_span);
my $iter = $set->iterator;
while ( my $dt = $iter->next ) {
print ,$dt->datetime;
}

# is it day or night?
my $day_set = DateTime::SpanSet->from_sets(
start_set => $sunrise, end_set => $sunset );
print $day_set->contains( $dt ) ? day : night;

my $dt = DateTime->new( year => 2000, month => 6, day => 20, time_zone => America/Los_Angeles, );
my $sunrise = DateTime::Event::Sunrise ->new( longitude =>-118 , latitude => 33, altitude => -0.833, iteration => 1
);

my $tmp = $sunrise->sunrise_sunset_span($dt); print "Sunrise is:" , $tmp->start->datetime , "n"; print "Sunset is:" , $tmp->end->datetime;
my $dt1 = $sunrise->sunrise_datetime( $dt ); print "Sunrise is:" , $dt1->datetime , "n"; my $dt2 = $sunrise->sunset_datetime( $dt ); print "Sunset is:" , $dt2->datetime , "n";

DateTime::Calendar::Hebrew is a Perl module with dates in the Hebrew calendar.

SYNOPSIS

use DateTime::Calendar::Hebrew;

$dt = DateTime::Calendar::Hebrew->new( year => 5782,
month => 10,
day => 4 );

DateTime::Calendar::Hebrew is the implementation of the Hebrew calendar. Read on for more details on the Hebrew calendar.