Free to 30 software for linux

Nitro provides everything you need to develop professional Web applications using Ruby and Javascript.
Nitro redefines Rapid Application Development by providing a clean, yet efficient API, a layer of domain specific languages implemented on top of Ruby and the most powerful and elegant object relational mapping solution available everywhere.
Nitro is Web 2.0 ready, featuring excellent support for AJAX, XML, Syndication while staying standards compliant.
Enhancements:
- VCR mode, Og QBE, feeds, and fixes were added.

Powernap is a small Python extension for accurate sleeping. Pythons time.sleep() function is fairly inaccurate. It is definitely not accurate enough for music, games, or graphics. powernap can sleep too long or too short, and usually does.
Using Linuxs real-time clock (RTC) allows for more accurate timing. This extension wraps all the messy RTC stuff and provides nap(), which performs the same job as sleep(), but more accurately.
Even more usefully, it provides rnap(), which is a padding nap. That is, if you call rnap(30), it will nap for however many milliseconds are required to make the time since the last nap 30 milliseconds. rtc_on() sets up the real-time clock, and rtc_off() turns it off. It also switches the scheduler to SCHED_FIFO.
Enhancements:
- This is the second public release.
- Most of the timing was moved into the C extension.
- rnap(), the rolling padding nap, is provided.

LibTPT library parser transforms TPT templates into text.

TPT is a template scripting language implemented in C++.

The parser, which integrates with your C++ code through a simple class API, is small and fast, focusing on functionality instead of rich feature sets.

Uses include on-the-fly HTML and source code generation.

Installation:

If you have multiple C++ compilers, it is a good idea to specify which C++ compiler should be used for building LibTPT.

The configure.pl script reads the CXX environment variable or you can use the "--cxx" option to specify where the C++ compiler is.

E.g.

# ./configure.pl --cxx=/usr/local/bin/g++32

or

> CXX=/usr/local/bin/g++32 ./configure

Run configure.pl to for a default configuration (use --help for more options).

For a default build:

# ./configure.pl
# make
# cd test
# ./test.sh
# cd ..
# make install

Java Tools is a lightweight integrated development environment for creating, compiling, and executing Java applications and applets.
Java Tools includes point and click access to the Java files, commands, and documents. It also includes a built-in text editor and user interface for the Java debugger.
It is intended for the new Java user who needs help getting started. Its also for the more experienced Java user who wants easy access to the Java commands and a text editor.
Main features:
- GUI with built-in help and small footprint.
- Point and click access to all files (Java, manifest, HTML, image and sound) and directories (package).
- Point and click access to all commands for compiling (javac), archiving (jar), documenting (javadoc), executing (java), debugging (jdb) and disassembling (javap).
- Point and click access to all documents (Java API Specification, Java Tools and Utilities, Java Features and Java Tutorial).
- Point and click creation of all files (Java, manifest and HTML) and directories (package).
- Point and click installation of distribution archive files (Java document, Java source code, Java Tutorial and Sun Tools).
- Automatic determination of class file dependencies for archiving (jar) and documenting (javadoc) Java files.
- Checking for unused, redundant and missing imports.
- Logging of all commands invoked by GUI.
- Code metrics for Java files.
- Built-in text editor (see Edit for details).
- Built-in user interface for the Java debugger with command-line editing and history.
- Self-installing executable (Java archive file).
- Comprehensive installation and user documentation for Java and Java Tools.

Gatotray project is a colorful tray icon to watch over CPU status including usage, frequency and temperature.
Main features:
- Time scale is non-linear: right-most columns reflect last seconds while lefter columns accumulate older measures, providing an idea of cpu usage evolution for up to 30 minutes in a glimpse. It makes a beautiful smoothing effect too.
- Colors of the usage bars vary with frequency, from green to red.
- Tooltip shows current usage percentage, frequency and temperature numerically.
- Instant temperature is shown graphically, in the form of a nice thermometer :-). Thermometer blinks on high temperature (>=85 C).
- Pops-up a top window with detailed system usage (on click).

GNU Cim is a compiler for the programming language Simula (except unspecified parameters to formal or virtual procedures (see the documentation for how portable code for formal procedures can be written)).

cim project offers a class concept, separate compilation with full type checking, interface to external C routines, an application package for process simulation and a coroutine concept.

Supported Platforms

