Free personal statements software for linux

Regular Statement String (RSS) provides several libraries in C, Java, and COM to implement and demonstrate the key-value development method using well-designed "strings" (RSS) as the media. Regular Statement String also shows a way to write "Process Oriented" applications.
Enhancements:
- This release adds an implementation for SUN Solaris (SPARC).

Saccs personal accounting provides a simple Web-based personal accounting package.
A person can have multiple accounts. Multiple installations on one system can accommodate multiple users.
Details:
Perl and MySQL. Certain perl libraries such as HTML::Template and DBI are required. Apache or something like it is recommended.
Will run on almost anything that can handle apache and perl.
I wrote a simple set of scripts to do web-based tracking of my bank accounts, credit card and cash balances, and "who owes me how much". This worked well enough for 3 years, so I want to release it for others to use. But the original is very dirty code and hard to install, so Im writing a new one, with the lessons learned in 3 years, that will also be properly modularised and packaged.
Main features:
- Create/open an account: bank or credit card or "community". You can have as many of these as will fit in the menu, more if you dont mind crowding.
- Bank account detail display will show date, description, "cleared" (think check) per month. It will show a balance and a "cleared" balance. The "cleared" balance should be the same as what your ATM shows you. It will also show the months net inflow and outflow.
- For bank accounts, previous months can be viewed. The month display will show beginning and ending balances and light up discrepancies.
- For credit cards, a running balance total will be shown along with date, item description, etc. When you receive your monthly statement, delete the items that are correct and enter the balance as a new starting point for the calculation. This helps to keep track of what youre spending on the card.
- "Community" shows a grid, each column corresponds to a friend and each row corresponds to money owed to or by one of the friends. The last row, the total, shows the total owed to or by the friend. Very useful for roommates and easier to use than describe.
- Transfers between accounts.
- No direct communication with any financial institution.
Enhancements:
- Fixed bug in adding names in community account
- Added the totals.

SQL::Statement::Embed can embed a SQL engine in a DBD or module.

SQL::Statement is designed to be easy to embed in other modules and to be especially easy to embed in DBI drivers. It provides a SQL Engine and the other module needs to then provide a data source and a storage mechanism. For example, the DBD::CSV module uses SQL::Statement as an embedded SQL engine by implementing a file-based data source and by using DBI as the user interface. Similarly DBD::Amazon uses SQL::Statement as its SQL engine, provides its own extensions to the supported SQL syntax, and uses on-the-fly searches of Amazon.com as its data source.

SQL::Statement is the basis for eight existing DBDs (DBI database drivers). If you have a new data source, you too can create a DBD without having to reinvent the SQL wheel. Its fun, its easy, become a DBD author today!

SQL::Statement can be also be embedded without DBI. Well explore that first since developing a DBD uses most of the same methods and techniques.

The role of SQL::Statement subclasses

SQL::Statement provides a SQL parsing and execution engine. It does not provide a data source or storage mechanism other than in-memory tables. The DBD::File module is a subclass of SQL::Statement that provides access to file-based storage mechanisms. Its quite possible to use things other than files as data souces, in which case we wouldnt use DBD::File, instead wed replace DBD::Files methods with our own. In the examples below, well use DBD::File, replacing only a few methods.

SQL::Statement provides SQL parsing and evaluation and DBD::File provides file-based storage. The only thing missing is a data source - what we actually want to store and query. As an example suppose we are going to create a subclass called Foo that will provide as a data source a simple file similar to a passwd file - one record per line, fields separated by colons, with only three fields "username, uid, gid".

Consider what needs to happen to perform a SELECT query on our Foo data:

* recieve a SQL string
* parse the SQL string into a request structure
* open the table(s) specified in the request
* define column names and postions for the table
* read rows from the table
* convert the rows from colon-separated format into perl arrays
* match the columns and rows against the requested selection criteria
* return requested rows and columns to the user

To perform operations like INSERT and DELETE, we also need to:

* convert rows from perl arrays into colon-separated format
* write rows
* delete rows

SQL::Statement takes care of all of the SQL parsing and evaluation. DBD::File takes care of file opening, reading, writing, and deleting. So the only things Foo is really responsible for are:

* define column names and postions for the table
* convert rows from colon-separated format into perl arrays
* convert rows from perl arrays into colon-separated format

In SQL::Statement subclasses these responsibilities are assigned to two objects, a ::Statement object is responsible for opening the table, defining the column names and positions, and for creating new ::Table objects. A ::Table object is responsible for reading, converting, writing, and deleting data.

GNOME Personal Web Server is a user friendly web server with GUI included in GNOME-Network.

KDE Personal Wiki engine for KDE, made for only personal use. Consider it a replacemente of KNotes and such apps.

You can create/remove pages, links between pages are automatically created.

I hope you like my first app.