Free interactive map software for linux

IO::Interactive is a Perl module with utilities for interactive I/O.

SYNOPSIS

use IO::Interactive qw(is_interactive interactive busy);

if ( is_interactive() ) {
print "Running interactivelyn";
}

# or...

print {interactive} "Running interactivelyn";


$fh = busy {
do_noninteractive_stuff();
}

This module provides three utility subroutines that make it easier to develop interactive applications...

is_interactive()

This subroutine returns true if *ARGV and *STDOUT are connected to the terminal. The test is considerably more sophisticated than:

-t *ARGV && -t *STDOUT

as it takes into account the magic behaviour of *ARGV.

You can also pass is_interactive a writable filehandle, in which case it requires that filehandle be connected to a terminal (instead of *STDOUT). The usual suspect here is *STDERR:

if ( is_interactive(*STDERR) ) {
carp $warning;
}
interactive()

This subroutine returns *STDOUT if is_interactive is true. If is_interactive() is false, interactive returns a filehandle that does not print.

This makes it easy to create applications that print out only when the application is interactive:

print {interactive} "Please enter a value: ";
my $value = ;

You can also pass interactive a writable filehandle, in which case it writes to that filehandle if it is connected to a terminal (instead of writinbg to *STDOUT). Once again, the usual suspect is *STDERR:

print {interactive(*STDERR)} $warning;

busy {...}

This subroutine takes a block as its single argument and executes that block. Whilst the block is executed, *ARGV is temporarily replaced by a closed filehandle. That is, no input from *ARGV is possible in a busy block. Furthermore, any attempts to send input into the busy block through *ARGV is intercepted and a warning message is printed to *STDERR. The busy call returns a filehandle that contains the intercepted input.

A busy block is therefore useful to prevent attempts at input when the program is busy at some non-interactive task.

Interactive BDD Environment project is a shell like utility for working with ROBDDs.

IBEN is a tool used for teaching Reduced Ordered Binary Decision Diagrams.

It allows the student to work with ROBDDs without learning a complex C or C++ interface to an ROBDD package.

One can enter the expressions interactively, and view the result as a graph or ask questions about the ROBDD, such as the number of nodes in the ROBDD.

slakbootIBS (Slackware Interactive Boot Scripts) is an enhanced set of replacement boot scripts for the Slackware Linux distribution.

Slackware Interactive Boot Scripts includes a set of control and dispatch tools for configuring and booting with colorized interactive scripts. The new boot process allows the operator to select or skip start-up components in realtime.

It facilitates debugging of startup problems and allows operators to maintain a common baseline to support several local configurations or multiple servers with a single set of scripts.

SILC Map is an utility which can be used to visualize the topology of a SILC network. This project can create maps which indicate the exact global position of the servers and it can create HTML pages out of the information it gathers from the servers.

It is also possible to create a HTML map page which allows the user to click the servers on the map image to get more detailed information of the server. The links between the routers and servers can also be drawn on the map image.

Wolfenstein: Enemy Territory is a Multiplayer Online First Person Shooter. Wolfenstein: Enemy Territory is a team game; you will win or fall along with your comrades. The only way to complete the objectives that lead to victory is by cooperation, with each player covering their teammates and using their class special abilities in concert with the others.

Featuring multiplayer support for as many as 64 players, Wolfenstein: Enemy Territory challenges gamers to the ultimate test of teamwork and strategy. Each of the five character classes is critical to a teams ultimate victory or defeat on the battlefield. The Covert Operative class allows players to steal uniforms, perform reconnaissance and gain access to enemy positions. While, the Engineer allows the Axis and Allied teams to lay and diffuse mines as well as build battlefield bridges, towers, forward command bases and other improvements in the midst of combat to gain advantages for their team.

Wolfenstein: Enemy Territory further online players the option to slug it out in the intense Team Last-Man-Standing game mode, where squad-mates cooperate to ensure their team has the last surviving man on the battlefield. With new game modes, character classes, weaponry, and added tactical skills, Wolfenstein: Enemy Territory will keep gamers in the trenches for hours.

GIFgraph::Map can generate HTML map text.

SYNOPSIS

use GIFgraph::Map;
$map = new GIFgraph::Map($gr_object);
$map->set(key1 => value1, key2 => value2 ...);
$HTML_map = $map->imagemap($gr_file, @data);

Is a perl5 module to generate HTML map text for following graph objects GIFgraph::pie, GIFgraph::bars, GIFgraph::point and GIFgraph::linespoints. As a result of its work is created HTML code containing IMG and MAP tags.

You simply need to insert this code into the necessary place of your page. In the inserted thus image, its certain parts are the references and at a choice their mouse in a status line of your browser displays the additional information.(See Samples).

TMHarvest provides a tool which harvests topicmaps from structured datasources.
The TMHarvest library is based on TM4J and provides a convenient way to automatically generate topic maps from different data sources. A rules files with embedded templates (written in XML) defines from which data sources topic map constructs should be taken into account, as well how new or existent topics should be associated.
Main features:
- TMHarvest creates topic maps from existing data sources. Currently it supports the following source-types: SQL-Databases, CSV-Files, XPath-Queries. In addition it is possible to integrate custom model-providers, written in Java. See for details.
- The harvesting is driven by a model-file. The model may be processed as often as you like. Since the data sources are queried at processing time, it is possible to build topic paps periodically in order to reflect changing content.
- The model-file has a modular setup. The resulting topic map is populated step by step from distinct templateActions. The static parts of the topic map (the structural parts, for example the topics that define the ontology of the topic map) may be merged from static files and therefore seperated from the actual harvest.
Pros and Cons
The process which creates the topic map is serialized in the model-file. Once the process is defined, it runs as often as you like. This enables the creation of topic maps, that are refreshed periodically in an automated way.
Working with the templates leads to a certain interactive experience. Shaping the model, letting TMHarvest run, revisiting the results, reshape the model... let you converge the final form
The fact that the model-file must be written by hand, excludes many users, which lack the necessary technical affinity. The development of graphical interfaces or wizards would be really helpful.