Free 0.4a software for linux

Zoom is a player for Z-Code stories or games. These are usually text adventures (interactive fiction), and were first created by Infocom with the Zork series of games.

Throughout the 80s, Infocom released many interactive fiction stories before their ambitions to enter the database market finally brought them low.

Zoom has versions for OS X and Unix-like operating systems using X-Windows. You can download the OS X version or the source code using the links to the left. Zoom can be redistributed under the terms of the GNU General Public License.

Obviously, Zoom is quite capable of playing Zork, so those of you who have access to the increasingly rare Infocom games can continue to play them. However, back in 1993, Graham Nelson released Curses and more importantly the Inform compiler that created it. There is now a considerable collection of new interactive fiction of variable quality available. Bafs guide to the interactive fiction archive is absolutely essential for those new to the scene.

picoSQL project is the first Italian Open Source relational database management system.
The project of picoSQL was born in 1995. It was an ODBC driver for COBOL indexed files. It consisted of a DLL written in C++ on Windows 3.1 operating system. In the beginning the main effort was made in order to obtain a good compatibity with existing front-end (mainly the MS-Access, MS-Query and VisualBasic) and in order to see COBOL files as a normalized relational DB.
The obtained success concurs to develop ulteriorly the product, refining the query optimizer and implementing an extended SQL, to exclusion of the DDL (Data Description Language). A later version, called PicoDB, were devoloped on UNIX system in client/server architecture.
PicoSql is released under GPL license; it derives from PicoDB (that remains a Picosoft proprietary product) with the addition of some SQL-DDL statement (CREATE/DROP TABLE(INDEX) and excluding COBOL files compatibility). The C/C++ library that allow the database access from C/C++ programs using the ODBC 2.5 API is released under LGPL license; this allows to link the library with programs that are not under GPL.
PicoSQL can be used from Windows applications (like MS-ACCESS, MS-Query, VB etc.) in client/server modality using the ODBC driver picoSQLNet. It can moreover be used from appropriate Java programs through the JDBC driver comprised in the distribution. Finally it can be used from programs written in C and C++ through its set of ODBC 2.5 compliant API.
PicoSQL lacks at the moment of some common characteristics to the most common RDBMS (like the schema and catalogue concepts and the management of the user permissions who can be obtained anyway using the permissions of the host operating system) but they are just these lacks to make it particularly simple to install and to use and fast in the logons and the queries.
Installation:
The installation is particularly simple: if you have the binary distribution, is sufficient to extract the compressed files in one directory ( under Windows NT/2000/XP) and execute:
startTestDb.sh (Unix/Linux)
PicoSQL consists fundamentally in a program, picosqld, to activate through inetd (or xinetd) or picoserv. In such a way it becomes a net service binded to a port, that is to a entire number comprised between 1 and 65535; this number (as an example 6789) must always be specified on the command line of picosqld. As an example:
picosqld 6789
For the activation with inetd (or xinetd), you must see the relative documentation. picoserv is a simple program that replaces inetd, mainly for scopes of test or debugging: its usage is the following:
picoserv [-f] commandLine portNumber
In our case the activation of picosqld can be obtained with the following command line:
picoserv "picosqld 6789" 6789
To notice as the port number is specified two times, as an argument of picosqld and as an argument of picoserv.
When picosqld receive a connection request, it reads a configuration file to find the necessary informations. This file is a text file on Unix/Linux systems.
# Unix/Lunixthe file read for configuration is
$HOME/.picosql.ini
or, if this file is missing
/etc/picosql.ini
The file consists of sections and parameters. A section begins with the name of the section in square brackets and continues until the next section begins. Sections contain attributes of the form
name=value
The file is line-based - that is, each newline-terminated line represents either a comment, a section name or a parameter. Section and parameter names are not case sensitive. Only the first equals sign in a parameter is significant. Any line beginning with a semicolon (;) or a hash (#) character is ignored, as are lines containing only whitespace. Each section corresponds to a database and comprises information like user, password and DB location. In the following example there are two database declared, the former called picoSqlTest, is accessible by anyone while the latter, called rubrica is accessible only by user pico giving the appropriate password.
[picoSqlTest]
DataDirectory=/home/test.db
[rubrica]
DataDirectory=/home/rubrica.db
User=pico
Password=soft
PicoOdbcTrace=NO
SuspensiveLock=YES
; for picosql client only
server=localhost
port=6789
Enhancements:
- This version fixes a problem on authentication and a bug when the connection fails.

DOTCONF++ library is a dotconf-like configuration file parser written in C++.
dotconf++ is a dotconf like configuration file parser written in C++. It supports macro substitution from the environment or from the file itself, config file inclusion, easy handling of XML like tags, checking for required tags, and more. The whole document (with all inclusions) is parsed into a useful tree structure that is easy to use in your program.
Main features:
Comments:
- # some comment
- ; some comment
- Multivalue parameters:
- ParameterName value1 value2 value3 "value4 with spaces"
- ParameterName1 = value11 value12 value13
Multiline parameters:
- MultilineText id1 "Quick brown
- fox jumps...
- bla bla bla"
- CustomLog /usr/local/apache-ssl/logs/ssl_request_log
- "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x "%r" %b"
Macro substitution from environment or from config file, with default values if substitution not found:
- LogFile ${TEMP_PATH:-"/tmp/default temp path"}
- LogOptions ${PWD:-/tmp}/log_${USER}
Tags ( tags are normal parameters, but they become parent for all parameters between opening and closing tag):
< SectionTag allOnOneLine > onLineParameter=onLineValue < /SectionTag >
< SectionTag tagValue tagValue2 >
inTagParameter "disabled? # comment
< /SectionTag >
#nested tags
< SectionTag tagValue >
TagEnable #parameter without value
< SubSection SubsectionName >
subsectionParameterDisabled Yes;comment
subsectionParameter2Disabled No
< /SubSection >
< /SectionTag >
Quotes and line-terminators inside values:
- Text = "this program is "dot conf-like"" "new line startsnhere"
- Config file inclusion ( with recursion checks ):
- DOTCONFPPIncludeFile ${PWD}/modules.conf