Free ascending order software for linux

ASCEND is a flexible modelling environment for solving hard engineering and science problems. It offers:
- an object-oriented model description language for describing your system,
- an interactive user interface that allows you to solve your model and explore the effect of changing the model parameters, and
- a scripting environment that allows you to automate your more complex simulation problems.
The project was originally written at Carnegie Mellon University in the 1980s and includes powerful and reliable solver routines that analyse the structure of your model and can solve thousands of simultaneous nonlinear equations in a few seconds on everyday computer hardware. It is under active development and is licensed under the GNU General Public License ensuring that it is free software and will remain free.

As Plone does not offer this functionality yet, PloneFolderOrder is a solution that works in todays Plone sites. Once integrated into Plone, it will become obsolete for newer versions of Plone, but there are enough Plone sites that need this functionality today to justify this temporary solution.
The difference to other solutions that store order information inside content objects themselves, PloneFolderOder stores order information in Plone Folders (Therefore the name PloneFolderOrder). Storing content order in a Plone Folder is preferable, because when the ordering changes, you only have to change a single object, the Plone Folder itself. The only drawback is that content objects have to query their container to know their place in the order.
The order screen of Plone Folders contains the list of the folders content, and the user can order the content.
The standard Plone views, and most importantly the navigation tree, are respecting the order set by users.
It is a full-fledged Plone product, installable and uninstallable using the QuickInstaller Tool.
Enhancements:
- Bug Correction : restarting zope will not delete the method getParentFromFolder

Build Order Anlyzer for the Axis & Allies RTS is a tool for analyzing builds in the Axis & Allies RTS game. Many sites go to great lengths to explain Build Orders, but the Build Order Analyzer is the first tool to actually allow players the ability to define a Build Order and then compare it to other Build Orders over time.

Key Facts to know about the Build Order Analyzer:

Only tool of its kind
Can support multiple types of RTS based games (not just Axis & Allies RTS!)
Built on Java technology & open source software

The Build Order Anlyzer 2.0 for Axis & Allies RTS is a tool for analyzing builds in the Axis & Allies RTS game. Wikipedia has a great defnition for a Build Order. To summarize, a Build Order in an RTS game defines the order in which a player builds their buildings, units, and upgrades. Understanding the timing and affect of various build trees is critical in making the appropriate tactical decisions during the game.

The BOA allows a player to build and analyze multiple Build Orders without playing a game. Lose to a player due to their build? Then plug it into the BOA and figure out a build to counter it! Gamers no longer have to play game, after game, after game to figure out a decent counter to another players Build Order, they can use the BOA to figure it out. The BOA can literally save serious gamers hundreds of hours of game play!

SlackIns is a complete Qt-based Gui with the design goals to provide a complete Pkgtool interface for Users in order to install, remove and upgrade tgz packages for SlackWare Linux OS.

Test::XML::Order is a Perl module to compare the order of XML tags in perl tests.

SYNOPSIS

use Test::XML::Order tests => 3;
is_xml_in_order( , ); # PASS
is_xml_in_order( , ); # FAIL
isnt_xml_in_order( , ); # PASS

This module contains generic XML testing tools. See below for a list of other modules with functions relating to specific XML modules.

FUNCTIONS

is_xml_in_order ( GOT, EXPECTED [, TESTNAME ] )

This function compares GOT and EXPECTED, both of which are strings of XML. The comparison works only on the order of the tags, attributes are ignored.

Returns true or false, depending upon test success.

isnt_xml_in_order( GOT, MUST_NOT_BE [, TESTNAME ] )

This function is similar to is_xml_in_order(), except that it will fail if GOT and MUST_NOT_BE have elements in the same order.

NOTES

Please note the following about Test::XML::Order.

The package does not check that the input is well formed XML. You should use Test::XML or a similar package if you want to make sure the XML is well formed.
Only the order of tags are checked, so

is_xml_in_order(< a a="b"/ >x< b >< /b >, < a/ >< b a="c" >asdf< /b >);

passes as the inputs have the same order: < a/ >< b/ >.

The tree structure is tested so the the test below passes.

isnt_xml_in_order(< a >< b/ >< /a >, < a/ >< b/ >);

Shell::Parser is a simple shell script parser.

SYNOPSIS

use Shell::Parser;

my $parser = new Shell::Parser syntax => bash, handlers => {

};
$parser->parse(...);
$parser->eof;

This module implements a rudimentary shell script parser in Perl. It was primarily written as a backend for Syntax::Highlight::Shell, in order to simplify the creation of the later.

Cobertura is a free Java tool that calculates the percentage of code accessed by tests.Cobertura project can be used to identify which parts of your Java program are lacking test coverage. It is based on jcoverage.
Main features:
- Can be executed from ant or from the command line.
- Instruments Java bytecode after it has been compiled.
- Can generate reports in HTML or XML.
- Shows percent of lines coveraged and branches coveraged for each class, package, and for the overall project.
- Shows the McCabe cyclomatic code complexity of each class, and the average cyclomatic code complexity for each package, and for the overall product.
- Can sort HTML results by class name, percent of lines covered, percent of branches covered, etc. And can sort in ascending or decending order.
Enhancements:
- Much improved branch coverage. Information on whether the true as well as the false of an if statement is collected. Also, information on the branches of a switch statement (including the default) is collected. (Jiri Mares)
- Assume Java source files are saved as UTF-8 instead of the computers default encoding.
- Write all HTML and XML reports in UTF-8 instead of the computers default encoding (Naoki Iwami).
- Fix a bug where the Cobertura ant tasks would not work correctly in Microsoft Windows when Cobertura was installed on a different drive than the drive from which youre running ant (Srivathsan Varadarajan).
- Added a "maxmemory" attribute to the instrument, merge and report ant tasks (Matt Cordes).
- Improve support for Maven and similar environments where control over system properties is difficult such as app servers, IoC containers, IDEs, etc. Setting the datafile location is difficult in these environments. To correct this, a cobertura.properties file located in the classpath is used to properly set the net.sourceforge.cobertura.datafile property. (Joakim Erdfelt)