Cim runs on any GNU or UNIX like operating systems regardless of the machine type. The portability of the GNU Simula Compiler is based on the C programming language. The compiler and the run-time system is written in C, and the compiler produces C code, that is passed to a C compiler for further processing towards machine code.

HTML::GenToc is a Perl module that generate a Table of Contents for HTML documents.

SYNOPSIS

use HTML::GenToc;

# create a new object
my $toc = new HTML::GenToc();

my $toc = new HTML::GenToc(title=>"Table of Contents",
toc=>$my_toc_file,
toc_entry=>{
H1=>1,
H2=>2
},
toc_end=>{
H1=>/H1,
H2=>/H2
}
);

# add further arguments
$toc->args(toc_tag=>"BODY",
toc_tag_replace=>0,
);

# generate anchors for a file
$toc->generate_anchors(infile=>$html_file,
overwrite=>0,
);

# generate a ToC from a file
$toc->generate_toc(infile=>$html_file,
footer=>$footer_file,
header=>$header_file
);

HTML::GenToc generates anchors and a table of contents for HTML documents. Depending on the arguments, it will insert the information it generates, or output to a string, a separate file or STDOUT.

While it defaults to taking H1 and H2 elements as the significant elements to put into the table of contents, any tag can be defined as a significant element. Also, it doesnt matter if the input HTML code is complete, pure HTML, one can input pseudo-html or page-fragments, which makes it suitable for using on templates and HTML meta-languages such as WML.

Also included in the distrubution is hypertoc, a script which uses the module so that one can process files on the command-line in a user-friendly manner.

B::Utils is a helper functions for op tree manipulation.

SYNOPSIS

use B::Utils;


These functions make it easier to manipulate the op tree.

FUNCTIONS

all_starts

all_roots

Returns a hash of all of the starting ops or root ops of optrees, keyed to subroutine name; the optree for main program is simply keyed to __MAIN__.

Note: Certain "dangerous" stashes are not scanned for subroutines: the list of such stashes can be found in @B::Utils::bad_stashes. Feel free to examine and/or modify this to suit your needs. The intention is that a simple program which uses no modules other than B and B::Utils would show no addition symbols.

This does not return the details of ops in anonymous subroutines compiled at compile time. For instance, given

$a = sub { ... };

the subroutine will not appear in the hash. This is just as well, since theyre anonymous... If you want to get at them, use...

anon_subs()

This returns an array of hash references. Each element has the keys "start" and "root". These are the starting and root ops of all of the anonymous subroutines in the program.

$op->oldname

Returns the name of the op, even if it is currently optimized to null. This helps you understand the stucture of the op tree.

$op->kids

Returns an array of all this ops non-null children, in order.

$op->first
$op->last
$op->other

Normally if you call first, last or other on anything which is not an UNOP, BINOP or LOGOP respectivly it will die. This leads to lots of code like:

$op->first if $op->can(first);

B::Utils provides every op with first, last and other methods which will simply return nothing if it isnt relevent.

$op->parent

Returns the parent node in the op tree, if possible. Currently "possible" means "if the tree has already been optimized"; that is, if were during a CHECK block. (and hence, if we have valid next pointers.)

In the future, it may be possible to search for the parent before we have the next pointers in place, but itll take me a while to figure out how to do that.

$op->previous

Like $op->next, but not quite.

walkoptree_simple($op, &callback, [$data])

The B module provides various functions to walk the op tree, but theyre all rather difficult to use, requiring you to inject methods into the B::OP class. This is a very simple op tree walker with more expected semantics.

The &callback is called at each op with the op itself passed in as the first argument and any additional $data as the second.

All the walk functions set $B::Utils::file and $B::Utils::line to the appropriate values of file and line number in the program being examined. Since only COPs contain this information it may be unavailable in the first few callback calls.

walkoptree_filtered($op, &filter, &callback, [$data])

This is much the same as walkoptree_simple, but will only call the callback if the filter returns true. The filter is passed the op in question as a parameter; the opgrep function is fantastic for building your own filters.

walkallops_simple(&callback, [$data])

This combines walkoptree_simple with all_roots and anon_subs to examine every op in the program. $B::Utils::sub is set to the subroutine name if youre in a subroutine, __MAIN__ if youre in the main program and __ANON__ if youre in an anonymous subroutine.

walkallops_filtered(&filter, &callback, [$data])

Same as above, but filtered.