Re: Renamed: Amaya as browser, not editor

In-reply-to: Your message of Fri, 02 Oct 1998 03:33:15 +0200."

> > The notion that "everybody can be a publisher" is fundamental to the Web
> > and has been there from day one: Tim Berners-Lee's first NextStep browser
> > was also a GUI editor. I agree with you that Web apps should be fast but
> > what we can show with the latest Amaya is that by using an optimized HTTP
> > protocol stack, editors don't have to be slow nor do they have to break
> > the "browsing" mode of users.
> >
> > Henrik Frystyk Nielsen, W3C
> 
> I agree with your approach, and really support you guys at the W3C in
> this regard.
> 
> But my point was really the following:
> By trying to be both a browser and editor, Amaya has not succeeded yet
> in being either.

Amaya is mainly an editor. We think that a good editor needs to be also a
browser, because the management of links and the publishing are important parts
of the editing task and they can be well done only if the editor integrates 
browsing 
facilities.
The goal of the W3C and the Amaya team is not to build a product (we don't 
have the
task force to do that), but to push some important ideas. Mixing of editing 
and browsing
is one of them. Another is to avoid people to have to learn HTML, but this can 
be true
only when authoring tools will produce good HTML code.
It seems that you don't like that approach, and you prefer to edit freely the
HTML source. That's OK today for computer scientists but not for many people. 
I agree with you that Amaya has to make progress, we are working on it, but 
you have
to accept to learn a minimum about it to discover that some features should be 
developed
(links management, multi-views, management of map areas, XML support)

Regards
  Irene.

Received on Tuesday, 6 October 1998 03:26:49 UTC