Free predictive text entry software for linux

KeySafe project is a small tool I wrote because I wasn?t very happy with the password keepers I?ve tried.
All of them required way too much work just to choose the correct password, and then to copy it into the relevant login dialogue.
Main features:
- Usage and configuration is split up, meaning that the user interface for finding a given password is very simple.
- Search is implemented in a drop-down text entry, no more scrolling or confusing tree hierarchies to find navigate.

Multiple Time Sheets is a simple tool to help you keep track of how many hours you work and for whom.
It differs from most time-tracking software because its designed to work like paper that magically totals up hours.
Main features:
- Uses text files, requiring no database.
- Supports only one user per app, for simpler code.
- Sends and tracks invoices, and payments thereof.
- Features a rudimentary to-do list that displays your list as an outline.
- Sends you a backup of your data automatically.
- Assume the user prefers free-form data entry in text files rather than typing into forms.
- Uses the htmlMimeMail.php class by Richard Heye (phpguru.org).
- CSV and OPML exports of some data.
- Automatic hyperlinking from MTS to your favorite web-based software.
Enhancements:
- This release added a feature that replaces text patterns with links so that strings like "Bug 10" can link to a bug tracking application.
- CSV export was added for the timesheet along with OPML export for the to-do list.

mudFTP is a protocol used for transfer of text files between a MUD server and a mudFTP client program. The text files can be notes, programs, room descriptions, etc. Once the file is transferred to the client, it is edited locally using the users favorite text editor.

In order to install mudFTP on your server, your server must have a centralized mechanism for editing text entries. In case of most MERC derivatives, this happens via the function string_append which takes a char** and takes over the control over input from the user, reallocating the text string as necessary. In any case, a fair knowledge of the C programming language and your MUD server is required in order to install mudFTP.

Once installed on the server side, mudFTP will listen on another port - typically youd wand this to be 6 higher than the normal port (e.g. if your mud is on port 4444, your mudFTP port would be on port 4450).

You users then use the mudFTP client program to connect. The client program identifies itself to the server with the MUD username/password and then waits for a request.

When a user with mudFTP enabled then edits a text using the text editing mechanism, it notices that there is a mudFTP connection and sends the text there instead of to the normal user screen. The users mudFTP client reads the text, saves it to a temporary file and spawns an editor. The user edits the file, and when satisfied, exits the editor. This causes the mudFTP client to send the text back to the server - which in turn replaces the text the user was editing with the new text from the client.

The server source code is ported to following platforms:

* Diku-like servers:
o Envy 2.2 with ILAB OLC
o Mythran 3.1.6b
o ROM 2.4b6 with Ivans OLC 1.72 (by Jessica Boyd)
o ROT 1.4 (by Dominic J. Eidson)
o Circle 3.0 (by George Greer)
* Non-Diku
o LDMUD (by Markus Peter) - should be portable to any LP [New!]

Ports under development:

If you are interested in porting to a new server platform, please email me. mudFTP should be portable to your server as long as your server has some central mechanism for editing text strings.

The C version of the client code works under the following platforms:

* Linux (libc5 as well as glibc)
* Any UNIX (untested, but the code is fairly compatible)
* Windows 95 and NT (port by Cath Allen)
* Windows 98 (untested)

The Java version of the client will work on any Java-capable platform.
Id very much like someone to port the client to the Macintosh platform

Gnome-blog project is a panel applet that can post to BloggerAPI compatible blogs.

* Clean interface doesnt get in the way of what youre writing
* WYSIWYG styled text support
* Entries can be written gradually over the course of a day, popping gnome blog open and closed as you have thoughts to jot down and then posting at the end of the day
* Operates as a panel object/applet or a standalone application
* Supports many different kinds of blogs
* New Spell checking
* New Drag and drop images into your blog entry (if your blog supports it)

Supported Blogs:
* Blogger.com / Blogspot.com
* Advogato.org
* Movable Type
* New WordPress
* New LiveJournal.com
* Pyblosxom
* Any other blog using bloggerAPI or MetaWeblog

Gtk2::Ex::Carp is a GTK+ friendly die() and warn() functions.

SYNOPSIS

use Gtk2::Ex::Carp;

# these override the standard Perl functions:

warn(i told you not to push that button!);

die(an ignominious death);


# new functions for showing extended error information:

# like warn(), but shows a dialog with extra information
# in an expandable text entry:
worry($SHORT_MESSAGE, $EXTENDED_INFORMATION);

# like worry(), but fatal:
wail($SHORT_MESSAGE, $EXTENDED_INFORMATION);

This module exports four functions, of which two override the standard die() and warn() functions, and two which allow for extended error reporting. When called, these functions display a user-friendly message dialog window.

The die() function in this module actually replaces the core die() function, so any modules youve loaded may die will use former instead of the latter. die() will also print the error message to STDERR and will exit the program (with the appropriate exit code) when the dialog is dismissed.

The warn() function will also print a message to STDERR, but will allow the program to continue running when the dialog is dismissed.

EXTRA FUNCTIONS
The worry() and wail() functions behave just like warn() and die(), respectively, except that they allow you to provide additional information. A second argument, which can contain additional error information, is used to fill a text box inside an expander.

HANDLING GLIB EXCEPTIONS
This module also installs warn() as a Glib exception handler. Any unhandled exceptions will be presented to the user in a warning dialog.

PROGRAM FLOW
Note that all the functions in this module create dialogs and use the run() method, so that the standard Glib main loop is blocked until the user responds to the dialog.

Posy::Plugin::TextToHTML is a Posy plugin to convert plain text files to HTML.

SYNOPSIS

@plugins = qw(Posy::Core
...
Posy::Plugin::TextToHTML
...);

This uses the HTML::TextToHTML module (as used by the txt2html script) to convert the body of an entry from text into HTML. This checks the extension of the entry file, and if it is txt, then it will convert the entry.

This basically replaces the parse_entry method, and calls the parent method for anything other than text.

Text::EtText::EtText2HTML is a Perl module to convert from the simple EtText editable-text format into HTML.

SYNOPSIS

my $t = new Text::EtText::EtText2HTML;
print $t->text2html ($text);
or
my $t = new Text::EtText::EtText2HTML;
print $t->text2html (); # from STDIN

ettext2html will convert a text file in the EtText editable-text format into HTML.