Free xboard us stories software for linux

PictureStories lets you make little webpages of stories you write where some of the words are replaced with images which is called rebus. What makes PictureStories cool is that the images are dynamically pulled from popular web-based image search engines (like Google).

Weve seen lots of cute little storybooks for kids that are like this, and we thought itd be neat to be able to do my own. Someone has probably had this idea before, but we couldnt find anything online anywhere, so we wrote it.

Vega Strike is a Linux action space simulator designed to bring 3d space combat to a whole new level of graphics, gameplay, and customizability.
Enhancements:
- Also featured is an introductory story campaign showing what the future of Vega Strike storytelling will look like.
- Hopefully we will release a campaign editor at some point which will allow users to contribute their own stories and dialogue to the game.
- The new screenshot (imaging) key is activated with i. PC users will find a link to the screenshots in the start menu, linux users will find it in the home directory ~/.vegastrike043/textures/
- Strangelet and PeteyG have worked for months on the art you will experience in 2.4.3.
- Dandandamans hard work has made the Loki Installer a reality for our linux users. You folks can toss gcc out the window and just download and run, like the mac and windows releases, and Fadookie and Mamiya0taru have polished the windows installer for the rest of the computational world.
- And my mac is finally out of the shop, and I have finally figured out how to make OS X 10.1 and 10.2 compatible binaries through OS X 10.3, so users with any Mac OS X can still experience Vega Strike. (this is not as easy as it sounds--look how many OS X 10.3 only apps there are out there and youll realize)
- All the items missing from 0.4.2 listed in the missing section have finally been added to 0.4.3, and thats the reason the developers decided to push for another 0.4.x release before forging ahead to 0.5.0 which will likely have a new gameplay feel and more stories.

Local Lyrics is a python based amaroK-script requires amaroK 1.4!

I wrote simple wrappers for dcop-calls (using the shell-tool dcop), kdialog and amaroKs script system while writing this script. Use them if you want (its all LGPL) See the .tar.bz2s contense and: http://twoday.tuwien.ac.at/pub/stories/22759/

This lyrics-plugin simply scans a selected folder for textfiles with lyrics. This might be usefull when you have a lot of lyrics stored on your harddisc, but they are not available on lyrc.com.ar or a simmilar service.

Installation:

Open the lyrics-filesystem-x.x.amarokscript.tar.bz2 with amaroKs script managers script install option.

Usage:

Start the script with amaroKs script manager.
Select the directory in which the lyrics are stored.
The filenames of the lyrics have to be:

"artist - title.txt"
or
"title.txt"

Now amaroK will search this folder for lyrics, when there are none in its database for the current track.

