Free mplayerxp 0.7.1 software for linux

Day planner is a simple time management program. It is designed to help you easily manage your time.

It can manage appointments, birthdays, and more. Day planner makes sure you remember your appointments by popping up a dialog box reminding you about them.

Day planner is free software which means that its free for everyone to use, share, change and copy.

SimpleDoc project is a simple Web-based document management system.
The interface is simple and intuitive, there is a tree structure for management and content editing is done without needing to reload the browser.
No database is required.
Main features:
- By using javascript extensively the interface is simple and intuitive, management is done easier and faster.
- Tree structure management and content editing is done without reloading the browser using XMLHttpRequest object, feel like in desktop applications.
- No database is required, the content is kept on the disk in files/directories using the same structure as you see in Tree View, you can edit the content manually, you are not required to use the admin inerface.
- Generate various types of documentation using one of available templates: Tree Menu, Raw html files etc.

Pop3eye is a pop3 email notifier, previewer and spam deleter. It can be run as a dockapp or as a regular or undecorated window that pops up when checking email.
Pop3eye can notify you of email from specific people, with certain subjects, or with information in any other header line by using regular expressions as filters.
It can display up to 20 partial lines of the email body in a tooltip window. Any number of accounts can be monitored and each can have its own color and font scheme.
Pop3eye 0.6 has undergone heavy reworking of regular expression pattern matching. You can setup expressions to match on any header line and then show or hide the email, or delete emails from the server without downloading them.
A log of deleted emails can be kept. You can set "test-delete" until satisfied with its operation.
A portion of the "From:" and "Subject:" lines are displayed as they are retrieved. Afterward, only those marked "show" will be seen.
Mouse actions affect only the account under the mouse. Right clicking on one account retrieves only for that account. Right clicking during retrieval will abort.
If your pop3 server supports UIDL, already downloaded headers and body text will not be downloaded again unless some emails have been deleted. You can force it to download with "shift-right-click".
Enhancements:
- A memory leak has been fixed.
- Retrieval to a local file and deleting email messages from the server can be done to all accounts simultaneously with Shift-Right-Click.

Tapiir is a simple and flexible audio effects processor, inspired on the classical magnetic tape delay systems used since the early days of electro-acoustic music composition.

Tapiir project provides a graphical user interface consisting of six delay lines, or "taps", which can introduce an almost arbitrarily big or small delay to their inputs and can be feed back to each other.

A wide set of effects can be easily achieved by properly configuring and connecting the delay lines: complex echo patterns, resonances, filtering, etc. Delays, interconnections and gains can all be controlled in real time.

TAPIIR internal processing modules consist of six delay-lines, each with a mixer at its input and a gain control at its output, and a stereo output mixer. Stereo input from an external source, typically a musical instrument, is routed to all input mixers. In addition to this, the output of each delay line is also routed to the input mixers of all delay lines, including itself. Figure 1 shows the diagram of TAPIIRs internals.

This cross-feeding of audio signals throughout the system of delay-lines and mixers, allows the user to create a very large variety of stereo delay effects. Very simple echos or ping-pong effects can be achieved easily, but more complex effects such as early reflection echos, reverbs, complex rhythmic and arrhythmic patterns and even Karplus-Strong like synthesis is also possible. It is important to observe, that these more complex effects are only possible by using sample accurate processing.

This article appears in Proceedings of the COST G-6 Conference on Digital Audio Effects (DAFX-01), Limerick, Ireland, December 6-8, 2001

Sample accuracy

Conventional hardware effect processors are often rather limited in the lenght of there delay-lines. It is unusual to encounter accuracy higher than 1 msec, and even 10 msec is used frequently, and maximum delay-lenght are limited as well.

Obviously, this limitation in hardware effect processors is deliberate, both out of technical concerns or marketing. Most users are not interested in higher accuracy, and the standard user interface of hardware effects processors - buttons or at the most an alpha-dial - would make it a painful job to adjust. Also, one can imagine that lower accuracy means less computational cost, and therefore lower overall cost of the effect processing hardware.

For advanced users however, this limitation can be annoying. Of course, many of the effects obtained with very short delay times, such as reverb or filtering, are usually also implemented in the same hardware, but it can be very interesting to combine all these with longer delay-time effects; it would be necessary to use several processors connected together to do this.

The implementation of TAPIIR, however, is sample accurate. This means that extremely short delay times can be used, 0.023 msec when using a sample-rate of 44100 Hz. In addition to this fine control over delay-lengths, the sample accuracy is also implented for feedback and even cross-feeding between the various delay-lines, This is achieved by the fact that the internal processing core of TAPIIR is written in such a way, that the input and output values of the delay-lines and mixers are passed on 1 at a time, instead of buffer-by-buffer.

Filtering with delays

