Free timetrex time software for linux

TimeTrex project is a complete Web-based payroll and time management suite that offers employee scheduling, attendance (time clock), job costing, invoicing/accounts receivable, and payroll in a tightly integrated package.
With the ability to interface with hardware such as iButtons, barcode readers, and cell phones, employees are able to efficiently track their time at the office or on the road.
Main features:
- TimeTrex helps organizations handle their payroll and time management needs in a more efficient and cost effective manner.
- TimeTrex helps organizations concentrate on their core business goals - the ones that generate revenue.
- TimeTrex benefits are well suited to any business, small or large, with one or more locations.
- TimeTrex allows secure and easy access to its web-based interface from anywhere in the world.
Whats New in 2.0.3 Stable Release:
- This release contains several minor bugfixes, including fixes to the installer requirements and to the employee contact information page that caused branch/department settings to reset themselves.
Whats New in 2.1.0 RC1 Development Release:
- This release contains several major new features such as a greatly improved permission system, more advanced premium policies with additional pay formulas, more advanced meal policies, better scheduling, multi-level timesheet verifications and improved reporting. This is the first release with a fully automated installer for both Windows and Linux.

wtime is a command line utility providing a way to track time spent on arbitrary tasks. The program serves as a front-end for plain text files that hold time data.

wtime provides a way to start/stop counting, display elapsed time, and display time spent in the selected time interval (defined by start and end date). The aim is to keep the program as simple as possible.

Time::Progress Perl module contains elapsed and estimated finish time reporting.

SYNOPSIS

# autoflush to get r working
$| = 1;
# get new `timer
my $p = new Time::Progress;

# restart and report progress
$p->restart;
sleep 5; # or do some work here
print $p->report( "done %p elapsed: %L (%l sec), ETA %E (%e sec)n", 50 );

# set min and max values
$p->attr( min => -2, max => -20 );
# restart `timer
$p->restart;
my $c;
for( $c = -2; $c >= -20; $c-- )
{
# print progress bar and percentage done
print $p->report( "eta: %E min, %40b %pr", $c );
sleep 1; # work...
}
# stop timer
$p->stop;

# report times
print $p->elapsed_str;

Time::Skew is a Perl module that computes local clock skew with respect to a remote clock.

SYNOPISI

use Time::Skew

# Init Convex Hull and timing data
my $hull=[];
my $result={};

# Iterate data point introduction
Time::Skew::convexhull($result,$datapoint,$hull);

This module supports the computation of the skew between two clocks: the (relative) skew is the speed with which two clocks diverge. For instance, if yesterday two clocks, at the same time, showed respectively 10:00 and 10:05, while today when the former shows 10:00 the latter shows 10:04, we say that their relative skew is 1 minute/24 hours, roughly 7E-4.

The module contains one single subroutine, which accepts as input a pair of timestamps, associated to a message from host A to host B: the timestamps correspond to the time when the message was sent, and to the time when message is received. Each timestamp reflects the value of the local clock where the operation takes place: the clock of host A for the send, the clock of B for the receive.

Please note that the module does _not_ contain any message exchange facility, but only the mathematics needed to perform the skew approximation, once timestamps are known.

The subroutine takes as argument:

a reference to a hash where values related to the timing of the network path from A to B;
a 2-elems array (a data point in the sequel) containing the timestamp of the receive event, and the differece between the send timestamp and the receive timestamp for one message;
a stack containing some data points, those that form the convex hull.

The usage is very simple, and is illustrated by the following example:

#!/usr/bin/perl -w
use strict;
use Time::Skew;

# Initialize data
my $hull=[];
my $result={};
while ( 1 ) {
# Exchange message and acquire a new data point
my $datapoint = acquire();
# Call the convexhull subroutine
Time::Skew::convexhull($result,$datapoint,$hull);
# After first message some results are still undefined
( defined $result->{skewjitter} ) || next;
# here you can use the results

};
}

The data returned in the "result" hash is the following:

result->{skew} the clock skew;
result->{skewjitter} the variance of the skew estimate, used to estimate convergence;
result->{jitter} difference between the current delay and the previous delay;
result->{delay} the communication delay, decremented by a constant (yet unknown) value, used to compute communication jitter;
result->{elems} the number of data points in the convex hull;
result->{select} the index of the data point in the convex hull used to compute the skew;
result->{itimestamp} the timestamp, first element in the data point just passed to the subroutine;
result->{delta} the timestamp difference, second element in the data point just passed to the subroutine;

The data returned in the "hull" stack is a series of data points, selected from those passed to successive calls of the subroutine. The number of data points in the "hull" stack usually does not exceed 20 units.

The algorithm is very fast: each call consists in scanning at most all data points in the "hull" stack, performing simple arithmetic operations for each element.

The algorithm must be fed with a sequence of data points before returning significant results. The accuracy of the estimate keeps growing while new data points are passed to the subroutine. A rough rule of thumb to evaluate estimate accuracy is to observe the skew jitter, and assume it corresponds to the skew estimate accuracy. Paths with quite regular communication delay (small jitter) converge faster.

Simple Timetracker provides an application for keeping a record of time vs tasks.

Timetracker is a Java application for recording time spent on projects and activities.

Time::Beat is a Perl module to convert between standard time and Swatch ".beat" time.

Time::Beat is a module to convert normal time to and from .beats, of which there are a thousand in a day. It can change normal time in time() format to .beats, and .beats into either 24-hour or 12-hour normal time.

SYNOPSIS

use Time::Beat qw(beat time24 time12);

my $time_in_beats = beats($time);

my $beats_in_24hr_time = time24($beat);

my $beats_in_12hr_time = time12($beat);

METHODS

There are three methods in Time::Beat.

beats($time)

beats will give you the current time in .beats if you do not specify a time string. If you specify a string in time() format it will return that particular time in .beats. The basic algorithm for doing this is to take the time in GMT+1 hour, convert it into seconds, and divide by 86.4.

time24($beat)

time24 takes a 3-digit beat time and outputs a 24-hour time along the lines of "12:34:56". The hours will have leading noughts.

time12($beat)

time12 takes a 3-digit beat time and outputs a 12-hour time along the lines of "12:34:56 am" or "12:34:56 pm". Hours do not have leading noughts.