Free del software for linux

del.icio.us post is a Firefox extension that allows you to posts current page or link to del.icio.us. Adds an entry to the context menu and a button to the toolbar.

Due to some changes in version 0.4, it is advised to first uninstall any previous versions of this extension before proceeding with the installation.

After installing use View -> Toolbars -> Customize... to add the button to the toolbar.

pydelicious library allows you to access the web service of del.icio.us via its API through python.
def getrss(tag = "", popular = 0, url = , user = ""):
get posts from del.icio.us via parsing Rss
tag (opt) sort by tag
popular (opt) look for the popular stuff
user (opt) get the posts by a user, this striks popular
url (opt) get the posts by url
def apiNew(user, passwd):
creates a new _DeliciousApi object
requires username and passwd
class _DeliciousAPI:
def __init__(self, user, passwd):
initialize the api with username and passwd
def tags_get(self):
get the tags
def tags_rename(self, old, new):
rename a tag
def posts_update(self):
when have the posts been updated
def posts_dates(self, tag = ""):
when have the posts been posted
def posts_get(self, tag="", dt="", url=""):
get the posts, filtering may help
def posts_recent(self, tag="", count=""):
what have been the latest posts
def posts_all(self, tag=""):
get me all posts
def posts_add(self, url, description="", extended="", tags="", dt="", replace="no"):
add an post to del.icio.us
url - the url of the page you like to add
description - a description of the page, often the title of the page
extended (opt) - an extended description, could be some kind of comment
tags - tags to sort your posts
dt (opt) - current date in format ...., if no date is given, the current
date will be used
def posts_delete(self, url):
delete a post by url
def bundles_all(self):
def bundles_set(self, bundle, tags):
def bundles_delete(self, bundle):
This are short functions for common api calls.
def add(user, passwd, url, description, tags = "", extended = "", dt = "", replace="no"):
def get(user, passwd, tag="", dt="", count = 0):
def get_all(user, passwd, tag = ""):
def delete(user, passwd, url):
def rename_tag(user, passwd, oldtag, newtag):
def get_tags(user, passwd):
This are short functions for getrss calls.
def get_userposts(user):
def get_tagposts(tag):
def get_urlposts(url):
def get_popular(tag = ""):
Examples:
>>> a = apiNew(user, passwd)
>>> a.posts_add(url="http://my.com/", desciption="my.com", extended="the url is my.moc", tags="my com")
True
>>> len(a.posts_all())
1
>>> get_all(user, passwd)
1
>>>
Enhancements:
- This release is mainly a rewrite.
- It now uses external libraries.

dterm application is a simple terminal emulator, which doesnt actually emulate any particular terminal. Mainly, it is designed for use with xterm and friends, which already do a perfectly good emulation, and therefore dont need any special help; dterm simply provides a means by which keystrokes are forwarded to the serial line, and data forwarded from the serial line appears on the terminal.

Running dterm

dterm is invoked thusly:
dterm [options|device ...]

dterm attempts to read the file ~/.dtermrc for options; if this doesnt exist, it tries /etc/dtermrc. Then it parses the options passed on the command line.

The options read should include a device name, e.g "ttyS0" or "ttyd0" for the first serial port on a Linux or FreeBSD system respectively.

Once started, dterm can be got into command mode using Ctrl/]. Press enter once from command mode to get back into conversational mode. (The command character can be changed with the esc= option, e.g. esc=p to use Ctrl/P instead of Ctrl/].)

Options:

The following options can be used from command mode

300, 1200, 9600 etc: Set speed, default 9600.
5, 6, 7, 8: Set bits per character, default 8.
1, 2: Set number of stop bits, default 1.
e, o, n, m, s: Set parity to even, odd, none, mark or space, default none.
cts, nocts: Enable / disable CTS flow control, default nocts.
xon, noxon: Enable / disable XON/XOFF flow control, default noxon.
modem: Enable / disable modem control (hang up modem on exit, exit if modem hangs up), default nomodem.
bs, nobs: Enable / disable mapping of Delete to Backspace, default nobs.
del, nodel: Enable / disable mapping of Backspace to Delete, default nodel.
maplf, nomaplf: Enable / disable mapping of LF to CR, default nomaplf.
igncr, noigncr: Ignore / output carriage returns, default noigncr.
crlf, nocrlf: Enable / disable sending LF after each CR, default nocrlf.
b: Send a 500 ms break.
dtr, nodtr: Raise / lower DTR, default dtr.
rts, norts: Raise / lower RTS, default rts.
d, r: Toggle DTR / RTS.
esc= : Set command mode character to Ctrl/ (default ])
@ : Read and process configuration from .
! : Execute shell command
show: Display current configuration and modem status.
help, h, ?: Display a summary of commands.
version: Display version, copyright and warranty information.
quit, q: Exit

