Free pre compiled software for linux

Apache Compile HOWTO is a full-featured Apache compilation HOWTO.
The Apache Compile HOWTO is a simple set of instructions and examples for compiling Apache, mod_ssl, mod_perl, mod_dav, mod_auth_ldap, mod_auth_mysql, mod_dynvhost, mod_roaming, mod_jserv, and mod_php (including MySQL, Postgres, pdflib, and IMAP).
Enhancements:
- Added XML and Sablotron support to PHP
- Dropped support for mod_jserv
- Added mod_jk support
- Enhanced support for Tomcat
- Updated software mentioned in the HOWTO
- Minor SGML enhancements

dTemplate 2.5 is known as the most rapid templating system in the known universe (at least at the time of creating this project). This templating system is lightweight and supports the declarative programming style. It is fast, because it compiles the template once and the the compiled code is parsed by a highly optimized C code.

XML::Compile::Schema is a Perl module to compile a schema.

INHERITANCE

XML::Compile::Schema
is a XML::Compile

SYNOPSIS

# preparation
my $parser = XML::LibXML->new;
my $tree = $parser->parse...(...);

my $schema = XML::Compile::Schema->new($tree);

my $schema = XML::Compile::Schema->new($xml_string);
my $read = $schema->compile(READER => mytype);
my $hash = $read->($xml);

my $doc = XML::LibXML::Document->new(1.0, UTF-8);
my $write = $schema->compile(WRITER => mytype);
my $xml = $write->($doc, $hash);
print $xml->toString;

This module collects knowledge about a schema. The most important method is compile() which can create XML file readers and writers based on the schema information and some selected type.

WARNING: The compiler is implemented in XML::Compile::Schema::Translate, which is NOT FINISHED. See that manual page about the specific behavior and its (current) limitations! Please help to find missing pieces and mistakes.

WARNING: the provided schema is not validated! In some cases, compile-time and run-time errors will be reported, but typically only in cases that the parser has no idea what to do with such a mistake. On the other hand, the processed data is validated: the output should follow the specs closely.

Two implementations use the translator, and more can be added later. Both get created with the compile() method.

XML Reader

The XML reader produces a hash from a XML::LibXML::Node tree, or an XML string. The values are checked and will be ignored if the value is not according to the specs.

XML Writer

The writer produces schema compliant XML, based on a hash. To get the data encoding correct, you are required to pass a document in which the XML nodes may get a place later.

Opcode is a Perl module created to disable named opcodes when compiling perl code.

SYNOPSIS

use Opcode;

Perl code is always compiled into an internal format before execution.
Evaluating perl code (e.g. via "eval" or "do file") causes the code to be compiled into an internal format and then, provided there was no error in the compilation, executed. The internal format is based on many distinct opcodes.
By default no opmask is in effect and any code can be compiled.

The Opcode module allow you to define an operator mask to be in effect when perl next compiles any code. Attempting to compile code which contains a masked opcode will cause the compilation to fail with an error. The code will not be executed.

OZONE is a 3D marble game.

OZONE is a free game similar to enigma, esprit or oxyd, but in 3D. You also have to move a marble, matching pairs of "OXYD stones" and dont break your marble.

XML::Compile::Schema::Translate is a Perl module to create an XML data parser.

INHERITANCE

XML::Compile::Schema::Translate
is an Exporter

SYNOPSIS

# for internal use only!

This module converts a schema type definition into a code reference which can be used to interpret a schema. The sole public function in this package is compile_tree(), and is called by XML::Compile::Schema::compile(), which does a lot of set-ups. Please do not try to use this package directly!

The code in this package interprets schemas; it understands, for instance, how complexType definitions work. Then, when the schema syntax is decoded, it will knot the pieces together into one CODE reference which can be used in the main user program.

