Free xiangqi 0.62 3 software for linux

CGI::Wiki is a toolkit for building Wikis.

Helps you develop Wikis quickly by taking care of the boring bits for you. You will still need to write some code - this isnt an instant Wiki.

SYNOPSIS

# Set up a wiki object with an SQLite storage backend, and an
# inverted index/DB_File search backend. This store/search
# combination can be used on systems with no access to an actual
# database server.

my $store = CGI::Wiki::Store::SQLite->new(
dbname => "/home/wiki/store.db" );
my $indexdb = Search::InvertedIndex::DB::DB_File_SplitHash->new(
-map_name => "/home/wiki/indexes.db",
-lock_mode => "EX" );
my $search = CGI::Wiki::Search::SII->new(
indexdb => $indexdb );

my $wiki = CGI::Wiki->new( store => $store,
search => $search );

# Do all the CGI stuff.
my $q = CGI->new;
my $action = $q->param("action");
my $node = $q->param("node");

if ($action eq display) {
my $raw = $wiki->retrieve_node($node);
my $cooked = $wiki->format($raw);
print_page(node => $node,
content => $cooked);
} elsif ($action eq preview) {
my $submitted_content = $q->param("content");
my $preview_html = $wiki->format($submitted_content);
print_editform(node => $node,
content => $submitted_content,
preview => $preview_html);
} elsif ($action eq commit) {
my $submitted_content = $q->param("content");
my $cksum = $q->param("checksum");
my $written = $wiki->write_node($node, $submitted_content, $cksum);
if ($written) {
print_success($node);
} else {
handle_conflict($node, $submitted_content);
}
}

Wmcalc is simple little application that I am writing. If youre not familiar with these windowmanagers, check them out in the links section. Of course, it should work in just about any window manager.
Wmcalc is a 64x64 pixel application that performs all the functions (and eventually more) of a simple four function calculator. It includes a 10 digit alpha-numeric display, and twenty buttons for user input. Clicking on the display will clear the calculator.
Installation:
Untar the file:
tar xvzf wmcalc-0.3.tar.gz
CD to source directory:
cd wmcalc-0.3
Compile it:
make clean; make
Copy the config file:
cp .wmcalc ~
Put the executable somewhere in your path:
mv wmcalc /usr/local/bin (or anyhere in your path)
Run it:
wmcalc &
Grab the appicon and move it to the dock.
Change the settings to start with Windowmaker
Afterstep Wharf 1.6.??: (I dont use Afterstep anymore, so...)
*Wharf wmcalc -Swallow "wmcalc" wmcalc &
***Note***:
The appicon only has a two pixel border where you can grab and move it. It is easiest to grab along the bottom edge.
If make doesnt work, you may need to fiddle with the settings in the Makefile.
Tested on: (Well, it runs, I dont know if Tested is quite right...)
WindowMaker-0.62.1
X Clients: Red Hat 6.0, Kernel 2.2.8
Usage:
usage: wmcalc [-g geometry] [-d dpy] [-v] [-f configfilename] [-h]
-g < geometry > Window Geometry - ie: 64x64+10+10
-d < display > Display - ie: 127.0.0.1:0.0
-v Verbose Mode.
-h Help. This message.
-f < filename > Full path to configuration file to use.
Buttons are defined as:
____________________
| x00 | where: x = 1 for Left Mouse Button
| 0 1 2 3 4 5 6 7 8 9| x = 2 for Middle Mouse Button
|--------------------| x = 3 for Right Mouse Button
|x01 x02 x03 x04 x05 |
|x06 x07 x08 x09 x10 | Note: the numbers 0..9 are the indicators
|x11 x12 x13 x14 x15 | for memory cells 0..9 respectively
|x16 x17 x18 x19 x20 |
--------------------
Button Functions:
100 Reinitialize the calculator, and both Registers
(Clear All)
200 Clear all the memory registers (0..10)
300 Clear the current number being entered only
x11 Start a program defined by CalcStart variable in config file
1yy Perform function shown on button
2yy Recall number from memory location [0-9] to display
for calculation
if yy = 2,3,4, 7,8,9, 12, 13, 14, 17
otherwise, can run a user-defined function (not implemented)
3yy Store Displayed number in memory location [0-9]
if yy = 2,3,4, 7,8,9, 12,13,14, 17
otherwise, can run a user-defined function (not implemented)
1xx Hopefully the other functions are obvious from their
button graphics.
Enhancements:
- Added "Locked" memory capabilities via config file
- General Code clean-up
- Keyboard Support - may not be platform independent

Munin is a tool for graphing all sorts of information about one or more servers and displaying it in a web interface. Munin uses the execellent RRDTool (written by Tobi Oetiker) and is written in Perl. Munin has a master/node architecture.
The master connects to all the nodes at regular intervals, and asks them for data. It then stores the data in RRD-files, and (if needed) updates the graphs. One of the main goals has been ease of creating own "plugins" (graphs).
Installation:
edit Makefile.config
- create the user "munin"
- make install-main
- create a cron-entry to run "munin-cron" as the user "munin" every 5 minutes
- if you want to use the dynamic graphs, configure the cgi directory (an example for apache can be found in README-apache-cgi).