Obviously, the effects obtained by sample accurate processing of delay-lines go far beyond the simple echo effects. This includes the creation of FIR filters and - using feedback - IIR filters (this has been the inspiration for the name TAPIIR). In these cases, the mixer gains function as filter coefficients. This means that TAPIIR can efficiently be used for filtering, with flexible filter design. In a future version, TAPIIR could contain a pole/zero editor that automatically sets the mixer values to create the corresponding filter.

The maximum delay-length that can be achieved is only limited by the physical RAM memory of the system TAPIIR runs on. To give an example, with 32 MB of free memory, a total delay-length of more than 6 minutes can be used. While this might seem rather useless for normal effect processing, it clearly has musical applications. Several compositions have been written that make use of long delay times. Originally performed with the use of tape-delays, they could take great profit of the use of digital techniques for sound quality. The use of hard disk space with sufficient fast access would take away time limitation even more.

Delay-length control

The graphical user interface of TAPIIR allows the user to take full advantage of the delay-length accuracy, but at the same time it tries to maintain user-friendly and manageable, by offering value-sliders for larger scales as well. Delay-time can be entered in time in seconds in number of samples. Sliders control the digits of the delay-length, with an accuracy of 5 decimals. An additional feature is the use of tempo/signature. In that case, delay-length in not represented in seconds, but in beats, and the sliders control the subdivision of beats according to the signature. Obviously, in many circumstances this representation is a lot more useful, in a musical sense, than time in seconds.

Wombat is a servlet container for Perl. It is not an executable program itself; rather, it is a library that can be used by programs to embed a servlet container. Embedding programs must provide implementations of Connector API classes that adapt Wombat to the surrounding environment. One such connector is Apache::Wombat which embeds a Wombat servlet container within an Apache httpd built with mod_perl.

Currently no developer documentation for Wombat itself is provided beyond the contents of this document and the POD for each Wombat class.

CONTAINER CONFIGURATION

CONTAINER DIRECTORIES

Web application directories are generally located beneath a single application base directory which in turn is usually located beneath the containers home directory. Each Host configured in the container can use the same application base directory (called webapps by default) or provide its own, possibly located outside the containers home directory. As well, each Application configured in the container has the option of locating its webapp directory outside its Hosts application base directory.

A typical directory structure for Wombat embedded within Apache/mod_perl might be:

# containers home dir
/usr/local/apache
# default hostss appbase dir
/usr/local/apache/webapps
# examples apps webapp dir
/usr/local/apache/webapps/examples
# another hosts appbase dir
/home/bcm/maz.org/webapps
# another apps webapp dir
/home/bcm/maz.org/webapps/comics

CONTAINER DEPLOYMENT DESCRIPTOR

The behavior and attributes of the Wombat servlet container are controlled by a container deployment descriptor (usually named server.xml). This file is modeled after the Tomcat 4 equivalent, but it does have slight differences. A full Configuration Guide will be published; until then, the definitions included below are the only documentation:

Elements supported in server.xml (named with XPath paths, example attribute settings included inline):

Server

Represents the entire perl interpreter, into which one or more Services are deployed. Only one Server may be specified.

Server/Service

Represents a collection of one or more Connectors that share a single Engine (and therefore the web applications visible within that Engine). A display name for the Service (name="HTTP Service") may be specified. Many Services may be specified for the single Server.

Server/Service/Connector

Represents an endpoint by which requests are received and responses are returned. Each Connector passes requests on to its associated Container for processing. The name of a class that implements the Wombat::Connector interface MUST be specified (className="Apache::Wombat::Connector"), as well as a scheme (scheme="http" attribute) and any attributes needed by the implementation. A secure flag (secure="1") may also be set to indicated that the request was transported using SSL. Many Connectors may theoretically be specified for a particular Service, but at this time, the Wombat internals need some refactoring before they can support Connectors for protocols other than HTTP.

Server/Service/Engine

Represents the highest level Container associated with a set of Connectors. The Engine discriminates between virtual hosts as necessary and passes the request along to the appropriate Host. A display name for the Engine (name="Apache-Wombat") may be specified, as well as the name of a default host (defaultHost="localhost" attribute) to receive requests that are not mapped to other specifically configured Hosts. Only one Engine may be specified for a particular Service.

Server/Service/Engine/Logger

Unless overridden in a lower level Container, all log messages will be handled by this Logger. The name of a class that implements the Wombat::Logger interface MUST be specified (className="Apache::Wombat::Logger"), as well as any attributes needed by the implementation. A minimum log level (level="DEBUG") may also be specified. If no Logger is specified, logging will be disabled for the Container. Only one Logger may be specified for a particular Container.

Server/Service/Engine/Realm

