Free toc software for linux

Gaim is a multi-protocol instant messaging client for Linux, BSD, MacOS X, and Windows. It is compatible with AIM (Oscar and TOC protocols), ICQ, MSN Messenger, Yahoo, IRC, Jabber, Gadu-Gadu, and Zephyr networks.
Gaim users can log in to multiple accounts on multiple IM networks simultaneously. This means that you can be chatting with friends on AOL Instant Messenger, talking to a friend on Yahoo Messenger, and sitting in an IRC channel all at the same time.
Gaim supports many features of the various networks, such as file transfer (coming soon), away messages, typing notification, and MSN window closing notification.
It also goes beyond that and provides many unique features.
A few popular features are Buddy Pounces, which give the ability to notify you, send a message, play a sound, or run a program when a specific buddy goes away, signs online, or returns from idle; and plugins, consisting of text replacement, a buddy ticker, extended message notification, iconify on away, and more.
Enhancements:
- Fix system log start times for some protocols
- SILC compiles with newer SILC toolkit versions (Pekka Riikonen)
- Fixed a bug where buddy icon cache files were left in the icon cache directory after they were no longer in use.
- Attempt to detect the file type of a buddy icon when saving.
- Additional Yahoo! boot protection (Peter Lawler)
- A few Yahoo! memory leaks plugged (Peter Lawler)
- Fixed handling of the new Yahoo! profile page. (Joshua Honeycutt, Peter Lawler)
- Fixed localized Yahoo! room lists. Please refer to the Yahoo! section of the Gaim FAQ for details. (Peter Lawler)
- Enabled sending files to ICQ users using ICQ 5.02 and newer (Jonathan Clark)

Net::AIM is a Perl extension for AOL Instant Messenger TOC protocol.

SYNOPSIS

use Net::AIM;

$aim = new Net::AIM;
$conn = $aim->newconn(Screenname => Perl AIM,
Password => yaddayadda);
$aim->start;

This module implements an OO interface to the Aol Instant Messenger TOC protocol.

This version contains not much more than hacked code that merely connects to the aol TOC servers and acts on instant messages.

METHODS

Net::AIM->new()

This is the Net::AIM constructor. No arguments needed.

$aim->debug($debug)

Set whether to print DEBUGGING information to STDERRR. Accepts $debug which should be a boolean value.

$aim->set($key, $val)

This method simply sets $key to $val in an internal hash for variables

$aim->get($key)

This method simply gets the value of $key from the internal hash

$aim->newconn()

This method creates a new AIM::Connection object

$aim->getconn()

This method returns a pointer to the AIM::Connection object

$aim->do_one_loop()

This executes one read off the socket.

$aim->start()

This just starts an infinte loop of $aim->do_one_loop;

$aim->timeout($secs);

This sets or returns the current timeout in seconds for the select loop. Takes 1 optional argument. Fractional timeout values are ok.

$aim->add_buddy($send_bool, $group, @buddies);

This adds @buddies to your buddy list, under the group $group. if $send_bool evaluates to TRUE then the toc_add_buddy command is sent to the server. Otherwise it is not sent out. This function will also save the list internally.

$aim->add_permit($send_bool, $group, @buddies);

This adds @buddies to your permit list, under the group $group. if $send_bool evaluates to TRUE then the toc_add_permit command is sent to the server. Otherwise it is not sent out. This function will also save the list internally.

$aim->add_deny($send_bool, $group, @buddies);

This adds @buddies to your deny list, under the group $group. if $send_bool evaluates to TRUE then the toc_add_deny command is sent to the server. Otherwise it is not sent out. This function will also save the list internally.

$aim->remove_buddy($send_bool, $group, @buddies);

This removes @buddies from your buddy list. $group must be the group they were orginally set with for them to be deleted from the internal $aim memory and prevent them from getting added again incase a set_config method is called.

if $send_bool evaluates to TRUE then the toc_add_deny command is sent to the server. Otherwise it is not sent out. This function will also save the list internally.

$aim->set_idle($idle_time)

This method sets our idle time to $idle_time. If $idle_time is omitted it will be set to 0.

