Free cleanup 4.5.2 software for linux

Dasher is a zooming predictive text entry system, designed for situations where keyboard input is impractical (for instance, accessibility or PDAs).

Dasher is usable with highly limited amounts of physical input while still allowing high rates of text entry.

Dasher is Free software released under the GPL. Further documentation may be found in the Doc/ subdirectory.

BitRock Installbuilder allows you to create easy to use multiplatform installers for Linux, Solaris and Windows. BitRock installers are native binaries that can run on Windows 98, ME, 2000, XP, 2003, Solaris and on virtually any Linux distribution.
The generated installers provide native look and feel and desktop integration for Windows, KDE and Gnome and are optimized in size and speed, reducing download, startup and installation time. BitRock Installers are single-file, self-contained native executables with no external dependencies and minimal overhead.
All BitRock installers are truly native code, do not require bundling a Java Runtime Environment and provide an intuitive interface on all platforms, even for users without previous Linux experience. BitRock InstallBuilder includes an easy to learn, easy to use GUI environment thar can be run on Windows and Linux.
Create Windows, Solaris and Linux installers from a single build environment. For advanced users, a friendly XML project format supports source control integration, collaborative development and customizing projects both by hand and using external scripts. A command line interface allows you to automate and integrate the building process.
QuickBuild functionality allows you to update installers in a few seconds, without having to repack the entire application. BitRock InstallBuilder provides convenient built-in actions for commonly required installation functionality such as changing file permissions, substituting text in file, adding environment variables, adding directories to the path, changing the Windows registry, launching external scripts and so on.
BitRock installers can be customized in a variety of ways, both graphically and in functionality, and can be run on GUI, text and unattended modes. An uninstall program is created as part of every installation. BitRock Installers are platform and programming language independent. Internationalization: BitRock installers support 15 different languages.
Main features:
- Multiplatform Support : BitRock installers are native binaries that can run on Windows 98, ME, 2000, XP, 2003, Solaris Sparc and on virtually any Linux distribution. Contact us for legacy Windows 95 support.
- Desktop Integration : BitRock installers provide native look and feel and desktop integration for Windows, KDE and Gnome.
- Optimized : BitRock installers are optimized in size and speed and do not require a self-extraction step, reducing download, startup and installation time.
- No External Dependencies : BitRock installers are single-file, self-contained native executables with no external dependencies and minimal overhead. Unlike competing products, all BitRock installers are truly native code and do not require bundling a Java Runtime Environment.
- Ease of Use : BitRock installers provide an intuitive and easy to use interface on all platforms, even for end users without previous Linux experience.
- Ease of Development : BitRock InstallBuilder includes an easy to learn, easy to use GUI environment. Design, build and test installers with the click of a button.
- Time Saving Functionality : For advanced users, a friendly XML project format supports source control integration, collaborative development and customizing projects both by hand and using external scripts. A command line interface allows you to automate and integrate the building process. QuickBuild functionality allows you to update installers in a few seconds, without having to repack the entire application.
- Built-in actions : BitRock InstallBuilder provides convenient built-in actions for commonly required installation functionality such as autodetecting a Java(tm) Runtime, changing file permissions and ownership, substituting text in a file, adding environment variables, adding directories to the path, creating symbolic links, changing the Windows registry, launching external scripts and so on.
- Crossplatform Build Support : The installer builder tool can run on Windows, Solaris and Linux and generate installers for all target platforms from a single project file. Create Windows, Solaris and Linux installers from a single build environment!
- Customization : BitRock installers can be customized in a variety of ways, both graphically and in functionality.
- Multiple Installation modes : BitRock installers provide : several GUI modes with native look-and-feel, for installation in a variety of desktop environments; a text-based installation mode, for console-based and remote installations; a silent/unattended install mode which can be used for integration in shell scripts for automated deployment.
- Uninstall Functionality : An uninstall program is created as part of every installation, allowing users to easily uninstall the software. As the installer, it can be run in a variety of modes. On Windows, uninstall functionality can also be accessed from the Add/Remove Program entry in the Control Panel.
- Startup Failure Detection : BitRock installers will automatically detect the best installation mode available. Users also have the option to manually select a mode.
- Language and Platform Independent : BitRock installers can install applications written in any language, including: Java, PHP, Perl, Python, C/C++ and .NET/Mono.
- Multiple Language Support : BitRock installers support a variety of installation languages, including English, German, Spanish, Italian, French, Portuguese, Traditional Chinese, Dutch, Polish, Valencian, Catalan, Estonian, Slovenian, Romanian and Welsh. You can specify a default language or let the user decide. Please contact us if you require additional language support.
Version restrictions:
- 30-day trial
Enhancements:
- This release adds new actions to calculate md5 and specify the default user and group for installed files.
- It has improved error notification for external program execution.
- The ability to access standard Windows shell folder locations using installer variables has been added.

