Received: with ECARTIS (v1.0.0; list gopher); Mon, 15 Apr 2002 13:00:34 -0500 (EST) Return-Path: <sugaku@sympatico.ca> Delivered-To: gopher@complete.org Received: from tomts6-srv.bellnexxia.net (tomts6.bellnexxia.net [209.226.175.26]) by pi.glockenspiel.complete.org (Postfix) with ESMTP id 9D2963B811 for <gopher@complete.org>; Mon, 15 Apr 2002 13:00:33 -0500 (EST) Received: from [209.226.175.22] by tomts6-srv.bellnexxia.net (InterMail vM.4.01.03.23 201-229-121-123-20010418) with SMTP id <20020415180032.KIOU3414.tomts6-srv.bellnexxia.net@[209.226.175.22]> for <gopher@complete.org>; Mon, 15 Apr 2002 14:00:32 -0400 From: Ralph Furmaniak <sugaku@sympatico.ca> To: gopher@complete.org Subject: [gopher] Re: Views Date: Mon, 15 Apr 2002 14:00:32 EDT MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Message-Id: <20020415180032.KIOU3414.tomts6-srv.bellnexxia.net@[209.226.175.22]> X-archive-position: 587 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: sugaku@sympatico.ca Precedence: bulk Reply-to: gopher@complete.org List-help: <mailto:ecartis@complete.org?Subject=help> List-unsubscribe: <mailto:gopher-request@complete.org?Subject=unsubscribe> List-software: Ecartis version 1.0.0 List-ID: Gopher <gopher.complete.org> X-List-ID: Gopher <gopher.complete.org> List-subscribe: <mailto:gopher-request@complete.org?Subject=subscribe> List-owner: <mailto:jgoerzen@complete.org> List-post: <mailto:gopher@complete.org> List-archive: <http://www.complete.org/mailinglists/archives/> X-list: gopher

> Sorry, I lost the location -- where can I find info or downloads for > your fork?

I have temporarily removed the link to the download since I have basically redone it, but have not finished testing it (I could put it up, but there still might be some bugs, although it shouldn't be anything big).

I included a list of features in a previous email, and I can write up some detailed info.

> So you're saying that your buck branch handles UMN .Links/.cap files?

I included the funtionality relatively recently (even has the same command-line options) based on the man pages, but I think the man page was not to clear on a few points. I have not tested this out yet.

> I'm not quite following, can you clarify a bit (even with an example)?

Okay, on my server I have a directory pyramid.dir and in it I have: pyramid.tex pyramid.dvi pyramid.pdf Now when the server serves the parent directory, on seeing that the directory has a .dir extension it acts accordingly. For a gopher+ request it will give an item `pyramid` with the views found in the directory. For other requests it will serve it as a directory. When the directory is requested it will display a message and the list of views. I hope this is clear enough, you can see it in action at sugaku.homeunix.org

The files in the directory do not need the same base filename, since only the extension is processed.+

> Indeed. Already thought of that but have no idea how to do it :-)

Should be a bit of DHTML or javascript and layers or iframes. I have seen it before (I have a friend who does this sort of stuff) but others can probably implement the HTML better. It should not be much of a problem writing the server-side code.