Free transporter 1.4 software for linux

Podracer is a podcast downloader. It takes a file with the URLs to all your podcast rss feeds and goes and gets the mp3s and stores them in a specified location. Podracer is a Bourne Shell script with an internal BitTorrent downloader written in Python.
Main features:
- Catchup feature updates the log without downloading all podcasts
- Run as a cron job to automatically receive podcasts
- Properly fails (with no error message for the sake of cron) if already running
- Download podcast enclosures of any file format
- Support for BitTorrent downloading and seeding of podcasts
- Configurable seed time management - seed torrents for an hour or a day
- Background torrent seeding continues after program ends and stops automatically
- System-wide and user-specific configuration
- User-specific subscription file and podcast download directories
- Commentable subscription file - go ahead and mark it up
- Fully configurable placement of files and directories
- Support for dynamic creation of download directories, i.e. based on date/time
- Appears in podcasters logs as a podcast receiver
- Automatic creation of m3u playlists
- User may request that m3u not be created
- Automatic removal of empty download directories
- Your suggestions...

RPilot project is an interpreter for the IEEE-standard language PILOT.
RPilot is an interpreter for the IEEE-standard programming language PILOT written in portable C.
PILOT is a language that was designed in the 1960s to support computer-aided instruction and is very simple to learn.
RPilot comes with an introduction to the language and several examples.
Enhancements:
- Fix usage of `isblank(), a GNU extension (Thanks to Patrick Eaton)
- Add some #defines to rpilot.h to replace a few hard-coded constants
- RPilot is over 4 years old. Wow.

Polar provides a smooth and simple cursor set created primarily in Inkscape.
Polar Cursor Theme is a smooth and simple cursor set created primarily in Inkscape.
Installation
There are three cursor sets included in this package. The default with the orange busy cursors is called PolarCursorTheme and the blue and green variants have -Blue and -Green added to the end of their theme name. To make sure that all themes are installed (or only the one you want) extract to /.icons/ in your home folder.
Note
KDE users please note that installing the cursors through the control center can cause some cursors to use the default X cursors. To fix this simply extract the theme directly to /.icons/ in your home folder.
Finally a special thanks to all the authors of various cursor themes here on gnome-look.org for ideas.
Enhancements:
- Added Zoom cursors
- Fixes to cursor mappings
- Highlight added to clean up outlines
- Added Blue and Green busy cursors as an option
- Changed move cursor
- Small changes to other cursors

GnomeRSVP project is a rapid serial visual projector.
GnomeRSVP is a "Rapid Serial Visual Projector" similar to products like AceReader.
In this dynamic representation of text, each word is flashed on the screen one at a time in succession.
The reader is less inclined to "oralize" the text, rather the reader interprets whole words as meaningful written symbols.
Automatic re-reading of adjacent previous text is therefore rendered impossible.
This results in much higher reading speeds than are possible with standard techniques.
Main features:
- Gnome compliance
- Font Selection
- Color Selection
- Text, HTML, and PDF file support
- Session Support
- Remembers Last Location and Position
- URL support!
- Variable speed from 120 to 6000 words per minute

RIFE project is a full-stack web application framework with tools and APIs to implement most common web features. Each of its toolkits is usable by itself and together they offer powerful integrated features that boost your productivity.
RIFE ensures that every declaration and definition is handled in one place in the code. This simplifies the developers task by reducing code replication, enforcing consistency, and easing maintenance.
RIFEs design provides the best of request-based and component-based approaches and blends them together in a consistent component object model. The web engine provides a solution that values maintainability without compromising on productivity.
Through a centralized site structure, an application can be split up into easily reusable binary modules that can be seamlessly integrated into other projects.
There are currently two major schools of web application development frameworks: request-based and component-based.
Request-based frameworks are very close to the original CGI specification. They use controllers and actions that directly handle incoming requests. Each request is fundamentally stateless.
With the introduction of server-side sessions, a certain degree of statefulness has been achieved. The different frameworks basically differentiate themselves by the way they map logic to URLs and how data is structured and provided to the developer.
Component-based frameworks abstract the developer away from the internals of the request handling and encapsulate the logic into reusable components, often independent from the web medium.
The state is automatically handled by the framework, based on the data that is present in each component instance. Together with some form of event handling, this development model is very similar to the features offered by desktop GUI toolkits. The different frameworks basically differentiate themselves by the provided component API and how components are combined together.
RIFE combines both by taking control of the entire data and logic flow in a request-based model. Developers remain close to the architecture of CGI applications and have full control over URLs, forms, parameters, cookies and pathinfos.
However, instead of mapping actions and controllers directly to the request, RIFE provides a component object model that behaves identically in many different situations such as individual pages, intercepted requests, portal-like page fragments and integratable widgets.
Components can be wired together and be packaged as groups that are components in their own right. They can be distributed separately and be seamlessly integrated into any other RIFE project. This provides the same form of reusability as component-based frameworks, but with the raw control of the request-based approach.
Enhancements:
- Transparent meta data merging has been implemented, which is a creative solution to keeping POJOs pure and still make it possible to declare dynamic meta data in plain Java.
- Other highlights of this release are: new (X)HTML template tag syntaxes, experimental Ajax support with DWR integration, embedded element priorities, strict pathinfo mapping, deprecated CmfProperty and CmfValidation, flowlink-specific datalinks, mail queue support for authentication and SSL, support for setting reflexive outputs and globalvars across submissions, and several bugfixes.