$aim->get_info($screen_name)

Sends an info request to the server for $screen_name. The server should reply with a URL which will contain the info requested about the user.

$aim->set_info($info)

This method sets your info or profile information to $info on the server.

$aim->evil($user, $anon)

Warn $screen_name. $anon: boolean value which will determine whether to warn the user anonymously or normally. Anonymous warnings are less severe.

$aim->send($message)

Send $message to the server. This is used internally by other functions to send commands to the server.

$aim->send(toc_add_buddy perlaim)

$aim->chat_invite($room, $msg, @buddies)

Invite @buddies to $room with the message $msg

$aim->chat_accept($room_id)

This will accept an invitation that was sent to us for $room_id

$aim->chat_leave($room_id)

This method instructs the server to take you out of the room $room_id

$aim->chat_whisper($room_id,$user,$msg)

Whisper $msg to $user in the room $room_id

$aim->chat_send($room_id, $message)

Send $message in chat room $room_id

$aim->chat_join($roomname)

Send a request to enter the room $roomname

$aim->send_im($screen_name, $message)

This method sends $message to $screen_name.

$aim->list_rooms();

This method returns an @array of rooms each consisting of ID:ROOM_NAME. For instance: 235236:Perl AIM Chat12 234323:Perl AIM Chat13 235832:Perl AIM Chat14 125082:Perl AIM Chat15

$aim->get_roomname($id)

This method returns the name of the room with id $id.

$aim->set_roomname($id, $roomname)

This saves $roomname in the $aim object in a %hash keyed on $id.

$aim->del_roomname($id)

Deletes $id and its associate value from our roomname hash in $aim

$aim->encode($str)