JWebPresenter project is a bitmap-image based Web presenting system.
It can add a Web extension to your favorite presentation tool, such as PowerPoint, MagicPoint, or Impress.
This is useful in distance learning, meeting, conferencing, and other situations.
It uses bitmap images to avoid compatibility problems. Other features include platform independence and simplicity.
Main features:
- Bitmap image based presenting: Hence we have no compatibility problem related to character corruption, locale, font, ... You can (and you must) use an authoring tool (e.g., PowerPoint, OpenOffice, MagicPoint, etc) to create the slides, then export into images to be presented with JWebPresenter.
- Platform independent: Any system satisfying the requirements should be OK, including Linux PC, Windows PC, PDA Sharp Zaurus SL-C760 (JWebPresenter SS v1.0x).
- Simplicity: I believe simple thing should be done simply. JWebPresenter SS v1.2.1 package (tar.gz) is only 36KB, including source, pre-compiled binarary, document, sample, and a 18KB (uncompressed size) license called GPL!
- Protocol and Image format independent: All protocols and image formats supported by JRE (Java Runtime Enviroment) should be OK.
- Efficience: There is little overhead in JWebPresenter.

Smarty project is a template engine for PHP. Many other template engines for PHP provide basic variable substitution and dynamic block functionality.
Smarty takes a step further to be a "smart" template engine, adding features such as configuration files, template functions, and variable modifiers, and making all of this functionality as easy as possible to use for both programmers and template designers.
Smarty also converts the templates into PHP scripts, eliminating the need to parse the templates on every invocation. This makes Smarty extremely scalable and managable for large application needs.
Main features:
- Caching: Smarty provides fine-grained caching features for caching all or parts of a rendered web page, or leaving parts uncached. Programmers can register template functions as cacheable or non-cachable, group cached pages into logical units for easier management, etc.
- Configuration Files: Smarty can assign variables pulled from configuration files. Template designers can maintain values common to several templates in one location without intervention from the programmer, and config variables can easily be shared between the programming and presentation portions of the application.
- Security: Templates do not contain PHP code. Therefore, a template designer is not unleashed with the full power of PHP, but only the subset of functionality made available to them from the programmer (application code.)
- Easy to Use and Maintain: Web page designers are not dealing with PHP code syntax, but instead an easy-to-use templating syntax not much different than plain HTML. The templates are a very close representation of the final output, dramatically shortening the design cycle.
- Variable Modifiers: The content of assigned variables can easily be adjusted at display-time with modifiers, such as displaying in all upper-case, html-escaped, formatting dates, truncating text blocks, adding spaces between characters, etc. Again, this is accomplished with no intervention from the programmer.
- Template Functions: Many functions are available to the template designer to handle tasks such as generating HTML code segments (dropdowns, tables, pop-ups, etc.), displaying content from other templates in-line, looping over arrays of content, formatting text for e-mail output, cycling though colors, etc.
- Filters: The programmer has complete control of template output and compiled template content with pre-filters, post-filters and output-filters.
- Resources: Templates can be pulled from any number of sources by creating new resource handlers, then using them in the templates.
- Plugins: Almost every aspect of Smarty is controlled through the use of plugins. They are generally as easy as dropping them into the plugin directory and then mentioning them in the template or using them in the application code. Many user-community contributions are also available. (See the plugins section of the forum and wiki.)
- Add-ons: Many user-community contributed Add-ons are available such as Pagination, Form Validation, Drop Down Menus, Calander Date Pickers, etc. These tools help speed up the development cycle, there is no need to re-invent the wheel or debug code that is already stable and ready for deployment. (see the Add-ons section of the forum and wiki.)
- Debugging: Smarty comes with a built-in debugging console so the template designer can see all of the assigned variables and the programmer can investigate template rendering speeds.
- Compiling: Smarty compiles templates into PHP code behind the scenes, eliminating run-time parsing of templates.
- Performance: Smarty performs extremely well, despite its vast feature set. Most of Smartys capabilities lie in plugins that are loaded on-demand. Smarty comes with numerous presentation tools, minimizing your application code and resulting in quicker, less error-prone application development/deployment. Smarty templates get compiled to PHP files internally (once), eliminating costly template file scans and leveraging the speed of PHP op-code accelerators.