- From: Tom Cloyd <tomcloyd@bestmindhealth.com>
- Date: Wed, 28 Dec 2005 17:11:11 -0800
- To: "Amaya mailing list" <www-amaya@w3.org>
Gary, You write - > How is Amaya in a different league than NVU? > > Both are tools that serve different purposes. In Amaya you can do things > you > cannot do in NVU. In NVU you can do things you cannot do in Amaya. To say > Amaya is in a different league than NVU really is not a correct > statement. Well, it might be a correct statement if I provided some justifcation for making it! My experience with NVU was this: It radically altered the HTML in a large number of pages in my web site - WITHOUT WARNING ME IT WAS GOING TO DO THIS! It filled by source files with lines and lines of empty space. It inserted superfluous nonsensical name and id attributes in my HTML header tags when I already had usable anchors present. It produced HTML which I did NOT write, and which made Tidy roll over and die. I was appalled, and screamed long and loud on the NVU list. Not one person got it that the future of the web is standards compliant web sites - FOR THE SAKE OF PEOPLE WHO CAN BENEFIT A GREAT DEAL FROM WEB ACCESS *if* it's accessible to them. My business is helping people. This is a core value to me. I don't think much of people who code up web page simply to get them to work - for them - and couldn't care less about other people. The developers of NVU clearly are in that camp. I do not think they deserve our respect. They certainly don't have mine. They haven't done their homework and they don't understand the Internet, viewed from a big picture perspective. It took me over two days of full time work to put my web site back together, after NVu mangled it, and I'm STILL removing from my source those superfluous id and name tags. This was simple a really bad experience for me. I got involved with NVU because I desperately needed a WYSIWYG HTML editor so I could simply get on with writing in a multitude of documents I'm developing for web publishing. Writing in a text editor, or a word processor which generates HTML (MS Word - gak! OpenOFfice Write - better, but it still radically messes with my HTML) was a less than ideal solution, especially if I want the documents to be up on-site and available, while I continue to develop them. I needed something that respects my HTML, as I work only in XHTML Strict, and try hard to achieve level II accessibility (as specified by W3C). **AMAYA DOES THIS!** My productivity has increased distinctly since I've switched to AMAYA as my primary web writing tool. It's that simple. And I don't have to go "correct" my HTML after it's pass through AMAYA. Isn't this the way things SHOULD be? > I still cannot get Amaya to run stable, it keeps crashing in Windows XP. I can understand your frustration. It has, so far, crashed for me only once, but I'm not asking it to do a great deal for me. Since it's so rich in functionality, I'd expect that stability might be a real problem in certain contexts. Let's hope that the problems can be found and fixed. The developers certainly seem responsive and interested in user problems. (Something which I can promise you is NOT the case with NVu.) -- t. ================================================ Tom Cloyd, MS MA, LMHC Private practice Psychotherapist Bellingham, Washington, U.S.A: (360) 920-1226 << TC.BestMindHealth.com / BestMindHealth.com >> << tomcloyd@bestmindhealth.com >> ================================================ -- ================================================ Tom Cloyd, MS MA, LMHC Private practice Psychotherapist Bellingham, Washington, U.S.A: (360) 920-1226 << TC.BestMindHealth.com / BestMindHealth.com >> << tomcloyd@bestmindhealth.com >> ================================================
Received on Thursday, 29 December 2005 01:11:24 UTC