Free doubts software for linux

PolkaDot is a really simple blogging system, roughly based on Blurt, which in turn is based on Bloxsom.
PolkaDot project is much simpler than either, both in terms of installation/configuration as well as its (minimal) feature set. Its also written in PHP, rather than Perl like its inspirations.
Its short for "Itsy Bitsy Teenie Weenie Yellow Polka-Dot Blogkini." Or did you mean "Why write PolkaDot?" Actually, my friend Roger has a blog and I was giving him a hard time because hes using WordPress rather than writing his own blogging software. (I mean, really, what kind of a geek doesnt write his own blogging software.) I had seen Blurt on Freshmeat recently, and decided to whip up something similar in PHP. Took a couple hours, total. (Granted, I grabbed all the hard code from php.net comments.)
Main features:
- Its free.
- It just needs PHP. Thats all. No database. No external libraries. No Perl or ASP. Nothing fancy at all. Itll run on the cheapest of hosts.
- Theres no real installation.
- Theres very little configuration. And, even if you dont configure a thing, itll still work.
- Its simple as can be:
- Posts are just text files.
- Categories are just sub-directories.
Version restrictions:
- Very few features.
- No RSS feed. (Although I might add this.)
- No comments. (Doubt Ill add this.)
- Uses system time. Im on the east coast. The host is on the west coast. So all the posts show a time 3 hours earlier than my local time. (I might fix this.)
- No fancy stuff like calendars and opinion polls.
- Probably doesnt scale real well. (But, if you wanted a large site, why would you even think of using this software?)
- A whole lot of other things that arent coming to me right at the moment.

Sound Studio is a Tcl/Tk application written by Paul Sharpe as his third year individual project, for which he received the Microsoft Prize for Software Engineering. It was subsequently improved by Robin Whitehead.

It enables recording, playback and simple cut & paste editing of sound files of diverse formats on a PC equipped with a soundcard and the OSS (formally VoxWare) sound drivers.

It uses Lance Norskogs Sox for format conversion; the version weve used is bundled together with this software in its entirety to prevent incompatibility problems, although you should try it with your own sox if you have a more recent one.

Sound Studio is now "finished", but no doubt there are loads of bugs still to be found and features to be added.

This CGI script acts as an HTTP or FTP proxy. Through it, you can retrieve any resource that is accessible from the server it runs on. This is useful when your own access is limited, but you can reach a server that in turn can reach others that you cant.
In addition, the user is kept as anonymous as possible from any servers. Common uses include: anonymous proxies similar to The Anonymizer, other personal uses, VPN-like functionality, and others. Its very simple to install, and very configurable.
When an HTML resource is retrieved, its modified so that all links in it point back through the same proxy, including images, form submissions, and everything else. Once youre using the proxy, you can browse normally and (almost) forget its there.
Configurable options include text-only support (to save bandwidth), selective cookie and script removal, simple ad filtering, access restriction by server, custom encoding of target URLs and cookies, and more-- there are about 45 options so far.
CGIProxy can run under mod_perl unchanged. It requires Perl 5.004 or later; Perl 5.6.1 or later may be required in future releases.
Version restrictions:
- Anonymity MAY NOT BE PERFECT!! In particular, there may be some holes where JavaScript can slip through. (If you find these or any other anonymity holes, please tell me!) For best anonymity, turn JavaScript off in your browser.
- URLs generated by JavaScript or similar mechanisms wont be re-proxyed correctly. JavaScript in general may not work as expected, especially if it accesses the network.
- If you browse to many sites with cookies, CGIProxy may drop some, but I havent seen this happen yet.
- To save CPU time, I took some shortcuts with URL-handling. I doubt these will ever affect anything, but tell me if you have problems. (The shortcuts are listed in the source code.)
- I didnt follow the spec on HTTP proxies, and there are violations of the protocol. Actually, this whole concept is a violation of the proxy model, so Im not too worried. If any protocol violations cause you problems, please let me know.
- Only HTTP and FTP are supported so far.
Enhancements:
- "javascript:" URLs are now handled better.
- rot-13 encoding of cookies now works correctly.
- "about:blank" pages no longer generate a warning page.
- The URL field in the start page now gets focus automatically.
- A few other bugfixes and workarounds are included.

