-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, Jun 10, 2003 at 02:10:45AM -0400, lists1 wrote: > It works heavily toward w3c standard compliant code (and if you look at the > top 100 sites, I doubt 10% of them are 100% standards compliant, and if you > have 100% standards compliant, you'll be excluding over 90% of the browser > users on the internet).
No you wouldn't, because all the browsers out can decently render a 100% compliant page. I've yet to find a browser that can't. > I read a while back that Amaya development/updating wasn't very > rapid. It supports the current standard. People who make the complaint that it doesn't get rapid development don't realize that people don't mess with a UI that just works. It kind of reminds me of the old Windows program HoTMetaL. > If you haven't worked in a production environment with a wysiwyg editor, you > can't appreciate the type of rapid development that you can do with such an > editor. Yes it screws up the code. And fixing the code under frontpage was > a nightmare, but it was still faster than hand editing. Unless you have macros. - -- .''`. Baloo Ursidae <[EMAIL PROTECTED]> : :' : proud Debian admin and user `. `'` `- Debian - when you have better things to do than fix a system -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+5ZnfJ5vLSqVpK2kRAlBrAJ40xsH5Kq5NL0ilqCp/2lkxfsvPagCdGhqM DueLhBaZ+Oxy3Aec1owpN+k= =GEpu -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
