Free afe proguard 7 software for linux

ProGuard is a free Java class file shrinker, optimizer, and obfuscator. ProGuard project can detect and remove unused classes, fields, methods, and attributes. It can then optimize bytecode and remove unused instructions.
Finally, it can rename the remaining classes, fields, and methods using short meaningless names. The resulting jars are smaller and harder to reverse-engineer.
More compact jar files also means smaller storage requirements, faster transfer of applications across networks, faster loading, and smaller memory footprints.
ProGuards main advantage compared to other Java obfuscators is probably its compact template-based configuration. A few intuitive command line options or a simple configuration file are usually sufficient. For instance, the following configuration option preserves all applets in a jar:
-keep public class * extends java.applet.Applet
The user manual explains all available options and shows more examples of this powerful configuration style.
ProGuard is fast. It only takes seconds to process programs and libraries of several megabytes. The results section presents actual figures for a number of applications.
ProGuard is a command-line tool with an optional graphical user interface. It also comes with plugins for Ant and for the J2ME Wireless Toolkit.
ProGuard is a Java class file shrinker, optimizer, and obfuscator. The shrinking step detects and removes unused classes, fields, methods, and attributes. The optimization step analyzes and optimizes the bytecode of the methods. The obfuscation step renames the remaining classes, fields, and methods using short meaningless names. The resulting jars are smaller and harder to reverse-engineer.
ProGuard can also be used to list unused fields and methods in an application, and to print out the internal structure of class files.
ProGuard typically reads the input jars (or wars, ears, zips, or directories). It then shrinks, optimizes, and obfuscates them. It then writes the results to one or more output jars (or wars, ears, zips, or directories). The input jars can optionally contain resource files. ProGuard copies all non-class resource files from the input jars to the output jars. Their names and contents remain unchanged.
ProGuard requires the library jars (or wars, ears, zips, or directories) of the input jars to be specified. It can then reconstruct class hierarchies and other class dependencies, which are necessary for proper shrinking, optimization, and obfuscation. The library jars themselves always remain unchanged. You should still put them in the class path of your final application.
In order to determine which code has to be preserved and which code can be discarded or obfuscated, you have to specify one or more entry points to your code. These entry points are typically classes with main methods, applets, midlets, etc.
- In the shrinking step, ProGuard starts from these seeds and recursively determines which classes and class members are used. All other classes and class members are discarded.
- In the optimization step, ProGuard further optimizes the code. Among other optimizations, classes and methods that are not entry points can be made final, and some methods may be inlined.
- In the obfuscation step, ProGuard renames classes and class members that are not entry points. In this entire process, keeping the entry points ensures that they can still be accessed by their original names.
Any classes or class members of your code that are created or invoked dynamically (that is, by name) have to be specified as entry points too. It is generally impossible to determine these cases automatically, but ProGuard will offer some suggestions if keeping some classes or class members appears necessary. For proper results, you should at least be somewhat familiar with the code that you are processing.
ProGuard does handle Class.forName("SomeClass") and SomeClass.class constructs automatically. The referenced classes are preserved in the shrinking phase, and the string arguments are properly replaced in the obfuscation phase. With variable string arguments, it is generally impossible to determine their possible values (they might be read from a configuration file, for instance).
However, as mentioned, ProGuard will note constructs like "(SomeClass)Class.forName(variable).newInstance()". These might be an indication that the class or interface SomeClass and/or its implementations may need to be preserved. You can then adapt your configuration accordingly.
Whats New in 3.9 Stable Release:
- This release fixes a number of bugs.
- Notably, ".class" constructs compiled in Java 6 are now handled correctly.
- The optimization step now avoids a possible division by 0 and correctly processes local variables with indices larger than 255.
- The documentation and examples have been updated.
Whats New in 4.0 Beta Development Release:
- Added preverifier for Java 6 and Java Micro Edition, with new option -dontpreverify.
- Added new option -target to modify java version of processed class files.
- Made -keep options more orthogonal and flexible, with option modifiers allowshrinking, allowoptimization, and allowobfuscation.
- Added support for configuration by means of annotations.
- Improved shrinking of unused annotations.
- Added check on modification times of input and output, to avoid unnecessary processing, with new option -forceprocessing.
- Added new options -flattenpackagehierarchy and -repackageclasses (replacing -defaultpackage) to control obfuscation of packages names.
- Added new options -adaptresourcefilenames and -adaptresourcefilecontents, with file filters, to update resource files corresponding to obfuscated class names.
- Now respecting naming rule for nested class names (EnclosingClass$InnerClass) in obfuscation step, if InnerClasses attributes or EnclosingMethod attributes are being kept.
- Added new inter-procedural optimizations: method inlining and propagation of constant fields, constant arguments, and constant return values.
- Added optimized local variable allocation.
- Added over 250 new peephole optimizations.
- Improved making classes and class members public or protected.
- Now printing notes on suspiciously unkept classes in parameters of specified methods.
- Now printing notes for class names that dont seem to be fully qualified.
- Added support for uppercase filename extensions.
- Rewritten class file I/O code.
- Updated documentation and examples.

