HistView 0.1.8

Takes an ASCII changelog as input and outputs a formatted HTML page.

  Add it to your Download Basket!

 Add it to your Watch List!


Rate it!

What's new in HistView 0.1.6:

  • This version brings some major improvements, making the Download Class much more powerful: it now can ignore or reject bots and crawlers, it no longer "stops" on failed database activities (download counter update), and you even can completely disable these statistic functions.
  • Moreover, all the classes now use a central central configuration to make their use easier.
Read full changelog
send us
an update
GPL (GNU General Public License) 
3.0/5 20
ROOT \ Documentation
HistView is an application that takes an ASCII changelog as input and outputs a formatted HTML page.

When developing some piece of software, one usually records its development history in an ASCII file, preceding all changes with a "hint" of the kind of change - such as an "+" for a new addition, or a "!" for a bug fix. After a while, one decides to release the package. And a while later the question arises, how to present the latest changes to users who wish to see the list of changes first to decide whether it's worth to update. At this moment, one can just place the plain text file somewhere accessible on the net - but wouldn't it look smarter to have it formatted as a nice HTML document? If you would like this, but don't want to waste time rewriting the history in HTML, HistView ist for you: it just reads in the history file, and formats it in HTML. Provided you use a style similiar to what I do.


· PHP 4


As shipped, the configuration usually is such that the files would be installed as follows:

Executables go to /usr/local/bin
Configuration files go to /etc
Documentation goes to /usr/local/share/doc/

For web apps, the installation goes to /usr/local/share/, and this
directory will be linked to /var/www/ - if this directory/file/link does not yet exist.

If you want to install to a different location, you may change some variables at the top of the Makefile. Usually, these are:

prefix=/usr/local Path for the executables is derived from this
datarootdir=$(prefix)/share Path for webapps and documentation uses this
sysconfdir=/etc Path for configuration files
WEBROOT=/var/www Just for webapps: Where to create a link

You may as well check the other settings, but these three are the most important for you. You could also override these on the command line, e.g. with "make prefix=/opt install" - but I don't recommend that if you want to run a "make uninstall" later, since you may forget what options you used on the


Once the configuration is done, installation is as easy as invoking

make install

from within the directory where the Makefile resides. As mentioned above, you also can override some configuration options here:

make prefix=/opt install

for example. But keep in mind that you need to remember these settings for the case you want to uninstall later.


is pretty much alike the install process. From the directory where the Makefile resides, simply invoke:

make uninstall

or, if you were overriding some options when calling "make install", you need to specify the same here:

make prefix=/opt uninstall

The uninstall process will remove everything it has installed - but nothing that you created yourself later (usually; if you e.g. added a file to the documentation directory in /usr/local/share/doc/< packagename >, this will be removed as well since we remove the entire directory. You are not expected to do modifications here) using this application, as e.g. template files, or "personal" configuration files you created in your home directory.

Last updated on October 14th, 2009

#ASCII changelog #ASCII to HTML #ASCII converter #ASCII #HTML #changelog #converter

Add your review!