Free polar 1.4 software for linux

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

Prasi is a Protocol for Remote Authentication and Shared Information.
Prasi is a single-sign-on system for your Perl or PHP scripts, similar to MS Passport. All your enabled services can save and share user profile data, and need not be one the same physical server. Available in 7 languages.
Prasi was originally written as an in-house tool to power our internal-use web applications. Due to one of the tools now being publically released (Wefis) it was decided to make Prasi an open-source project, despite its similarity to other existing open-source projects.
Prasi can be used on two levels. Firstly, it enables all CGI (Perl or PHP) scripts residing on any server to perform user management without the hassle of user management. One perl procedure call, and the browsing user is identified or challenged. The exact behaviour is easily customisable.
On the second level, Prasi is also able to keep track of user data (for example, profiles) and seamlessly share that profile information with other Prasi-enabled scripts. Using Prasi in this way gives scripts the power of mySQL and other types of databases without needing to manage the data themselves. Its quite nearly magic.
For the end user, one login, one password - all Prasi-enabled scripts instantly know who the user is and customise content accordingly.
Enhancements:
- This release adds minor bugfixes and increased compatibility with "cgi-bin"-type systems.

PHPCoder is a web based front-end to the Turck MMCache encoding functions, which are similar to the Zend Encoder product.

Turck MMCache is a free open source PHP accelerator, optimizer, encoder and dynamic content cache for PHP. It increases performance of PHP scripts by caching them in compiled state, so that the overhead of compiling is almost completely eliminated.

Also it uses some optimizations to speed up execution of PHP scripts. Turck MMCache typically reduces server load and increases the speed of your PHP code by 1-10 times.

PHPCoder enables you to encode your PHP scripts and applications into non reversible byte-code, thus preventing users of your programs from viewing or alterting the source code while having full functionality.

Another excellent use for PHPCoder is to encode your applications PHP configuration files, that way someone viewing your source code does not see your databae login and password information.

In addition to encoding PHP scripts PHPCoder allows you to set restrictions on the encoded scripts, you can lock a script to a particular server IP address, server host name, visitor IP, or even place a time limit on the script so it will expire after x amount of time.

PHP Coder also allows you to specify Text, HTML or PHP code that should be prepended and appended to each file before it is encoded, allowing you to easily and securely implement your own licensing scheme.

To use your encoded scripts your clients simply install the free Turck MMCache or the Turck Loader.

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.

PurePostPro provides an upload post-processor for Pure-FTPd.

PurePostPro is a Perl/MySQL script that enables user uploads to be managed more easily. New uploads are logged in a MySQL database, and duplicate files are tracked using MD5 checksums.

The script has two main functions:

1. It logs all incoming uploads to a two-table database;

2. It calculates an MD5 checksum for each file and stores that in the database too.