ALPHA RELEASE: dancer WWW client

Steven Miale (smiale@cs.indiana.edu)
Wed, 27 Jul 1994 01:13:36 -0500

I've been working on a WWW client, and have an alpha version ready (it's
fairly stable, but has some bugs and some features have yet to be implemented.)
It requires tkinter to run.

It can be FTP'ed from ftp.cs.indiana.edu:/pub/smiale/dancer.tar.gz

>From the README:

Design philosophy
-----------------

Dancer was meant to be modularized, unlike Mosaic. Looking at 'dancer' gives
you some idea of what this means. There are two types of modules that can
be loaded: agents, which retrieve URLs, and viewers, which display or process
them.

For instance,

import basicurl

loads in the file 'agents/basicurl.py'. You are not forced to use this; you
could write your own if you thought it would be better or faster. The same
goes for the viewers:

import audio
import pict
import mpeg
import postscript
import whtml

Each module is only required to register itself with the dispatcher module;
it must tell it what kind of data it is looking for. For example,
'viewers/audio.py' consists of:

import posix
from dispatcher import *

def Play(url, name, (file, header)):
posix.system('/usr/openwin/bin/audiotool ' + file + ' &')

RegisterExtension('au', Play)
RegisterContentType('audio/basic', Play)

The last two lines register the MIME-style content type (when retrieving
files via HTTP) and the extension (when the content type is unavailable.)
Anything with a content type of "audio/basic" or an extension of "au" is
sent to Play. The callback takes the unfiltered URL, the filtered name
(originally the URL, but can be modified by modules which filter the data
rather than display it, like an uncompress module), and a tuple consisting
of the filename and the header (an RFC822 object; see rfc822.py).

-- 
Steven Miale [smiale@cs.indiana.edu] HTTP://cs.indiana.edu/hyplan/smiale.html