Free entry points 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.

OglExt is a free OpenGL extension library, enabling the easy access of all functionality up to OpenGL version 2.0 as well as API functions of more than 270 OpenGL extensions. OglExt library was initially written for Microsoft Windows but works for Linux and MacOS X as well.
OpenGL developers for the Windows operating system usually know the problem: The official OpenGL library only supports version 1.1 of the OpenGL specification. However, todays graphics hardware supports OpenGL version 2.0 and a lot OpenGL extensions. To access such functionality, you have to determine the entry point for each function you want to use via wglGetProcAddress() or glXGetProcAddressARB(). Even worse, for Microsoft Windows you have to do this for each OpenGL rendering context, because the entry points may differ for different pixel formats.
By using OglExt, you dont have to care about this anymore, because the extension library manages all the above for over 200 OpenGL extensions.
Enhancements:
- This release fixes a minor bug in the parsing of functions that have pointers as return types.
- Additionally, the project compiles on Visual Studio .NET 2005.

Zen explorer desktop entry adds a service menu with the option to send a music file to your Creative zen jukebox.

Ive only tested it with Zen V Plus 2 gig, but it uses libmtp to send the file. Not too exciting, i wrote it in less than a minute.

Net::Google::Calendar::Entry is an entry class for Net::Google::Calendar.

SYNOPSIS

my $event = Net::Google::Calendar::Entry->new();
$event->title(Party!);
$event->content(P-A-R-T-Why? Because we GOTTA!);
$event->location("My Flat, London, England");
$event->status(confirmed);
$event->transparency(opaque);
$event->visibility(private);

my $author = Net::Google::Calendar::Person->new;
$author->name(Foo Bar);
$author->email(foo@bar.com);
$entry->author($author);

Data::ICal::Entry::Todo is a Perl module that represents a to-do entry in an iCalendar file.

SYNOPSIS

my $vtodo = Data::ICal::Entry::Todo->new();
$vtodo->add_properties(
summary => "go to sleep",
status => INCOMPLETE,
# Dat*e*::ICal is not a typo here
dtstart => Date::ICal->new( epoch => time )->ical,
);

$calendar->add_entry($vtodo);

$vtodo->add_entry($alarm);

A Data::ICal::Entry::Todo object represents a single to-do entry in an iCalendar file. (Note that the iCalendar RFC refers to entries as "components".) It is a subclass of Data::ICal::Entry and accepts all of its methods.

PHK is a PHP-oriented package system. PHKs purpose is to package a library or an application, in order to distribute and run it as a single file. As an introduction, you may think of it as a PHP-oriented jar, with a lot of additional features.
Main features:
- No runtime software : as it was said above, there is no runtime software to install before using a PHK archive, as it contains its own runtime code. Any installed PHP (version 5.1.0 or more) is ready to include/execute a PHK archive without any modification.
- Supports libraries, applications, plugins : a PHK archive can contain a library or an application (an application is a library with an entry point). PHK archives can also be used as plugins.
- Unlimited number of subfiles : a PHK archive can contain an unlimited number of subfiles and directories. A subfile can contain up 2 Gbytes of binary data. The total size of a PHK archive is limited to 2Gbytes. Every subfile can be, on a file by file basis, compressed (gzip or bz2), and/or filtered through php_strip_whitespace() (for PHP source).
- Standard locations for package information : PHK provides standard locations for administrative informations like packages name, author, license, copyright, etc. PHK also allows to specify an icon file and an URL. All these inforamtion are displayed in webinfo mode.
- Webinfo mode : in webinfo mode, the PHK archive behaves like a small web site, allowing the user to display every information about the archive, and the content of every subfile. This mode is a standard feature of every PHK archive.
- Mount/umount user scripts : the package author can specify a mount_script. This subfile will be called every time the PHK archive is mounted. In the same manner, an umount_script can be specified.
- Built-in CLI commands : several built-in CLI commands are available. These commands are the equivalent, in CLI mode, of the webinfo mode. They allow to display every information about the PHK archives structure and content.
- Meta-packages : PHK supports meta-packages, allowing a PHK archive to be incorporated as a subfile inside another PHK archive, along with other regular files. This feature is useful for unit tests (see the Zend Framework demonstration packages for an example) or to build meta-libraries (incorporating several librairies, but without mixing them together). These sub-PHK archives can be automatically mounted when the main package is mounted.
- Web path protection : In a PHK archive, the subfiles are protected from incorrect or unauthorized access from the web. The legitimate entry points are explicitely identified, making the package easier to secure. From the web, it is impossible to display or to call a subfile if it is not explicitely enabled by an option. Among other benefits, it allows to suppress the usual empty index.htm files in every directories !
- CRC checksum : A PHK archive includes a CRC checksum mechanism. Depending on the packages options, this checksum can be verified every time the package is mounted, or on users request.
- Digital signatures : A PHK package can be digitally signed (using a digital certificate). This feature allows users to verify that their package comes from a source they trust.

Data::ICal::Entry::FreeBusy is a Perl module that represents blocks of free and busy time in an iCalendar file.

SYNOPSIS

my $vfreebusy = Data::ICal::Entry::FreeBusy->new();
$vfreebusy->add_properties(
organizer => MAILTO:jsmith@host.com,
# Dat*e*::ICal is not a typo here
freebusy => Date::ICal->new( epoch => ... )->ical . / . Date::ICal->new( epoch => ... )->ical,
);

$calendar->add_entry($vfreebusy);

A Data::ICal::Entry::FreeBusy object represents a request for information about free and busy time or a reponse to such a request, in an iCalendar file. (Note that the iCalendar RFC refers to entries as "components".) It is a subclass of Data::ICal::Entry and accepts all of its methods.

METHODS

ical_entry_type

Returns VFREEBUSY, its iCalendar entry name.

optional_unique_properties

According to the iCalendar standard, the following properties may be specified at most one time for a free/busy entry:

contact dtstart dtend duration dtstamp
organizer uid url

optional_repeatable_properties

According to the iCalendar standard, the following properties may be specified any number of times for free/busy entry:

attendee comment freebusy request-status

Data::ICal::Entry::TimeZone is a Perl module to represents a time zone definition in an iCalendar file.

SYNOPSIS

my $vtimezone = Data::ICal::Entry::TimeZone->new();
$vtimezone->add_properties(
tzid => "US-Eastern",
tzurl => "http://zones.stds_r_us.net/tz/US-Eastern"
);

$vtimezone->add_entry($daylight); # daylight/ standard not yet implemented
$vtimezone->add_entry($standard); # :-(

$calendar->add_entry($vtimezone);

A Data::ICal::Entry::TimeZone object represents the declaration of a time zone in an iCalendar file. (Note that the iCalendar RFC refers to entries as "components".) It is a subclass of Data::ICal::Entry and accepts all of its methods.

This module is not yet useful, because every time zone declaration needs to contain at least one STANDARD or DAYLIGHT component, and these have not yet been implemented.