XPilot project is a multi-player 2D client/server space game.
XPilot is a multi-player 2D space game. Some features are borrowed from classics like the Atari coin-ups Asteroids and Gravitar, and the home-computer games Thrust (Commodore 64) and Gravity Force (Commodore Amiga), but XPilot has many new aspects too.
Main features:
- True client/server based game; optimal speed for every player.
- Meta server with up to date information about servers hosting games around the world.
- A web of world-wide rating servers; compare your skills with pilots from all around the world, and climb the ladder of the world-wide rating list.
- Real physics; particles of explosions and sparks from your engines all affect you if youre hit by them. This makes it possible to kill someone by blowing them into a wall with engine thrust or shock waves from explosions.
- Specialized editors for editing ship-shapes and maps.
- Game objective and gameplay adjustable through a number of options, specified on the commandline, in special option files, or in the map files. Examples of modes of the game:
- classical dogfight; equipped with only your gun, you have to rely on your maneuvering and tactical skills
- team; fight together, steal other teamss treasures (involves flying around with a ball in a string, much like in Thrust) and blow up their targets (which are, no doubt, heavily guarded)
- all out nuclear war; chose carefully between more than twenty weapon and defense systems to stay alive and annihilate your enemies
- race; make it through the deadly course before your opponents
- Adjustable gravity; adjustable by putting special attractors or deflectors in the world, or by adjusting the global gravity in various ways.
- Cannons and personalized and vengeful robot fighters give you a hard time.
- Watch your energy, and remember to dock with a fuel station to refuel before its too late.
- Defend your home base, or terrorize and steal someone elses.
- Equip your ship with the 15+ defense and weapon systems: afterburners, cloaking devices, sensors, transporters, extra cannons, mines and bombs, rockets (smarts, torpedos and nuclear), ECM, laser, extra tanks, autopilot etc.
To start playing, you need to connect to a server by using a client program called xpilot. There are always servers running if you check with the meta server, but if you for some reason do not want to join them, youll have to start a server of your own (see man-page xpilots(6)).
Enhancements:
- Team cannons could kill teammates with laser pulses. Fixed.
- On the map Death Star one can destroy a large number of targets with one FNC. This results in packet buffer overflows and slow updates. To overcome this a smarter map update algorithm is implemented in the server and also map updates are now limited to max 2 KB per network packet.
- The default score font was reduced from 15 to 13.
- When the server sends map updates to the client these are now always acknowledged immediately by the client. This should help prevent stalls or lock-ups on maps where are a large number of targets or cannons can be destroyed. It should also reduce the number of very big server frame update packets.
- Robots no longer try to go after players who arent in playing mode.

netshng project can be used in the development of applications which require direct communication (using the netsh protocol) with a Foxmoxie Networks STRATA-family router.

This program requires the use of libnetshclient. If in doubt, use the latest versions of both.

This application has been tested on the Linux platform only.

To compile, you must have:

GNU make 3.81+
GNUtls 1.4.4+
libnetshclient 2.2.0+

and of course, standard Posix and ANSI headers.

To build the binary, simply edit the Makefile and change the value of the variable named LIBNETSHCLIENT to the directory of your libnetshclient source and build.

Once done, type make.

There is presently no install mechanism, so this must be done manually.

The KLogo-Turtle is an interpreter of the LOGO language for KDE desktops.
The KLogo-Turtle is a useful tool for teaching geometry and the basic principles of the programming of computer. Children can study the mathematics of geometry in an interactive and constructive way.
KLogo-Turtle has syntax a little different than the LOGO language developed at MIT. Look at the documents link. Comments, doubts and suggestions, please use the e-mail link.
KLogo-Turtle supports commands in the languages english, portuguese, german, italian and french.
KLogo-Turtle is under the GPL license and is developed in KDevelop by Euclides Chuma.
Enhancements:
- Release version stable (0.6) with support for commands in english, portuguese, german, italian and french.