Examples:

Connect via ttyS1 to a system running at 2400 bps, 7 bits even parity:

dterm ttyS1 2400 7 e

Send a break in a running session:

^]
dterm> b
dterm>

DB_File is a Perl5 access to Berkeley DB version 1.x.

SYNOPSIS

use DB_File;

[$X =] tie %hash, DB_File, [$filename, $flags, $mode, $DB_HASH] ;
[$X =] tie %hash, DB_File, $filename, $flags, $mode, $DB_BTREE ;
[$X =] tie @array, DB_File, $filename, $flags, $mode, $DB_RECNO ;

$status = $X->del($key [, $flags]) ;
$status = $X->put($key, $value [, $flags]) ;
$status = $X->get($key, $value [, $flags]) ;
$status = $X->seq($key, $value, $flags) ;
$status = $X->sync([$flags]) ;
$status = $X->fd ;

# BTREE only
$count = $X->get_dup($key) ;
@list = $X->get_dup($key) ;
%list = $X->get_dup($key, 1) ;
$status = $X->find_dup($key, $value) ;
$status = $X->del_dup($key, $value) ;

# RECNO only
$a = $X->length;
$a = $X->pop ;
$X->push(list);
$a = $X->shift;
$X->unshift(list);
@r = $X->splice(offset, length, elements);

# DBM Filters
$old_filter = $db->filter_store_key ( sub { ... } ) ;
$old_filter = $db->filter_store_value( sub { ... } ) ;
$old_filter = $db->filter_fetch_key ( sub { ... } ) ;
$old_filter = $db->filter_fetch_value( sub { ... } ) ;

untie %hash ;
untie @array ;

DB_File is a module which allows Perl programs to make use of the facilities provided by Berkeley DB version 1.x (if you have a newer version of DB, see "Using DB_File with Berkeley DB version 2 or greater"). It is assumed that you have a copy of the Berkeley DB manual pages at hand when reading this documentation. The interface defined here mirrors the Berkeley DB interface closely.

Berkeley DB is a C library which provides a consistent interface to a number of database formats. DB_File provides an interface to all three of the database types currently supported by Berkeley DB.

Camera Life (FDCL) is a system for cataloging your photo collection. Camera Life project gives users the ability to search your archive by albums that you set up, or by directory structure.
Camera life (FDCL) is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
FDCL is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with Chatterbox; see the file LICENSE. If not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. Or visit http://www.gnu.org/licenses/gpl.html
Main features:
Self Updating
- When you add photos to the photo directory you specified when installing, FDCL will cache, thumnail and make public all such photos (Administration: File Manager). You can allow certain user classes to maintain your site by editing the photo descriptions and delete photos that suck.
Topic view and Folder View
- On the main page, users are presented with the option of viewing photos by topic or folder. In topic view, albums (collections of like photos) are categorized by topic (ex: People, Things, My Vacataions).
- Folder view is hierrical and based on the directory structure of the photos. When viewing a photo, users are given the option to view others photos in the same topic or folder.
Image deletion
- When viewing a photo, you have the option to delete it. When a user deletes an image, FDCL actually flags it as non-public. An admin has to actually erase it (Administration: File Manager). And when you erase it, FDCL just moves it to the erased folder. FDCL will never rm your photos. With this in mind, it is sensible to allow users to delete offensive images and admins to erase them.
Themes
- You can easily change the look of the entire site by choosing a different theme (Administration: Customize: Themes). Official themes can be downlaoded from http://fdcl.sourceforge.net other themes are available at your local supermarket (or not).
Users
- Users can anonyously sign up an account. The admins choose which accounts to give privileges to. All authentication is done by random cookies saved in the DB and passwords are salted and hashed.
Logging
- Some actions are logged to the logs table. This is done via the db_log function. You can view the logs (Administration: Log Viewer) and see the audit trail to modifications to the ssytem. You can then rollback specific action (like renaming a photo) by simply choosing the previous state to go back to.
Enhancements:
- This version adds support for Gallery Remote API, microformats, sitemaps, OpenSearch, and RSS feeds, and supports iPhoto photocasting.
- There are now photo keywords with a del.icio.us-like keyword editor.
- Checkpoints allow you to review and approve changes to the site.
- Your users can now order prints online.
- There are also big changes under the hood and some security enhancements.

