<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Schengili Roberts, Keith</title>	<link>http://tc.eserver.org/authors/Schengili-Roberts,_Keith</link>
	<description>A bibliography of works by Schengili Roberts, Keith in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Schengili Roberts, Keith</title>
		<link>http://tc.eserver.org/dir/Schengili-Roberts,_Keith</link>
	</image>
	<item>
		<title>Debugging JavaScript Using Venkman</title>
		<link>http://tc.eserver.org/21167.html</link>
		<guid>http://tc.eserver.org/21167.html</guid>
		<description>Most people who do even a little bit of JavaScript programming, even those who are simply tweaking somebody else’s code, are familiar with the rudimentary JavaScript debugger in the recent versions of Internet Explorer. Click on the yellow warning icon in your browser, and you get a listing of various JavaScript errors in your code. It is simple, and for many people it is enough, but it’s not really the type of fully-fledged debugging environment with features programmers have come to expect in other development languages. If you find yourself doing a lot of JavaScript programming or tweaking and you are concerned with cross-browser support for your scripts, then Venkman is worth checking out.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Schengili-Roberts,_Keith.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>