Free state cyclones software for linux

StateML is a State Machine Markup Language, with GraphViz and template-driven code generation.

SYNOPSIS

## See the stml command for command line use (recommended)

## Heres what a .stml file might look like:

< machine
id="main"
xmlns="http://slaysys.com/StateML/1.0"
xmlns:C="http://your.com/path/to/ns/for/C/code"
xmlns:Perl="http://your.com/path/to/ns/for/perl/code"
xmlns:Java="http://your.com/path/to/ns/for/Java/code"
...
>
< event id="init">
< C:api>void init_event_handler()< /C:api>
< /event>
< state id="#ALL" graphviz:style="dashed">
< arc event_id="init" goto="running">
< C:handler>init_device()< /C:handler>
< /arc>
< /state>
< state id="running"/>
< /machine>

use StateML;

my $machine = StateML->parse( $source ); ## filename, GLOB, etc.

StateML->parse( $source, $machine ); ## Add to existing machine

... process $machine as needed, see stml source for ideas...

WARNING: Alpha code. I use it in production, but you may want to limit your use to development only.

StateML is an XML dialect and a tool (stml) that reads this dialect (by default from files with a ".stml" extension) and converts it to source code using source code to a data structure.

It can then emit the data structure as a graphviz-generated image or graph specification or you may take the data structure and do what you want with it (bin/stml can pass it to template toolkit, for instance).
parse

my $m = StateML->parse( $StateML_string ) ;
my $m = StateML->parse( *F ) ;

UML::State is an object oriented module which draws simple state diagrams.

SYNOPSIS

use UML::State;

my $diagram = UML::State->new(
$node_array,
$start_list,
$accept_list,
$edges
);

# You may change these defaults (doing so may even work):
$UML::State::ROW_SPACING = 75; # all numbers are in pixels
$UML::State::LEFT_MARGIN = 20;
$UML::State::WIDTH = 800;
$UML::State::HEIGHT = 800;

print $diagram->draw();

ABSTRACT

Are you tired of pointing and clicking to make simple diagrams? Do your wrists hurt thinking about making the pretty UML your boss likes so well? Consider using UML::State and UML::Sequence to make your life easier.

UML::State together with drawstate.pl allows you to easily generate state diagrams. You enter them in something like a cross between ASCII art and school room algebra. They come out looking like something from a drawing program like Visio. See drawstate.pl in the distribution for details about the input format and the samples directory for some examples of input and output.

You will probably use this class by running drawstate.pl or drawstatexml.pl which are included in the distribution. But you can use this package directly to gain control over the appearance of your pictures.

The two methods you need are new and draw (see below). If you want, you may change the dimensions by setting the package global variables as shown in the SYNOPSIS. Obviously, no error checking is done, so be careful to use reasonable values (positive numbers are good). All numbers are in pixels (sorry by Beziers in SVG seem to require pixels). I have not tried changing the numbers, so I dont have any idea if doing so makes reasonable changes to the output.

multistat is a generic program to display the up/down status of all kinds of things (some examples: VPN, particular machines, whether filesystems are mounted).

You will need to edit the multistat.py file to configure the things whose status you want to check.

Status for each "property" (i.e., VPN, computer, filesystem mount) is either red or green.

For each property, you enter values into several arrays, as defined below

Taken from multistat.py:

# commands that set properties to the green state
green_cmds = []

# commands that set properties to the red state
red_cmds = []

# commands whose output can be used to determine whether the state is green or red
check_colour_cmds = []

# strings that, if present in check_colour_cmds, mean that we are in the green state
is_green = []

# display this when in the green state
green_display_strings = []

# display this when in the red state
red_display_strings = []

So what happens is:

For each property:

1. In the green state the green_display_strings value for the property is displayed in green.

2. In the red state the red_display_strings value for the property is displayed in red.

3. To determine whether the property is in the gren or red state, the command in the check_colour_cmds array is run, and if the string in the is_green array is found in the output, then the property is in the green state. Otherwise, it is in the red state.

4. If green_cmds and red_cmds are not null (they MUST be defined, but they MAY be empty strings), then clicking the displayed string for the property on the widget will cause the relevant command to be executed to cause the property to change state. In other words, you can force a property to toggle between green and red by clicking the property on the widget. So, for example, you can mount/umount filesystems with a click. For some properties it makes no sense to provide a toggle (for example, if you are simply monitoring whether a particular computer is on the network): for such properties, define red_cmds and green_cmds to be empty strings.