Unless overridden in a lower level Container, all web applications will be subject to this security Realm. The name of a class that implements the Wombat::Realm interface MUST be specified (className="Wombat::Realm::DBIRealm"), as well as any attributes needed by the implementation. If no Realm is specified, security will be disabled for the Container. Only one Realm may be specified for a particular Container.
Note that security MUST be also enabled in a particular web applications deployment descriptor in order for the Realm to be relevant to that web application. Therefore a Realm may be configured for an entire Container but only in use for a single Application.

Server/Service/Engine/SessionManager

Unless overridden in a lower level Container, all sessions will be managed by this SessionManager. The name of a class that implements the Wombat::SessionManager interface MUST be specified (className="Wombat::SessionManager::StandardSessionManager"), as well as any attributes needed by the implementation. A maximum inactivity interval/idle out time may also be specified (maxInactiveInterval="300"). If no SessionManager element is specified, sessions will be disabled for the Container. Only one SessionManager may be specified for a particular Container.

The type of SessionManager used will depend heavily on the environment provided by the embedding program. For instance, a multiprocess Apache/mod_perl server embedding Wombat will require a SessionManager that caches sessions in shared memory, on disk or in some other location that all processes can access, whereas a multithreaded daemon embedding Wombat might use a simple memory-based SessionManager.

Server/Service/Engine/Valve

Represents a request-processing component that "wraps" around the Servlet that is ultimately responsible for processing the request. The name of a class that implements the Wombat::Valve interface MUST be specified (className="Wombat::Valve::RequestDumperValve"), as well as any attributes needed by the implementation. Many Valves may be specified for a single Container.

Valves are used to add container functionality for specific Containers, much like Filters are used to add application functionality for specific Servlets. An example of a commonly-used Valve might be a one that logs information about each request (an AccessLogValve perhaps).

Server/Service/Engine/Host

Represents a Container associated with a particular virtual host. A Host maps the request URI to a particular web application and passes the request along to the appropriate Application. The name of the host MUST be specified (name="localhost"), as well as the application base directory (appBase="webapps") which can be specified absolutely or relative to the containers home directory. Many Hosts (at least one, corresponding to the Engines default host attribute) may be specified for a single Engine.

Server/Service/Engine/Host/Alias

Represents an alternate name or names for the virtual host. For a Host named maz.org, the Alias *.maz.org might be configured to catch requests for specific hosts and subdomains in the domain. The name of the alias MUST be specified (name="*.maz.org"). Many Aliases may be specified for a particular Host.

Server/Service/Engine/Host/Logger

A Logger configured for a Host overrides any Logger configured at the Engine level.

Server/Service/Engine/Host/Realm

A Realm configured for a Host overrides any Realm configured at the Engine level.

Server/Service/Engine/Host/SessionManager

A SessionManager configured for a Host overrides any SessionManager configured at the Engine level.

Server/Service/Engine/Host/Valve

Any Valves configured for a Host add to (and execute after) any Valves configured at the Engine level.

Server/Service/Engine/Host/Application

Represents a Container associated with a particular web application. An Application inspects the request URI and passes the request along to the appropriate Servlet (as configured in the web applications deployment descriptor). The display name of the application (displayName="Examples Application") and the URI path base for the application (path="/wombat-examples") MUST be specified, as well as the webapp directory (docBase="examples") which can be specified absolutely or relative to the parent Hosts application base directory. Many Applications (at least one, corresponding to the URI path /) may be specified for a single Host.

Server/Service/Engine/Host/Application/Logger

A Logger configured for an Application overrides any Logger configured at a higher level.

Server/Service/Engine/Host/Application/Realm

A Realm configured for an Application overrides any Realm configured at a higher level.

Server/Service/Engine/Host/Application/SessionManager

A SessionManager configured for an Application overrides any SessionManager configured at a higher level.

Server/Service/Engine/Host/Application/Valve

Any Valves configured for an Application add to (and execute after) any Valves configured at a higher level.

Open Mortal is a parody of the once popular coin-up fighting game, Mortal Kombat, for Windows and Linux.
OpenMortal is currently playable, has 16 playable characters, some more in the making. New characters can be added, so be a Open Mortal actor today!
Enhancements:
- Some more backgrounds were included.

libstrophe is a library for XMPP client and component communication. Our goal is to build a library that is portable, usable quickly, reliable, well documented and that implements the XMPP specification.
Main features:
- XMPP compliant
- Platform agnostic
- TLS support (coming soon)
- SASL DIGEST-MD5 and SASL PLAIN authentication
- Legacy jabber authentication
- Resource binding
- Low-level miniDOM access for manipulating stanzas
- Event handers for timed events, stanza names and/or namespaces, stanza ids
- Threadsafe (coming soon)
- High-level stanza object manipulation and handling (coming soon)
- Full documentation (coming soon)
- Customizable logging and allocation facilities
- C++ binding (coming soon)
Enhancements:
- fix a bug in the fallback to jabber auth that prevented login to jabberd 1.4 servers
- Simplify access to the default loggers, and merge the basic_logging and basic examples
- draft C++ api