This package provides a complete http client library. It currently implements most of the relevant parts of the HTTP/1.0 and HTTP/1.1 protocols, including the request methods HEAD, GET, POST and PUT, and automatic handling of authorization, redirection requests, and cookies.

Furthermore the included Codecs class contains coders and decoders for the base64, quoted-printable, URL-encoding, chunked and the multipart/form-data encodings. The whole thing is free, and licenced under the GNU Lesser General Public License (LGPL) (note that this is not the same as the GPL).

Following are the kits and documentation for the HTTPClient Version 0.3-3. If you have any problems, bugs, suggestions, comments, etc. see the info on debugging and reporting problems. An older version of these pages are also available in Japanese, thanks to the kindly efforts of Yuji Kumasaka.

Using the HTTPClient should be quite simple. First add the import statement import HTTPClient.*; to your file(s). Next you create an instance of HTTPConnection (youll need one for every server you wish to talk to). Requests can then be sent using one of the methods Head(), Get(), Post(), etc in HTTPConnection.

These methods all return an instance of HTTPResponse which has methods for accessing the response headers (getHeader(), getHeaderAsInt(), etc), various response info (getStatusCode(), getReasonLine(), etc), the response data (getData(), getText(), and getInputStream()) and any trailers that might have been sent (getTrailer(), getTrailerAsInt(), etc). Following are some examples to get started.
To retrieve files from the URL "http://www.myaddr.net/my/file" you can use something like the following:
try
{
HTTPConnection con = new HTTPConnection("www.myaddr.net");
HTTPResponse rsp = con.Get("/my/file");
if (rsp.getStatusCode() >= 300)
{
System.err.println("Received Error: "+rsp.getReasonLine());
System.err.println(rsp.getText());
}
else
data = rsp.getData();

rsp = con.Get("/another_file");
if (rsp.getStatusCode() >= 300)
{
System.err.println("Received Error: "+rsp.getReasonLine());
System.err.println(rsp.getText());
}
else
other_data = rsp.getData();
}
catch (IOException ioe)
{
System.err.println(ioe.toString());
}
catch (ParseException pe)
{
System.err.println("Error parsing Content-Type: " + pe.toString());
}
catch (ModuleException me)
{
System.err.println("Error handling request: " + me.getMessage());
}

This will get the files "/my/file" and "/another_file" and put their contents into byte[]s accessible via getData(). Note that you need to only create a new HTTPConnection when sending a request to a new server (different protocol, host or port); although you may create a new HTTPConnection for every request to the same server this not recommended, as various information about the server is cached after the first request (to optimize subsequent requests) and persistent connections are used whenever possible (see also Advanced Info).

To POST form data from an applet back to your server you could use something like this (assuming you have two fields called name and e-mail, whose contents are stored in the variables name and email):
try
{
NVPair form_data[] = new NVPair[2];
form_data[0] = new NVPair("name", name);
form_data[1] = new NVPair("e-mail", email);

// note the convenience constructor for applets
HTTPConnection con = new HTTPConnection(this);
HTTPResponse rsp = con.Post("/cgi-bin/my_script", form_data);
if (rsp.getStatusCode() >= 300)
{
System.err.println("Received Error: "+rsp.getReasonLine());
System.err.println(rsp.getText());
}
else
stream = rsp.getInputStream();
}
catch (IOException ioe)
{
System.err.println(ioe.toString());
}
catch (ModuleException me)
{
System.err.println("Error handling request: " + me.getMessage());
}

Here the response data is read at leisure via an InputStream instead of all at once into a byte[].

As another example, if you want to upload a document to a URL (and the server supports http PUT) you could do something like the following:
try
{
URL url = new URL("http://www.mydomain.us/test/my_file");

HTTPConnection con = new HTTPConnection(url);
HTTPResponse rsp = con.Put(url.getFile(), "Hello World");
if (rsp.getStatusCode() >= 300)
{
System.err.println("Received Error: "+rsp.getReasonLine());
System.err.println(rsp.getText());
}
else
text = rsp.getText();
}
catch (IOException ioe)
{
System.err.println(ioe.toString());
}
catch (ModuleException me)
{
System.err.println("Error handling request: " + me.getMessage());
}

Locale::Maketext::Lexicon::Tie is a Perl module to use tied hashes as lexicons for Maketext.

SYNOPSIS

package Hello::I18N;
use base Locale::Maketext;
use Locale::Maketext::Lexicon {
en => [ Tie => [ DB_File => en.db ] ],
};

This module lets you easily tie the %Lexicon hash to a database or other data sources. It takes an array reference of arguments, and passes them directly to tie().

Entries will then be fetched whenever it is used; this module does not cache them.