amaroKed is a SuperKaramba theme for controling amaroK.

Mouse wheel over it changes the volume.

Frox is a transparent FTP proxy that runs under Linux and BSD. It should also work on other UNIX OSes that use ipfilter.
It supports caching of FTP downloads, either by redirecting through a Squid proxy, or through its own local cache. Downloads may also be transparently scanned for viruses (through an external scanner).
Additionally there is an interface for writing scripts to add features or modify froxs behavior, and examples are included to limit download file size and to transparently direct connections to specific hosts to mirror servers.
The proxy is written with security in mind, and in the default setup runs as a non-root user in a chroot jail.
Enhancements:
- Log IP address in xfer logs when name resolution fails.
- Add ForceHTTP option to force downloads to go via the HTTP proxy even where caching will not be possible
- Close all file descriptors before execing virus scanner. Prevents frox waiting forever for some virus scanners to exit
- Compile time option for frox to alter argv[] so ps gives info as to what each frox process is doing
- Improve SSL logging and docs
- Fix for incorrect parsing of Deny ACLs which was introduced in 0.7.16

Xlayout is a simple utility for controlling X11 windows and pointer from the console or remotely.
It can alter the geometry of a window, the position of the pointer, hide a window or send it to the top, list all windows, and get the current pointer position.
For use in scripts, it has the ability to return a status result ("1" for error, "0" for success). It can also ease windows into location.
Enhancements:
- Beta testing has begun.
- This release includes features to display information on the current screens connected.
- Some of the convenience methods were smoothed out.
- Bugfixes were made for the user input.
- A lot of code tidy ups were done.

LogicParser project is a simple parser for logical expressions.

This small application parses a logical expression and shows his tree representation (in a TreeView), along with its DOT format and PNG graph. It also calculate the result of the proposition based on given values.

Pauker is a generic flashcard program written in Java. Pauker uses a combination of ultra-shortterm, shortterm, and longterm memory.
You can use it to learn all the things you never want to forget, like vocabulary, capitals, important dates, etc.
Pauker uses a combination of ultra-shortterm, shortterm, and longterm memory. You can use it to learn all the things efficiently you never want to forget, like vocabulary, capitals, important dates, etc.
Main features:
- completely free (OpenSource, GPL)
- flash card based,
- learning application,
- written in java
- using the leitner cardfile system,
- and works offline without the need of an internet connection.
Enhancements:
- Pauker works now with accidently unpacked lesson files.
- The French translation was updated.
- Wrong newline characters are shown when an answer was mistyped.
- The chosen repeating method when inserting new cards is now saved between program starts.
- An unobtrusive button for donations was added.
- The internal search engine was updated to Apache Lucene v2.1.
- The internal keyboard focus and default button handling was cleaned up.

GNU font utilities to allow conversion of a scanned type specimen image into an outline (PostScript or Metafont) font. These fonts can be used with Ghostscript or TeX.
Since the fontutils were originally written in the early 1990s, other programs have been developed which do a better job of some parts of this task. Here is a list of the fontutils programs with indications of their current status:
- imgrotate: rotates images 90 degrees, an inefficiently-implemented subset of pnmrotate (from netpbm).
- imageto: extracts individual characters from a large image; still useful.
- fontconvert: some features may still be useful, such as creating a tfm file from a bitmap.
- charspace: allows non-interactive side bearing specification, so possibly still useful. On the other hand, fontforge allows interactive specification, and has a very nice preview window for testing side bearings.
- gsrenderfont: a shell script that converts outline fonts to bitmaps at a given size. This is called from TeX programs under certain circumstances. The version here has long been replaced by the scripts in the TeX distributions.
- limn: does the actual conversion from bitmaps to splines. These days, youre much better off using autotrace or potrace.
- bzrto: conversion from the generic homegrown `bzr (Bezier) format output by limn to PostScript Type 1, PostScript Type 3, or Metafont. Obsolete.
- bpltobzr: translate the binary bzr format into an equivalent text format `bpl (bezier property list), for editing. Fortunately, a full-featured free outline font editor, fontforge, has been written (by George Williams).
- xbfe: bitmap font editor for shapes and metrics; astonishingly, it seems there are still no bitmap editors for any format except BDF, so still useful.