RE: coupla html+ possibilities

• Mail folder: WWW Talk Jul-Oct 1993
• Next message: Rayne Woo: "Binaries for HPs"
• Previous message: Per Hedbor: "Graphics in Xmosaic"
• Reply: Marc Andreessen: "RE: coupla html+ possibilities"
• Reply: Marc Andreessen: "RE: coupla html+ possibilities"

From: wais@ecn.purdue.edu (Chris Davis)
Message-id: <9307061642.AA27991@ups.ecn.purdue.edu>
Subject: RE: coupla html+ possibilities
To: www-talk@nxoc01.cern.ch
Date: Tue, 6 Jul 1993 11:42:26 -0500 (EST)
X-Mailer: ELM [version 2.4 PL21]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1247      
Status: RO

In Message-Id: <9307040959.AA09910@wintermute.ncsa.uiuc.edu>
Marc Andreessen writes:
> 
> (b) An optional parameter for <LI> to allow specification of a pointer
>     to an image to inline (rather than using a bullet or whatever).
>     This would let one do something like:
> 
>     <UL>
>     <LI IMG="internal-gopher-menu"> A Gopher menu.
>     <LI IMG="internal-gopher-image"> A weathermap.
>     </UL>
> 
>     ... and then one would get a slick bitmap-enumerated list.  Again,
>     text-based clients could substitute the normal list style or
>     textual equivalents (e.g., "[menu]" and "[image]").

When a link points to a gopher file, isn't the information about what type of 
data being pointed to already provided in the URL?

e.g.  gopher://ecn.purdue.edu/I9/Some_nifty_graphic 
	Is known to be a "gopher-image" because of the I9.

I would think it wouldn't be too hard for the client to display a small
bitmap instead of a bullet when it sees something like this in the link. As
soon as you move out of gopher provided information, the problem becomes very
murky, and an optional parameter like the one you suggest would probably be
just about the only way to do it without a lot of headaches.

Chris Davis -- Purdue University ECN