Free publishing a book software for linux

Enhancements:

• Statistics filter & Graphs flter now changed to single Date Filter.
• Date Filter now enabled for Pie Charts & Bar Chart.
• Removal of Error Statistics debugging pop-ups with grand total stats.
• Graphs Bar Chart legend moved to top left.
• Application window & components resized & compacted for better visibility on
• lower resolution screens.
• Prayer Tab Salat selection button highlighting added.
• Prayer Tab Month datagrid...absent salah colour changed from light red/pink
• red to a darker red.
• Options Tab Backup function now enabled.
• Options Tab Restore function now enabled.
• Options Tab Error removal on Edit/Save function, corrupting data files.
• Application data files integrity check & repair code added during startup.

Requirements:

• Adobe AIR

Addresh Book is a (basic) Address Book implemented entirely in Shell Scripts. Current functionality is implemented for adding records, deleting records and searching records.

Note: This project has been largely superceeded by the ZDB project below.

Atom Publishing Protocol framework for Rubys goal is to make adopting Atom Publishing Protocol(APP) support in web applications as easy as it can be. This is to be reached by implementing a framework that handles the protocol-level duties for the programmer, while not making any requirements for the site design. Details of the project are laid down in a roadmap.

The way that this framework realizes this functionality is by implementing a base class for each back-end. At the moment there is only one back-end, for Ruby on Rails. The base classes then expect that the users application responds to a certain interface that makes the content information storing the responsibility of the application.

While implementing the framework Im going to follow two principles, simplicity and generality. Simplicity in that sense that the framework only does what it needs to do, nothing else, thus staying out of the way of the developer, laying down as few constraints on the application as possible.

Generality principle follows on the same track. As the overhead from using the framework is in the minimum, the field of application gets wider. From technical point of view the generality will be helped by multiple back-ends that enable the use of framework in many different environments.

The APP is currently an Internet-Draft and hence most likely will change in near future. For this, it is better to keep the framework as simple as possible so that it can be refactored with minimum effort.

The work for this project is freely available(MIT licensed) from this website. I am writing this framework as a part of my final thesis at the Tampere University of Technology, Finland.

Podcast::Publisher is a Perl module for creating and managing podcasts.

SYNOPSIS

use Podcast::Publisher;

my $podcast = Podcast::Publisher->new;
$podcast->set_logger( sub { my $msg = shift; print $msg; } );
$podcast->set_error_logger( sub { my $msg = shift; print STDERR $msg; } );
my $xml = "./podcast.xml";
$podcast->set_file( $xml );
$podcast->set_remote_root( "http://localhost.localdomain/podcast/publishing/" );
$podcast->set_db_connection( { driver => "mysql",
username => foo,
password => bar,
host => localhost,
database => podcast } );

# If we change podcast information, synchronize this information in the MP3 file itself
$podcast->set_synchronize( 1 );

$podcast->set_metadata( { title => "Chris Podcast",
description => "All About Chris",
"docs" => "http://localhost",
"editor" => "podcastmanager@localhost",
"webmaster" => "podcastmanager@localhost",
} );

# This adds an item to the database, and synchronizes the
# MP3 Tag information in the file with the database
$podcast->add_new_episode( { title => Some title,
author => Chris of course
category => Jazz
description => First in a series of many
mp3 => /home/foobar/mp3s/episode1.mp3 } );

$podcast->set_upload_settings( { host => localhost.localdomain,
username => someuser,
password => somepass,
path => podcast/publishing/,
remote_root => http://localhost.localdomain/podcast/publishing/ } );
$podcast->upload();

DocBook to LaTeX/ConTeXt Publishing project is splitted in two instances working on the same principles. Both instances are intended to produce DVI, PostScript, PDF documents from DocBook SGML or XML sources, by converting first to a high level set of TeX macros.

Even if close, each instance is provided as an independent package and works alone. The available instances are:

dblatex

Publishing is done by using LaTeX.

dbcontext

Publishing is done by using ConTeXt.

mod_litbook is an alternate method for referencing documents.

mod_litbook is an experiment in web techonology - an experiment in document reference and retrieval is at the core of this module. Although the initial "Proof of Concept" is the King James Bible, the concept has a broader range of applications than just displaying Bible stories.

Im not sure why this particular idea hit when it did, nor why I choose The Bible as the "Proof of Concept" (other than it was the most readily available hiarchial structured document available in machine readable format from Project Gutenberg) but the nucleus of the idea came from three areas of hypertext/WWW research.

One idea came from Jakob Nielsons work on user interfaces for the web. The primary article that relates to mod_litbook is using the URL as UI; in that the URL should aid in the navigation of the website. The primay point of Jakob Nielsons article is that the URL should help visualize the structure of the website but I mis-remembered the article in thinking that the URL should also provide an easy way to retrieve the information requested.

Another idea came from Ted Nelsons work on Xanadu, the ultimate in hypertext vaporware (30 years and still no product). But it does have some interesting ideas, namely in tumblers. The concept of each node including all the nodes addressed below it is a powerful concept and one that I started to explore just prior to writing mod_litbook (in addition to some work a few years ago in file system design that is still in the design stage).

In playing around with the concept I found that within The Bible, there are frequent references to other passages, and that the references looked similar to the tumblers concept proposed by Ted Nelson. And upon investigation, none of the other online Bible sites I found allowed one to request an arbitrary portion of The Bible. Sure, you could get a book, or a chapter or a verse, but you couldnt get just the portion of Moses at Mount Sinai. At least, not without a lot of work.

The third idea came from Project Zope, an object publishing web server, where the URL doesnt reference a static document but instead names an object to be displayed. The fact that most website URLs point to files (or templates) is a holdover from the early days of the web and the filespace you see in a URL doesnt necessarily have to map to a physical file system, or a file at all.

Now, out of this mess of ideas came mod_litbook, an Apache module that combines an addressing structure similar to tumblers hidden behind an object publishing module using easy-to-remember URLs to retrieve just the portion of the document you want (in this case, using a conventional bible notation munged into a URL,).

Why a module? Because handling all this behing a CGI program would have made the result less elegant and primarily, the server Im using for the demo system isnt powerful enough to handle an excessive CGI overhead that this may generate. And because I could.