Re: Concerns about HTML+ complexity

Dan Hinckley <hinckley@netcom.com>

Mail folder: WWW Talk Apr 94-present
Next message: Terrence M. McLaren: "Mosaic v2.0alpha5 Release"
Previous message: Steve Hiebert: "Re: Concerns about HTML+ complexity (example)"
Maybe in reply to: Ken Fox: "Re: Concerns about HTML+ complexity"
Reply: Brian Behlendorf: "Re: Concerns about HTML+ complexity"

Errors-To: listmaster@www0.cern.ch
Date: Fri, 17 Jun 1994 23:54:17 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <Pine.3.89.9406171454.A12899-0100000@netcom8>
Errors-To: listmaster@www0.cern.ch
Reply-To: hinckley@netcom.com
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: Dan Hinckley <hinckley@netcom.com>
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: Concerns about HTML+ complexity
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mime-Version: 1.0
Mime-Version: 1.0



Dan Hinckley                  The EarthWeb Project
Executive Director             voice: 303.642.7330
204 Divide View Drive            fax: 303.642.7330
Golden, CO 80403         email:hinckley@netcom.com

On Fri, 17 Jun 1994, Brian Behlendorf wrote:

I'd appreciate some ideas on how you think this might be implemented.
> 
> As food for thought, let me throw this in:  if I could tell the art people
> here that they could Quark Xpress files seamlessly into HTML files (sans
> hyperlinking of course) because everyone out there has a free plug-in
> provided by Quark that does the rendering into every Web browser (and if
> people don't have it they can get it from our site anyways), they'd do
> backflips. 
> 
> Build a strong, portable, efficient API, and encourage ALL vendors to
> build plug-ins to the API for their products.  Then HTML++... won't have
> to try and become a page description language, it can stay light and easy
> to use as the lingua franca. 
> 
> 	Brian
>