PyGEP project is a simple library suitable for academic study of GEP (Gene Expression Programming) in Python 2.5, aiming for ease of use and rapid implementation.
It provides standard multigenic chromosomes; a population class using elitism and fitness scaling for selection; mutation, crossover and transposition operators; and some standard GEP functions and linkers.
PyGEP is intended for research, not commercial application. Those interested in a full GEP system are advised to visit Gepsoft, makers of GeneXproTools.
Enhancements:
- This release incorporates extensive stability testing, code cleanup per cheesecake and pylint, and documentation updates.
- Also, as a minor performance enhancement, gene evaluation lists only expand attributes inside their coding regions.

IceBreaker project is an addictive action-puzzle game involving bouncing penguins.
IceBreaker is an action-puzzle game in which you must capture penguins from an Antarctic iceberg so they can be shipped to Finland, where they are essential to a secret plot for world domination.
To earn the highest Geek Cred, trap them in the smallest space in the shortest time while losing the fewest lives. IceBreaker was inspired by (but isnt an exact clone of) Jezzball by Dima Pavlovsky.
Enhancements:
- little bits of code cleanup
- slightly increase bonus for clearing more than 80 on higher levels to help counteract the fact that having more penguins make that more and more impossible

libxcpc library implements an automatic resource cleanup and exception handling in C. Error handling and cleanup code (at least for code that does error handling) can take quite some space in terms of lines of code to be written. This not only increases the binary size, but makes the code more difficult to read. C++ has native exception handling, and this solves part of the problem, while keeping exposed the resource cleanup one.
The libxcpc offers C++ like exception handling, plus automatic resource cleanup, to be used in software written in C. The libxcpc introduces three abstractions, that are Resource, Container and Exception. The Resource is every object (or action) that needs cleanup. This can be a block of allocated memory, an open file, a mapped memory region, etc... Every allocated Resource is owned by a Container. A Resource can be moved from a Container to another. A Container is a bucket inside which Resource are allocated.
A Container can be the parent of other Containers, by hence introducing a parent/child relationship between Containers. A Container can be reassigned to be child of a new Container. By freeing a Container all the Resources allocated inside the Container will be freed, and all the child Containers will be recursively freed too. Resource Containers greatly simplify the resource cleanup code, by being able to issue a single call to free a Container and having automatically all the Resources contained by it, freed as well.
Resources are added/removed in a LIFO (Last In First Out) way, and the libxcpc library offers APIs to re-arrange the order of the Resources inside their Contexts. An Exception is (like in C++) any kind of abnormal condition that prevent the program to flow in its path. This can be a failed memory allocation, a failure to open a file, a failure to mmap(2) a portion of a file, a failure to write(2) a file, etc... An Exception is described by a unique number (int) and by an associated data (void *). Exceptions are thrown using the XCPC_THROW(ctx, exno, data) statement, or re-thrown using XCPC_RETHROW(ctx).
A nice feature of exception handling, is that it allows you to handle only certain kind of exceptions, and different exceptions in different points of your code tree. Using libxcpc library, you handle exceptions by surrounding the potentially-throwing code with the XCPC_TRY(ctx) statement. The code can then use either the XCPC_CATCH(exno) or the XCPC_CATCH_ANY statements to handle specific or all kind of exceptions that happened in the code bound by the XCPC_TRY(ctx). An Exception block must be terminated by a XCPC_END_TRY statement.
If the current Exception block does not handle the current Exception using the XCPC_CATCH(exno) statement, and does not have a XCPC_CATCH_ANY statement, the libxcpc library backtrack to find a valid handler in the code at higher layers of the call hierarchy. It is important that at least the other Exception block uses a XCPC_CATCH_ANY statement, so that any Exceptions not caught by the code, is handled properly. When an Exception is caught by an handler, all the resources allocated by the code from the beginning of the XCPC_TRY(ctx) block, down to the place where the Exception is thrown, are automatically freed once the handler reaches the XCPC_END_TRY statement.
Enhancements:
- This release adds new system calls wrappers and fixes a few minor bugs.

Raggle is a console RSS aggregator, written in Ruby. Features include customizable keybindings, basic HTML rendering, HTTP proxy support, OPML import/export, themes, support for various versions of RSS, Screen support. browser auto-detection, and more. Raggle has been tested under Linux, FreeBSD, Mac OSX, and OpenBSD, and should work properly under other Unix variants as well.
Enhancements:
- category-based view filtering
- feed search (via Syndic8.com)
- feed editing
- improved console HTML rendering
- key bindings for mark unread, import/export OPML, opening links
- current key bindings window
- documentation updates (updated README, man page, full internal API docs, online help)
- much better character encoding conversions (via iconv)
- fixed terminal resizing
- massive code cleanup
- preliminary i18n support (via gettext-ruby)
- fixed a metric ton of bugs
- ...and probably a bunch more stuff that Im forgetting

async-j is an architecture for building long-running, high-performance network servers in Java. It is based on Javas nio library, but shields the user from nios bugs and complexities.
An object-oriented design is used for extendability and low development and maintenance costs.
Enhancements:
- Code cleanup