Pod::HTML2Pod Perl module can translate HTML into POD.

SYNOPSIS

# Use the program html2pod that comes in this dist, or:
use Pod::HTML2Pod;
print Pod::HTML2Pod::convert(
file => my_stuff.html, # input file
a_href => 1, # try converting links
);

Larry Wall once said (1999-08-27, on the pod-people list, I do believe): "The whole point of pod is to get people to document stuff they wouldnt document in any other form."

To that end, I wrote this module so that people who are unpracticed with POD but in a hurry to simply document their programs or modules, could write their documentation in simple HTML, and convert that to POD. Thats what this module does.

Specifically, this module bends over backwards to try to turn even vaguely plausable HTML into POD -- and when in doubt, it simply ignores things that it doesnt know about, or cant render.

FUNCTIONS

This module provides one documented function, which it does not export:
Pod::HTML2Pod::convert( ...options... )

This returns a single scalar value containing the converted POD text, with some comments after the end.

This function takes options:

file => FILENAME,

Specifies that the HTML code is to be read from the filename given.

handle => *HANDLE,

Specifies that the HTML code is to be read from the open filehandle given (e.g., $fh_obj, *HANDLE, *HANDLE{IO}, etc.) If you specify this, but fail to specify an actual handle object, inscrutible errors may result.

content => STRING,

Specifies that the HTML code is in the string given. (Alternately, pass a reference to the scalar: content => $stuff.)

tree => OBJ,

Specifies that the HTML document is contained in the given HTML::TreeBuilder object (or HTML::Element object, at least).

a_name => BOOLEAN,

Specifies whether you want to try converting < a name="..." > elements. By default this is off -- i.e., such elements are ignored.

a_href => BOOLEAN,

Specifies whether you want to try converting < a href="..." > elements. By default this is off -- i.e., such elements are ignored. If on, bear in mind that relative URLs cannot be properly converted to POD -- any relative URLs will be complained about in comments after the end of the document. Normal absolute URLs will be treated as best they can be. Note that URLs beginning "pod:..." will be turned into POD links to whatever follows; that is, "pod:Getopt::Std" is turned into L< Getopt::Std >

debug => INTEGER,

Puts Pod::HTML2Pod into verbose debug mode for the duration of processing this this HTML document. INTEGER can be 0 for no debug output, 1 for a moderate amount that will cause the HTML syntax tree to be be dumped at the start of the conversion, and 2 for that plus a dump of the intermediate POD doctree, plus a few more inscrutible diagnostic messages. Looking at the trees dumped might be helpful in making sense of error messages that refer to a particular node in the parse tree.

The programming of measurement instruments can be real pain. There are many different protocols, sent over many different interface and bus systems. For every programming language you want to use, you have to find libraries that support both your device and its bus system.
In order to ease this unfortunate situation, the VISA [1] specification was defined in the middle of the 90ies. Today VISA is implemented on all significant operating systems. A couple of vendors offer VISA libraries, albeit mostly in binary form.
These libraries work together with arbitrary peripherical devices, although they may be limited to certain interface devices, such as the vendors GPIB card. Virtual Instrument Software Architecture
The VISA specification has explicit bindings to Visual Basic, C, and G (LabVIEWs graphical language). However, you can use VISA with any language capable of calling functions in a DLL. Python is such a language.
PyVISA project is a VISA binding for Python. In relies on an external library file that you can download from your interface vendors web pages (National Instruments, Agilent, etc). PyVISA implements a convenient and Pythonic access to this library in two layers:
1. First, there is the lower level vpp43, which directly calls the VISA functions from Python. See the PyVISA low-level implementation for more information.
2. On top of it, an object-oriented Python module has been created called visa simply. In case of doubt, use visa because it is easier and more convenient. vpp43 is only for people who need full control or the official VISA functions for some reason. See the PyVISA manual for more information.
Enhancements:
- PyVISA can now cope with older VISA implementations, too.