Free fxp.one 1.4 software for linux

FXP.One is a whole new system to FTP and FXP. It is not just another client. This engine does all the hard work with dealing with FTP sites.
Built into that is a very simple but powerful API protocol. The idea is then, if someone wants to do an FTP, or FXP, client they can then make one without the FTP hassles. Currently there already are multiple clients. They all talk to the FXP.One engine, and you can interchance the clients.
That is, use one client to create and queue up some items and start the queue process. At a later time, a different client, from a different location can connect and check on the progress of that queue, change it, add to it and so on.
Main features:
- Full FTP and FXP capabilities.
- SSL/TLS support, auto-sensing and forced.
- SSL/TLS data support, auto-sensing and forced.
- SSCN seceure data FXP support.
- CCSN seceure data FXP support.
- XDUPE aware for faster queue processing.
- Auto resume, or overwrite options
- Resume last (re-queue all resume items last for faster queue processing)
- FXP direction control (if one site is firewalled)
- PRET Pre-transfer support for ring-sites.
- Skip lists for both files and directories
- Pass lists for both files and directories (opposite to skip list)
- Move-first for both files and directories
- Automatic skip of empty files and directories.
- Encodes all file and directory names as to handle any locale.
Enhancements:
- Local SSL transfers would fail without an SSL certificate.
- Local transfers would incorrectly negotiate CCSN.
- Both of those problems have been fixed.
- STOP methods were implemented.
- The FXP.One home is automatically created based on platform.
- Minor autoconf fixes were made.

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.

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.

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

FoxGame is an extension that can be used to enhance user experience with O-game.
Enhance user experience with O-game (now works in every o-game version)
Adds a lot of features to the webgame O-game.
It also integrates Database features inside the game.
O-Game, is a real-time spacial browser game.
bs-BA/hr-HR/cs-SR can be downloaded as a separate version from http://foxgame.mozdev.org/ because there is no especific firefox version for those languages.
Main features:
- Automatic universe selector in login page.
- Reduced galaxy view: Planet column is not rendered and its functinality is moved to Name col., debris header reduced also.
- Extra delete options and spy report options: You can control messages from the top or the bottom.
- Fleet arrival and return time: In fleet destiny selection page you will see the time when you fleet will arrive and come back to your planet.
- Fleet retreat time: In fleet page you will see the time when your fleet will arrive if you order to come back.
- Multilanguage support: es-ES(spanish), en-US(english), de-DE(deutsch), pl-PL(polish), fr-FR(french), nl-NL/nl-BR (dutch), it-IT (italian), bs-BA/sr-CS/hr-HR (bosnian, serbian, croatian), pt-PT/pt-BR(portugese), tr-TR(Turkish), zh-CN/zh-TW (Simplified chinese and traditional chinese), ru-RU (russian), da-DK (danish), si-SL (slovenian) and sv-SE/sv-FI (swedish). If your language is not supported and you want to translate it, mail me.
- Almost all finishing hours: Research and buildings finishing hours, hangars qeue finishing time, you can see date/time in overview if you wish and even in phalanx.
- Highlight ally and private messages: Ally and private messages now have a diferent background to see them easily.
- Highlight big debris fields: Debris fields bigger than you fix min will have different background in galaxy view.
- Autochoose mision type: You can define mission priorities so FoxGame will select the mission according to that.
- Online DBs integration: Send reports to Milos (only ogame.com.es), EspRep and GalaxieTool directly within OGame (solar systems, stats and spy reports supported).
- In mines and power plants info screens (the ones you see when you click in the name) you will see the diferences between your actual level and the rest.
- Autoselect fleet destination: Select coord text anywhere go to fleet send screen and Voila! the destination is already selected. There is no need to take down numbers anymore.
- Private message signatures.