Date::Manip is a date manipulation routines.

SYNOPSIS

use Date::Manip;

$version = DateManipVersion;

$date = ParseDate(@args);
$date = ParseDate($string);
$date = ParseDate($string);

@date = UnixDate($date,@format);
$date = UnixDate($date,@format);

$delta = ParseDateDelta(@args);
$delta = ParseDateDelta($string);
$delta = ParseDateDelta($string);

@str = Delta_Format($delta,$dec,@format);
$str = Delta_Format($delta,$dec,@format);

$recur = ParseRecur($string,$base,$date0,$date1,$flags);
@dates = ParseRecur($string,$base,$date0,$date1,$flags);

$flag = Date_Cmp($date1,$date2);

$d = DateCalc($d1,$d2 [,$errref] [,$del]);

$date = Date_SetTime($date,$hr,$min,$sec);
$date = Date_SetTime($date,$time);

$date = Date_SetDateField($date,$field,$val [,$nocheck]);

$date = Date_GetPrev($date,$dow,$today,$hr,$min,$sec);
$date = Date_GetPrev($date,$dow,$today,$time);

$date = Date_GetNext($date,$dow,$today,$hr,$min,$sec);
$date = Date_GetNext($date,$dow,$today,$time);

$name = Date_IsHoliday($date);

$listref = Events_List($date);
$listref = Events_List($date0,$date1);

$date = Date_ConvTZ($date);
$date = Date_ConvTZ($date,$from);
$date = Date_ConvTZ($date,"",$to);
$date = Date_ConvTZ($date,$from,$to);

$flag = Date_IsWorkDay($date [,$flag]);

$date = Date_NextWorkDay($date,$off [,$time]);

$date = Date_PrevWorkDay($date,$off [,$time]);

$date = Date_NearestWorkDay($date [,$tomorrowfirst]);

&Date_Init();
&Date_Init("VAR=VAL","VAR=VAL",...);
@list = Date_Init();
@list = Date_Init("VAR=VAL","VAR=VAL",...);

The above routines all check to make sure that Date_Init is called. If it hasnt been, they will call it automatically. As a result, there is usually no need to call Date_Init explicitely unless you want to change some of the config variables (described below). They also do error checking on the input.

The routines listed below are intended primarily for internal use by other Date::Manip routines. They do little or no error checking, and do not explicitely call Date_Init. Those functions are all done in the main Date::Manip routines above.

Because they are significantly faster than the full Date::Manip routines, they are available for use with a few caveats. Since little or no error checking is done, it is the responsibility of the programmer to ensure that valid data (AND valid dates) are passed to them. Passing invalid data (such as a non-numeric month) or invalid dates (Feb 31) will fail in unpredictable ways (possibly returning erroneous results). Also, since Date_Init is not called by these, it must be called explicitely by the programmer before using these routines.

In the following routines, $y may be entered as either a 2 or 4 digit year (it will be converted to a 4 digit year based on the variable YYtoYYYY described below). Month and day should be numeric in all cases. Most (if not all) of the information below can be gotten from UnixDate which is really the way I intended it to be gotten, but there are reasons to use these (these are significantly faster).

$day = Date_DayOfWeek($m,$d,$y);
$secs = Date_SecsSince1970($m,$d,$y,$h,$mn,$s);
$secs = Date_SecsSince1970GMT($m,$d,$y,$h,$mn,$s);
$days = Date_DaysSince1BC($m,$d,$y);
$day = Date_DayOfYear($m,$d,$y);
($y,$m,$d,$h,$mn,$s) = Date_NthDayOfYear($y,$n);
$days = Date_DaysInYear($y);
$days = Date_DaysInMonth($m,$y);
$wkno = Date_WeekOfYear($m,$d,$y,$first);
$flag = Date_LeapYear($y);
$day = Date_DaySuffix($d);
$tz = Date_TimeZone();