added www dir to hold the website

This commit is contained in:
david 2001-09-30 17:17:15 +00:00
parent a0d3129cb3
commit 24825c308f
2 changed files with 107 additions and 1 deletions

View File

@ -23,7 +23,7 @@ TARFILE="scrollserver-$VERSION.tar"
BZFILE="$TARFILE.bz2"
echo "Creating $BZFILE" # Do not include CVS, pub or temp dirs
tar -cf $TARFILE scrollserver --exclude=CVS --exclude=pub --exclude=temp
tar -cf $TARFILE scrollserver --exclude=CVS --exclude=pub --exclude=temp --exclude=www
if [ -f scrollserver/$PACKAGEDIR/$BZFILE ]
then

View File

@ -0,0 +1,106 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE>ScrollServer</TITLE>
</HEAD>
<BODY>
<h1>ScrollServer</h1>
<h2>Latest Release</h2>
The latest release is version 0.5, which offers several improvements. It is
architecturally cleaner than 0.4 and uses css stylesheets for a much more
attractive appearance. There is a dependency I'm still trying to figure out. If
you encounter a bug please let me know as it will help me figure it out.
<p>
See CHANGELOG for the nitty gritty.
<h2>What is ScrollServer?</h2>
ScrollServer is a <a href="http://www.python.org">Python</a> based http server
that provides access to a <a href="http://scrollkeeper.sourceforge.net">ScrollKeeper</a>
database with any web browser. You can use ScrollServer
to browse and search help files that are installed in the ScrollKeeper
database on your computer. Someday you will also be able to view online
ScrollServer databases.
<p>
ScrollServer is a young project that is still in early development, so many
features are not yet implemented. You should find it usable but incomplete.
<p>
Please report bugs and request features by filing them on SourceForge, or
by writing to the author at
<a href="mailto:david@lupercalia.net">david@lupercalia.net</a>.
<h2>SourceForge Site</h2>
You can download the latest release and post bug reports on the
<a href="http://sourceforge.net/projects/scrollserver">SourceForge Page</a>.
<h2>CVS</h2>
I'm not using the SourceForge CVS. ScrollServer is hosted in the
<a href="http://www.linuxdoc.org/LDP/LDP-Author-Guide/cvs.html">Linux
Documentation Project CVS</a>.
<h2>Status</h2>
ScrollServer is in very early development, but it is already useful. It has
been tested on RedHat 7.1 and Debian Woody. Reports of success or failure on
other systems greatly appreciated.
<p>
I'm working towards a 1.0 release which will implement basic functionality.
<ul>
<li>It must be usable in text browsers but attractive in X.</li>
<li>It must Serve all documentation formats supported by ScrollKeeper.</li>
<li>It must provide browsing by document title or topic.</li>
</ul>
<p>
In later releases searching should be powerful but easy. It's a classic trade
off, but I'm going to try. It will probably mean writing my own DocBook-aware
search library.
<p>
There are more ambitious goals in the long term. Eventally, ScrollServers will
be able to talk to one another, and to share information with each other. One
ScrollServer will `publish' a document or five hundred, and another will
`subscribe' to the `publication'. This is mainly for the benefit of the Linux
Documentation Project and others who provide more general Linux information.
<p>
Each subscription can be left offsite or cached locally, updating the
local ScrollKeeper database. If the local ScrollServer database has a cached
copy of the document, it will be used in preference to the online copy.
<p>
Eventually a reader might be able to rate a document, and have their comments
sent to the publisher (i.e., the other ScrollServer) and also to the author of
the document, which can be extracted from the DocBook.
<p>
Sound like an interesting project?
<h2>Resources</h2>
See these sites for information about related topics.
<p><a href="http://www.ibiblio.org/osrt/omf/">The OMF specification</a><br>
<a href="http://scrollkeeper.sourceforge.net">ScrollKeeper</a><br>
<h2>Known Bugs</h2>
Gnome specific uris such as gnome-help:foo don't work. I and the gnome-doc
people are working on a solution. It may just mean work in the xsl stylesheets.
<p>
KDE documents haven't even been looked at yet.
<p>
HTML is cached, but there is no cache management.
<p>&nbsp;<p>
<b><i>
David Merrill<br>
david@lupercalia.net
</i></b>
</BODY>
</HTML>