This method returns $str encoded as per the TOC specs: escaped special chars ({}[]$) and enclosed in quotes (")

$aim->send_config()

This method instructs the module to send our configurations which are the mode (permit/deny/all) and our buddy list to the server and to set it as our saved config on the server

$aim->send_buddies()

This method instructs the module to send all our current buddies to the AOL server.

$set_config_str($config_str, add_bool)

This parses a config string of the form: g Buddies p permit1 p permit2 d deny1 d deny2 b budd1 b budd2

Key: g - Buddy Group (All Buddies until the next g or the end of config are in this group.) b - A Buddy p - Person on permit list d - Person on deny list m - Permit/Deny Mode. Possible values are 1 - Permit All 2 - Deny All 3 - Permit Some 4 - Deny Some

$aim->normalize($data)

This method normalizes $data by killing all but strict alphnumeric characters. Typically used for screen_names.

XAR application aims to provide an easily extensible archive format.

Important design decisions include an easily extensible XML table of contents for random access to archived files, storing the toc at the beginning of the archive to allow for efficient handling of streamed archives, the ability to handle files of arbitrarily large sizes, the ability to choose independent encodings for individual files in the archive, the ability to store checksums for individual files in both compressed and uncompressed form, and the ability to query the table of contents rich meta-data.

The ultimate goal of the XAR project is to provide an archive format suitable for packaging software created by DarwinPorts. (Note it is a work in progress, so please feel free to make suggestions and report bugs in the xar Bugzilla product.)

Installation:

cd xar/src
./configure
make
sudo make install

naim project is the original ncurses, console-based AIM client, which also supports IRC, ICQ, and Lily CMC.
For AIM and ICQ, it uses the TOC protocol, and includes many commonly-requested features found nowhere else, while still preserving naims classic look and feel.
Main features:
- naim includes unique features like zero-configuration peer to peer encryption, automatic message queueing, and incoming message modification (to correct common spelling mistakes and expand common abbreviations; see /help filter).
- naim also includes powerful dynamic module support, allowing developers to modify all major aspects of naims behavior.
- Third-party plug-ins have been used to extend naims functionality for use in embedded monitoring clients, and for use as host to automatic clients ("bots").
- The naim-modules package (distributed below) includes several example plug-ins, including a telnet server (nsocket), an interactive bot (naimusers), and a simple anti-spam measure (nantispam).
- When combined with GNU Screen, naim is great to use as a chat client as well as an answering machine. Individual users can detach, log out, pack up and go home, then log back in from anywhere on the Internet to resume their naim session.
- naim is maintained by an OPEN, DIRECTED COMMUNITY, and has been in development since October, 1998.

CMSimple is a simple content management system for simple maintainance of small commercial or private sites. It has a simple installation, is easy to modify, and offers an unique combination of features.
CMSimple project uses an HTML-file for storing the entire site, which can be edited in your favorite editor. It has a dynamic TOC and document locator, a WYSIWYG editor (no plugin--functions in IE and Mozilla), a search function, link validation, image handling, and automatic backup. It is easy to set up your own layout; just edit the template and stylesheet.
Main features:
- Easy installation
- The CMS script is less than 50 KB
- Template driven layout using a css script
- The contents of the site is stored in a single HTML-file
- Many languages available (both for the user and for site maintenance)
- Written in PHP - it runs on Linux/Apache servers, or on Win32 with Apache or IIS
- Inbuilt WYSIWYG editor (both on IE and Mozilla) - or an alternative configuration using HTMLArea3.0 editor.
- Uploading of images and files
- Link validation
- Search function
- Print version option
- User downloads from their HTML content file.
- Simple mailform & guestbook included
- Easy setup of multi language sites
- PHP-scripting may be included within the content (named CMSimple Scripting)
- Integration with 3rd party scripts possible (using CMSimple scripting)
- Online editing of system configuration
- wwwaut login available (for Linux system)
- Automatic backup on logout
- Documentation and Support Forum at CMSimple.dk
Requierments:
- CMSimple is written in PHP4. Thus, PHP >= 4.0.4 is required on your server.
- CMSimple runs on a Linux server under Apache, or on Win32 under Apache or IIS. No database is needed as the entire site contents are stored in a single HTML-file.
- For better password protection it is advised to set wwwaut to true, which is done by configuring your PHPsettings. This can only be done on Linux where PHP must be installed as an Apache module (not a CGI).
Enhancements:
- Major code cleanup was done in almost all files.
- The structure of code in PHP, HTML, and CSS was improved.
- The output validates as HTML 4.01 Transitional.
- Page splitting is supported on a user defined level.
- A mailform XSS vulnerability was fixed.
- New OEdit buttons were added.
- A page login was added to make it easier to login in IE7.
- Searching on entities was implemented.
- Several other improvements were made.

dtRdr::GUI::Wx::SearchTree is a Perl module that can display search results as a tree.

SYNOPSIS

Methods

book_root

Create a root for the book.

$tree->book_root($book);

When were displaying multiple books, this will not be the root of the tree?

want_item

$item = $tree->want_item($node);

parent_item

Get or create the tree down to (not including) the given node.

my $parent = $tree->parent_item($node);

append_item

Append a TOC node to the tree.

$tree_item = $tree->append_item($parent_item, $toc);

Event Handlers

show_context_menu

$self->show_context_menu($evt);

item_activated

$tree->item_activated($event);

Posy::Plugin::Toc is a Posy plugin to create a table of contents.

SYNOPSIS

@plugins = qw(Posy::Core Posy::Plugin::Toc));
@actions = qw(header
...
make_page_toc
render_page
...
);
@entry_actions = qw(header
...
parse_entry
make_toc
render_entry
...
);

Creates a table of contents generated from headings.
The table of contents will be generated if the entry (or page) contains the toc_entry_split/toc_page_split or the toc_entry_split_after/toc_page_split_after values, only from headers below the match, OR, if the the toc_entry_at_start/toc_page_at_start value is true, in which case the table of contents will be generated from the whole entry (or page) and placed at the start.

If there are no headers (element $toc_chapter_element), then no table of contents will be generated.

This creates a make_toc entry-action, which will put a table of contents in the entry. This should be placed after parse_entry and before render_entry in the entry_action list. If you are using the Posy::Plugin::ShortBody plugin, this should be placed after short_body in the entry_action list, not before it.
This also creates a make_page_toc action, which will put a table of contents in the whole page body. This should be placed before render_page (so that one can be sure that one has the whole page to process).