From owner-freebsd-small Mon Oct 5 15:32:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18261 for freebsd-small-outgoing; Mon, 5 Oct 1998 15:32:53 -0700 (PDT) (envelope-from owner-freebsd-small@FreeBSD.ORG) Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18239 for ; Mon, 5 Oct 1998 15:32:48 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from diabolique ([195.121.59.34]) by smtp01.wxs.nl (Netscape Messaging Server 3.6) with SMTP id AAB4241; Tue, 6 Oct 1998 00:32:45 +0200 Message-Id: X-Sender: skywise@pop.wxs.nl X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Demo Date: Tue, 06 Oct 1998 00:31:03 +0200 To: "Andrew Hannam" From: Jeroen Ruigrok/Asmodai Subject: RE: WWW i/f Cc: "FreeBSDSmall" , "Andrzej Bialecki" In-Reply-To: <000501bdf069$12346d60$0104010a@andrewh.famzon.com.au> References: <000401bdf065$da48a900$0104010a@andrewh.famzon.com.au> Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 At 16:04 05-10-98 , Andrew Hannam wrote: >[Opinion] >WWW is just another GUI, although a cheap one from the server point of view. >Like all GUI's you can design good and bad applications. The point with html >is that by nature you tend to end up with bad interfaces unless you do the >design work first. True, well, ye can try some designs already, except the point is that when ye are going to go for HTML 1.0, 2.x, 3.x, or 4,x compliance, the HTTPd code gets enlarged by a factor 2 or something due to extra functionality. The question we should ask is do we need every option available? Are there tags available that might be benificial to the configuration? Another lame question that's evading my eyes is, how are we going to write the config? Does a simple POST do the trick? >Who these days has time to do anything other than a quick and dirty >implementation? Only the marketing people who see it like any other form of >trend marketing. This explains the many bad interfaces we see. >They are either bad from being "quick and dirty" or bad from being too >glossy with limited functionality. Any familiarity with 3Com's Hubs and Switches? They have a nice WWW interface and useable too... >Point is... > design an interface properly in html and it should be as good as any other >GUI implementation. Care to disagree, I find CLI's too be much more enjoyable and better to manipulate... WWW might be better in layout of data and their current settings. Matter of preference? >The same applies to command lines. If you design badly you get a bad result >(hence the comments earlier in this group about how bad Cisco IOS is. >Command line completion does a lot to "rescue" the useability of Cisco IOS). What's so wrong about IOS? I still don't see it. Hence I suggested the completion too, Andrej might have had the opinion voiced on the list at some earlier time too, but I haven't found that though =) regards, Jeroen Ruigrok van der Werven / Asmodai ICQ-UIN: 1564317 .:. Ninth Circle Enterprises Network/Security Specialist /==|| FreeBSD and picoBSD, the Power to Serve ||==\ -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 6.0 for non-commercial use iQA/AwUBNhk6mIY752GnxADpEQJP4wCfRzpPwsgvS2FxRgoM5riPrVP3lcMAoIvh lvZegpfjj3+pQRXQdo00t4g1 =PpVR -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message