Complete.Org: Mailing Lists: Archives: gopher: August 2003:
[gopher] Re: PyGopherd 2.0 released; Gopher and WAP

[gopher] Re: PyGopherd 2.0 released; Gopher and WAP

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: PyGopherd 2.0 released; Gopher and WAP
From: MJ Ray <markj@xxxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 28 Aug 2003 15:37:04 +0100
Reply-to: gopher@xxxxxxxxxxxx

On 2003-08-28 15:14:52 +0100 PapaLazarus <papalazarus@xxxxxxx> wrote:
> A pictures worth a thousand words, well maps & diagrams.

I agree entirely, but nothing prevents a mobile gopher client 
displaying (or more likely storing for later display, in my case) 
images.  I expect such images would be more relevant to the task than 
95% of web images.  It also helps navigation speed to have a 
consistent user interface, such as gopher menus, and not to have to 
process dense markup.  I think gopher probably will come out ahead on 
access speed for most tasks usually done on mobiles, from combining 
lots of reasons.  As has been said, there's quite a few similar 
solutions in WAP interfaces as gopher ones.

MJR/slef   My Opinion Only and possibly not of any group I know.

[Prev in Thread] Current Thread [Next in Thread]