Free work from home data entry software for linux

Zen explorer desktop entry adds a service menu with the option to send a music file to your Creative zen jukebox.

Ive only tested it with Zen V Plus 2 gig, but it uses libmtp to send the file. Not too exciting, i wrote it in less than a minute.

Amarok Music Diary creates a SQLite3 Database with every song played a day. It is possible to add a custom lyric to every database entry html-File export is provided. An example: http://www.sbox.tugraz.at/home/s/stifi/stifi_blog/

Usage:

The database is stored in ~/.kde/share/apps/amarok/scripts-data/amarok-diary.db
To add lyrics, use to Context Menu Entry
For viewing it, use sqlitebrowser http://sqlitebrowser.sourceforge.net
(To due a change in the sqlite data format you may need the CVS Version of the sqlitebrowser)

To export the database use the context menu entry. Per default only songs with the public flag set are exported. This option can be changed in the configuration file.

Data::ICal::Entry::Event is a Perl module that represents an event in an iCalendar file.

SYNOPSIS

my $vevent = Data::ICal::Entry::Event->new();
$vevent->add_properties(
summary => "my party",
description => "Ill cry if I want to",
# Dat*e*::ICal is not a typo here
dtstart => Date::ICal->new( epoch => time )->ical,
);

$calendar->add_entry($vevent);

$vevent->add_entry($alarm);

A Data::ICal::Entry::Event object represents a single event in an iCalendar file. (Note that the iCalendar RFC refers to entries as "components".) It is a subclass of Data::ICal::Entry and accepts all of its methods.

PyMusicD is yet another jukebox daemon written in python. It was born out of my frustration with the current mp3 jukeboxes, mostly the lack of features that I want. Ive also been playing with python quite a lot lately, and this is my first attempt at a large project in python.
The player is being written to satisfy my own requirements for a car mp3 player, although theres no reason you couldnt use this for a home mp3 player, or work mp3 player.
It assumes that your network users are (mostly) benign, and doesnt take a lot of precautions against malicious users who want to screw with your mp3s. Take appropriate measures to only allow trusted users to play with it, at least until I secure it a bit better.
Its primary purpose is to run in the background, and play mp3s whenever they are in the playlist.
Usage
Unpack this to its own directory. Edit the pymusicd.conf file to your liking. Run python PyMusicD, then run python pymusic to play around with it. The client operates very similarly to most shells, and includes tab completion for commands (but not arguments... yet.)
If you wish to install this to the system, you may do so by running python setup.py install. This will install the server binary in the default place for your platform (according to distutils.) You may then edit the config file (/etc/pymusicd.conf by default) and run the server by running PyMusicD. The cli client will be named pymusic.
This software is currently in development. It is not ready for end users yet. You should have familiarity with scripting in python before you set about to use this software. That being said, if you find bugs that arent listed in TODO, and/or have problems with the software that arent listed in TODO, email me (zwhite@darkstar.frop.org) and Ill see what I can do to help you. Code patches/suggestions are always welcome.
This is known to work on my Slackware 9.0 machine using the Python 2.2.2 package that came with it. I have also tested it on my Mac OSX 10.2.8 machine with Python 2.2. I have no reason to believe that it wont work on any machine with a Python 2.x interpreter and
either mpg123 or mpg321. Your mileage may vary. If it doesnt work on your platform, please let me know. My goal is to have this work on any platform that python runs on.
Enhancements:
- Fixed a bug when adding an entire directory with %2A instead of *
- Added a debug command to get server state, currently only playstatus is reported, will add more as needed.
- Changed the way the stop command works to eliminate a bug.
- Check to make sure a file exists before we add it to the playlist.
- We no longer start playing music as soon as the playlist has entries.
- Instead, we wait for a play command to be issued.
- Added config file support. Defaults to /etc/pymusicd.conf or ./pymusicd.conf
- Added a setup.py and setup.cfg file. Now users can install PyMusicD using the standard "python setup.py install" method that other scripts and modules use.

Data::ICal::Entry::Journal is a Perl module that represents a journal entry in an iCalendar file.

SYNOPSIS

my $vjournal = Data::ICal::Entry::Journal->new();
$vjournal->add_properties(
summary => "Minutes of my party",
description => "I cried because I wanted to.",
# Dat*e*::ICal is not a typo here
dtstart => Date::ICal->new( epoch => time )->ical,
);

$calendar->add_entry($vjournal);

A Data::ICal::Entry::Journal object represents a single journal entry in an iCalendar file. (Note that the iCalendar RFC refers to entries as "components".) It is a subclass of Data::ICal::Entry and accepts all of its methods.

Data::ICal::Entry::TimeZone is a Perl module to represents a time zone definition in an iCalendar file.

SYNOPSIS

my $vtimezone = Data::ICal::Entry::TimeZone->new();
$vtimezone->add_properties(
tzid => "US-Eastern",
tzurl => "http://zones.stds_r_us.net/tz/US-Eastern"
);

$vtimezone->add_entry($daylight); # daylight/ standard not yet implemented
$vtimezone->add_entry($standard); # :-(

$calendar->add_entry($vtimezone);

A Data::ICal::Entry::TimeZone object represents the declaration of a time zone in an iCalendar file. (Note that the iCalendar RFC refers to entries as "components".) It is a subclass of Data::ICal::Entry and accepts all of its methods.

This module is not yet useful, because every time zone declaration needs to contain at least one STANDARD or DAYLIGHT component, and these have not yet been implemented.

Non-Networked File System provides a consistent file system over several non networked UNIX computers (or slow networked). For example on your computer at home and at work using only a floppy disk for the synchronisation.
Main features:
- You are sure to work on the latest version of files.
- You dont need to remember which files are modified on an host and must be transfered on others.
- You dont need to made backup, because if a computer crash the file system is still on the other computers working with NNFS.
- The NNFS medium is choosen by a user shell script, it could be: floppy disk, usb key, serial connection, ...
- Minimal NNFS medium bandwidth to make the updates.
- EASY TO USE: Running ``nnfs command before and after your work.
- Numbered backup of files modified/deleted on NNFS.
- If you modify the same file on several hosts NNFS solves the update conflict.
- The program has been hugely tested.
Enhancements:
- This release fixes the case where the user modifies a file mode while NNFS is running and NNFS is configured in order that a file mode change does not imply file synchronization.