BoboMail is a so called webmail application, which provides mail access through a web interface.
It is distributed under the GNU GPL. See COPYING in the package or go to http://www.gnu.org for details.
The first version of BoboMail was used for about a year and a half in the intranet of the Computer Club Ostfriesland (one of Germanys largest computer clubs, see http://www.cco-ev.de if you understand German). I wrote my own webmailer, because at that time only some Perl scripts were available, which were not easy to customize (e.g. German interface).
The name of BoboMail comes from former name of ZPublisher, a cgi framework used by the developer.
I hope you will find BoboMail usefull. Please send complaints (e.g. spelling mistakes), criticism, security advices, suggestions, praises and everything else to ich@henning-schroeder.de or visit me (Henning) on my personal webpage at http://www.henning-schroeder.de/en Important acknowledgement: This product includes software developed by Digital Creations for use in the Z Object Publishing Environment (htt://www.zope.org).
The BoboMail distribution contains Zopes ZPublisher and ZTemplates. These compoments underly the Zope Public License (ZPL). They are packages with BoboMail for easier installation. BoboMail is hosted at Sourceforge (http://sourceforge.net). If you are interested in BoboMail development please visit the its webpage at http://bobomail.sourceforge.net Besides I want to make BoboMail even more modular so that my stuff can be used for a mailinglist archiver or a web-forum. Attention: I really would like to know where you will use BoboMail. Please tell me your success stories
Main features:
- read, write, reply, forward, delete and bounce messages
- send and receive attachments
- decodes quoted-printable, base64 and uuencoded
- handles HTML-mails properly (with inline images!)
- does not need Javascript
- direct support for the following MIME types: message/rfc822, message/delivery-status, multipart/alternative, multipart/mixed, multipart/report, multipart/related, multipart/digest, text/plain, text/html, text/x-vcard, image/jpeg, text/rfc822-headers, image/png, image/x-xpixmap, image/gif
- works with POP3-servers and partially IMAP4 (spool-files under development)
- easy to modify and customize through HTML-templates
- modular design provides easy interface for other authentication methods and mail protocols
- provides optionally its own fast multithreading webserver (BoboMailHTTPD)
- multi-lingual support (i18n) - currently English, Brazilian Portuguese, Finish, Spanish and German
- and its 100% Python
Enhancements:
- with the help from Ken Causey the annoying first-login-bug is fixed now :-)
- IMAP support for uw-imapd, expects additional folders in $HOME/Mail
- now runs with Python 2.x without problems
- new look, using nicer template inspired by zope.org
- and some other small bug fixes (see cvs if you like)

Gnusto project is a Javascript-based interpreter for Z-machine adventure games.

Gnusto is a Mozilla app which lets you play adventure games-- specifically, the hundreds of games both modern and ancient available in the Z-machine format.
You can try out the most recent version at the installation / release notes page. And we need testers! The more people who test it now, the better the program will eventually be.

Were very close to full standards compliance for version 3, 4, 5, 7 and 8 stories, the most common versions. Longer-term ideas along the way are the ability to download stories from the IF Archive (with help from Bafs Guide), a disassembler (already written and awaiting integration), a source-level debugger for Inform, and possibly integration with the Inform tool chain to produce some kind of IDE.

The name "gnusto" comes from a spell in the Enchanter series. Its use in this project was suggested by Boluc Papuccuoglu in a thread about the project on rec.games.int-fiction.

Geo:Coder:US 1.00 offers a full-feature facility for geocoding US addresses, that is, estimating the latitude and longitude of any street address or intersection in the United States, using the TIGER/Line data set from the US Census Bureau. Geo:Coder:US uses Geo:TigerLine to parse this data, and DB_File to store a highly compressed distillation of it, and Geo:StreetAddress:US to parse addresses into normalized components suitable for looking up in its database.

You can find a live demo of this code at http://geocoder.us/. The demo.cgi script is included in eg/ directory distributed with this module, along with a whole bunch of other goodies. See Geo:Coder:US:Import for how to build your own Geo:Coder:US database.

Consider using a web service to access this geocoder over the Internet, rather than going to all the trouble of building a database yourself. See eg/soap-client.pl, eg/xmlrpc-client.pl, and eg/rest-client.pl for different examples of working clients for the rpc.geocoder.us geocoder web service.

Major Features:

1. Geo:Coder:US->geocode( $string )
   • Given a string containing a street address or intersection, return a list of specifiers including latitude and longitude for all matching entities in the database. To keep from churning over the entire database, the given address string must contain either a city and state, or a ZIP code (or both), or geocode() will return undef.
   • geocode() will attempt to normalize directional prefixes and suffixes, street types, and state abbreviations, as well as substitute TIGER/Line's idea of the "primary street name", if an alternate street name was provided instead.
   • If geocode() can parse the address, but not find a match in the database, it will return a hashref containing the parsed and normalized address or intersection, but without the "lat" and "long" keys specifying the location. If geocode() cannot even parse the address, it will return undef. Be sure to check for the existence of "lat" and "long" keys in the hashes returned from geocode() before attempting to use the values! This serves to distinguish between addresses that cannot be found versus addresses that are completely unparseable.
   • geocode() attempts to be as forgiving as possible when geocoding an address. If you say "Mission Ave" and all it knows about is "Mission St", then "Mission St" is what you'll get back. If you leave off directional identifiers, geocode() will return address geocoded in all the variants it can find, i.e. both "N Main St" and "S Main St".
   • Don't be surprised if geocoding an intersection returns more than one lat/long pair for a single intersection. If one of the streets curves greatly or doglegs even slightly, this will be the likely outcome.
   • geocode() is probably the method you want to use. See more in the following section on the structure of the returned address and intersection specifiers.
2. Geo:Coder:US->geocode_address( $string )
   • Works exactly like geocode(), but only parses addresses.
3. Geo:Coder:US->geocode_intersection( $string )
   • Works exactly like geocode(), but only parses intersections.
4. Geo:Coder:US->filter_ranges( $spec, @candidates )
   • Filters a list of address specifiers (presumably from the database) against a query specifier, filtering by prefix, type, suffix, or primary name if possible. Returns a list of matching specifiers. filter_ranges() will ignore a filtering step if it would result in no specifiers being returned. You probably won't need to use this.
5. Geo:Coder:US->find_ranges( $address_spec )
   • Given a normalized address specifier, return all the address ranges in the database that appear to cover that address. find_ranges() ignores prefix, suffix, and type fields in the specifier for search purposes, and then filters against them ex post facto. The intention for find_ranges() to find the closest match possible in preference to returning nothing. You probably want to use lookup_ranges() instead, which will call find_ranges() for you.
6. Geo:Coder:US->lookup_ranges( $address_spec, @ranges )
   • Given an address specifier and (optionally) some address ranges from the database, interpolate the street address into the street segment referred to by the address range, and return a latitude and longitude for the given address within each of the given ranges. If @ranges is not given, lookup_ranges() calls find_ranges() with the given address specifier, and uses those returned. You probably want to just use geocode() instead, which also parses an address string and determines whether it's a proper address or an intersection automatically.
7. Geo:Coder:US->find_segments( $intersection_spec )
   • Given a normalized intersection specifier, find all of the street segments in the database matching the two given streets in the given locale or ZIP code. find_segments() ignores prefix, suffix, and type fields in the specifier for search purposes, and then filters against them ex post facto. The intention for find_segments() to find the closest match possible in preference to returning nothing. You probably want to use lookup_intersection() instead, which will call find_segments() for you.
8. Geo:Coder:US->lookup_intersection( $intersection_spec )
   • Given an intersection specifier, return all of the intersections in the database between the two streets specified, plus a latitude and longitude for each intersection. You probably want to just use geocode() instead, which also parses an address string and determines whether it's a proper address or an intersection automatically.

Requirements: Perl