gunzets supports Gunze touch panels under Linux and XFree86. Supported panels are the serial, PS/2, and USB devices.
All devices are supported by means of an XFree86 module, and the USB device via a kernel module as well. Both XFree version 3.3.6 and 4.x are supported, as well as kernel 2.2 and 2.4. The driver is supported by Gunze USA.
Version restrictions:
- Debouncing is only supported for XFree 4.0 (not 3.3.6).
- A bounce event breaks smoothing processing
- Support for multi-screen operation is not supported.
Compiling
In order to successfully load the module you need to have the following facilities compiled in your kernel or loaded as modules:
- usb generic support (usbcore.o)
- a usb host controller driver (usb-ohci.o o usb-uhci.o)
- support for misc devices like the ps2 mouse (misc.o)
- the input mechanism (input.o)
To compile the driver just make. If your 2.4 or 2.2 kernel headers are not available from /usr/src/linux/include then specify KERNELDIR to point to your kernel source directory, either on the make command line or in the environment. For example:
make KERNELDIR=/usr/src/linux-2.4
To load the driver, use insmod:
insmod ./gunzets.o
To use the input mechanism, specify it on the command line:
insmod ./gunzets.o use_input=1
To automatically create the entry point in /dev (needed if you are not using the input mechanism) run the gunzets_load script instead:
./gunzets_load
Instllation
To install the module to the proper places you can run make install. You may also wish to copy gunzets_load from /usr/local/bin to /etc/rc.d/init.d or /etc/init.d and create a proper symbolic link for automatic load at boot.

SeaMonkey projetc is a web-browser, advanced e-mail and newsgroup client, IRC chat client, and HTML editing made simple -- all your Internet needs in one application.

The SeaMonkey project is a community effort to deliver production-quality releases of code derived from the application formerly known as "Mozilla Application Suite".

Whereas the main focus of the Mozilla Foundation is on Mozilla Firefox and Mozilla Thunderbird, our group of dedicated volunteers works to ensure that you can have "everything but the kitchen sink" — and have it stable enough for corporate use.

b. is a Web-based manager for Web bookmarks. Bookmarks are stored in an XML file. Operations on the data are done with Perl scripts.
Main features:
Collaborative bookmarks
- A new and powerful feature is the ability to share bookmarks. These shared bookmarks may be publicly viewed by all, while a certain set of users have the ability to add or change them. These users can also add comments to the shared bookmarks, as in a bulletin-board. The display of the shared bookmarks is highly configurable: one can show extra information associated with a bookmark, such as its popularity, when it was last visited, when it was added, etc. With these new features, b. becomes a collaborative space for sharing discoveries of the Web.
- Old-style b. functionality is not lost however: one can still maintain a set of private bookmarks just as before. Whats new is the option to exchange bookmarks between the private and shared sets.
Accessible from any Web browser
- The main advantage for storing your bookmarks on the Web is to have them accessible from any Web browser. b. produces XHTML 1.0 code, doesnt use any Javascript, and is best viewed with a CSS1-compliant browser such as Netscape 6+/Mozilla, Internet Explorer 5+, and Opera 5+.
Bookmark data stored in XML format
- XML has quickly become an acknowledged standard for the management of data transmitted over the Internet. Its foundation as a markup language like HTML gives it a wide base of users, and its precept of separating data from its display provides XML versatility for the many possible uses of the data.
- Im using a DTD for collaborative bookmarks called XBEL-collab. Its a slight modification of the XBEL DTD for bookmarks >>, to allow for features like comments and hit counts. The original XBEL DTD was created by python.org.
Customizable
- In a themes/ subdirectory, one can determine the look of b. with CSS stylesheets, custom graphics, and HTML templates. There are more customization options with this new release.
Multi-user
- b. supports multi-user environments. Using basic Web server user authentication (i.e. by password-protecting the b./ directory), only certain users can have access to b.. Each user has his/her own bookmarks and optionally can have his/her own theme, welcome message, etc.
Version restrictions:
Must close browser to log off
- This is a limitation of basic HTTP user authentication: once you have access to a directory, you always have access until your browser session has ended.
Modify bookmarks from one machine at a time
- Problems can result if one attempts to modify bookmarks from two different machines at the same time. (Viewing and accessing the data from more than one machine is fine.) Although a backup of the XML file is written every time it is modified, something more secure could be implemented.