This may not make much sense (sorry!) but if you read it again with the multistat.py script open in front of you, you should be able to see what I mean.

You can change the actual displayed colours easily (see screenshot 2 for an example where "red" has been redefined).

By default, properties are scanned and updated once per miute.

Tclkeymon is a daemon for Toshiba laptops that use ACPI and the Toshiba ACPI extensions.

The project monitors function keys and Toshiba-specific buttons (including the CD player buttons and the state of the laptop lid) and responds appropriately.

FSA::Rules is a Perl module to build simple rules-based state machines in Perl.

Synopsis

my $fsa = FSA::Rules->new(
ping => {
do => sub {
print "ping!n";
my $state = shift;
$state->result(pong);
$state->machine->{count}++;
},
rules => [
game_over => sub { shift->machine->{count} >= 20 },
pong => sub { shift->result eq pong },
],
},

pong => {
do => sub { print "pong!n" },
rules => [ ping => 1, ], # always goes back to ping
},
game_over => { do => sub { print "Game Overn" } }
);

$fsa->start;
$fsa->switch until $fsa->at(game_over);

This class implements a simple state machine pattern, allowing you to quickly build rules-based state machines in Perl. As a simple implementation of a powerful concept, it differs slightly from an ideal DFA model in that it does not enforce a single possible switch from one state to another. Rather, it short circuits the evaluation of the rules for such switches, so that the first rule to return a true value will trigger its switch and no other switch rules will be checked. (But see the strict attribute and parameter to new().) It differs from an NFA model in that it offers no back-tracking. But in truth, you can use it to build a state machine that adheres to either model--hence the more generic FSA moniker.

FSA::Rules uses named states so that its easy to tell what state youre in and what state you want to go to. Each state may optionally define actions that are triggered upon entering the state, after entering the state, and upon exiting the state. They may also define rules for switching to other states, and these rules may specify the execution of switch-specific actions. All actions are defined in terms of anonymous subroutines that should expect an FSA::State object itself to be passed as the sole argument.

FSA::Rules objects and the FSA::State objects that make them up are all implemented as empty hash references. This design allows the action subroutines to use the FSA::State object passed as the sole argument, as well as the FSA::Rules object available via its machine() method, to stash data for other states to access, without the possibility of interfering with the state or the state machine itself.

Geography::States is a Perl module with map states and provinces to their codes, and vice versa.

SYNOPSIS

use Geography::States;

my $obj = Geography::States -> new (COUNTRY [, STRICT]);

EXAMPLES

my $canada = Geography::States -> new (Canada);

my $name = $canada -> state (NF); # Newfoundland.
my $code = $canada -> state (Ontario); # ON.
my ($code, $name) = $canada -> state (BC); # BC, British Columbia.
my @all_states = $canada -> state; # List code/name pairs.

This module lets you map states and provinces to their codes, and codes to names of provinces and states.

The Geography::States - new ()> call takes 1 or 2 arguments. The first, required, argument is the country we are interested in. Current supported countries are USA, Brazil, Canada, The Netherlands, and Australia. If a second non-false argument is given, we use strict mode. In non-strict mode, we will map territories and alternative codes as well, while we do not do that in strict mode. For example, if the country is USA, in non-strict mode, we will map GU to Guam, while in strict mode, neither GU and Guam will be found.

The state() method

All queries are done by calling the state method in the object. This method takes an optional argument. If an argument is given, then in scalar context, it will return the name of the state if a code of a state is given, and the code of a state, if the argument of the method is a name of a state. In list context, both the code and the state will be returned.

If no argument is given, then the state method in list context will return a list of all code/name pairs for that country. In scalar context, it will return the number of code/name pairs. Each code/name pair is a 2 element anonymous array.

Arguments can be given in a case insensitive way; if a name consists of multiple parts, the number of spaces does not matter, as long as there is some whitespace. (That is "NewYork" is wrong, but "new YORK" is fine.)

Metawriter provides an editor for interlinked texts.

It is useful for writing highly structured documentation, or creating a mindmap with link tracking.

Each text is given a name, a title, a group, and a state marker.

The content syntax is similar to that used by a Wiki.