Date: Sat, 13 Aug 2005 11:24:28 -0500
From: brian@pongonova.net
To: gopher@complete.org
Subject: [gopher] Re: basic newb info
Message-ID: <20050813162428.GB9956@pongonova.net>
References: <afb85cb40507111446382e89e9@mail.gmail.com>
 <42FCEC9D.5040201@route-add.net> <20050813044356.GH8640@pongonova.net>
 <20050813151309.GB16199@katherina.lan.complete.org>
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050813151309.GB16199@katherina.lan.complete.org>
User-Agent: Mutt/1.5.5.1i
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

On Sat, Aug 13, 2005 at 10:13:09AM -0500, John Goerzen wrote:
> Well, what exactly do you want to see?  IMHO, one of the best ways to
> see what can be done is to look at what is done out there.

I'd like to see some side-by-side comparisons of Gopher pages and the
"source" used to generate it.  Sort of like some PHP sites, where you
can click a link and view the actual PHP.

A wiki sounds interesting...actually, that sounds like an interesting
project:  Modify a wiki which will parse a gopher page.  That way,
editing the page will display the actual source.

Hmm...if anyone's interested, I might just try to tackle that later in
the fall after school is underway.  pmwiki sounds like a good
candidate, it's in Perl and I believe there's a Perl gopher module
(plus, the creator of pmwiki, Patrick Michaud, is local to me and
might be persuaded to provide some pointers!).

  --Brian