Message-ID: <3C45D06E.74FB8A34@sympatico.ca>
Date: Wed, 16 Jan 2002 14:11:42 -0500
From: Ralph Furmaniak <sugaku@sympatico.ca>
MIME-Version: 1.0
To: gopher@complete.org
Subject: [gopher] Re: Gopher thoughts
References: <3C4493E0.D60E4C67@sympatico.ca> <87sn96qpn9.fsf@complete.org>
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


> Personally, I think we need a gopherd written in Python, and I aim to
> do that one of these days.  (Really!)

In that case, would anyone mind a Lisp or Fortran server?  While we're at it,
lets just write bytecode!

> > left with a well organized page (anyone who has used Lynx on standard
> > web pages may attest to how disorganized the flow becomes upon removal
> > of tables and other such things).
>
> I need to review Gopher+ some more and see just how extensible we can
> make it.  It may be possible to add some gopher+ attributes.

Here is a way I just thought of which does not add things to the protocols,
and still works for Gopher0.  Basically you can group items together by
indentation (like in almost every piece of source code), so adding 2 spaces to
the beginning of consecutive lines groups these together (hence you can easily
get subgroups).  More specifically, you can have an (optional) blank line,
followed by an info line that becomes the heading for that group, followed by
some indented menus.  Standard clients will show some indented groups, while
more advanced clients can recognize this and do some fun stuff.  This could
also fix some of the problems with current (Mozilla, Konqueror) tree
presentations by having info lines, followed by one tree for the group,
instead of just putting everything together and/or dropping the info lines
(from what I've seen).

    Ralph Furmaniak