<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Examining The Doctor</title>
	<link>http://devdawn.com/2006/08/15/examining-the-doctor-2/</link>
	<description></description>
	<pubDate>Fri, 29 Aug 2008 20:38:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Stu</title>
		<link>http://devdawn.com/2006/08/15/examining-the-doctor-2/#comment-3083</link>
		<dc:creator>Stu</dc:creator>
		<pubDate>Mon, 28 Aug 2006 23:01:42 +0000</pubDate>
		<guid>http://devdawn.com/2006/08/15/examining-the-doctor-2/#comment-3083</guid>
		<description>Yes. I hadn't considered this. I guess this review was written from a "New To Help Authoring" perspective.

Also, I believe you could run it in conjunction with the larger help authoring software. I'm not convinced it is the total solution. What it does, it does very very well. But a product like &lt;a href="http://www.ec-software.com/" rel="nofollow"&gt;Help &#038; Manual&lt;/a&gt; covers a far broader range of functionality.

And Dr. Explain doesn't have to look at getting all that functionality. I'd like to see just a few things added that would go a long way. The ability to add images to any page. The ability to get right in and wysiwyg edit any page. And some of the functionality you are talking about, importing from existing HTML (or other base data files).

Now that I'm thinking it through again, the memory is coming back :). In my opinion it's gonna rock for small to medium software projects. They need to have an edge. What's to stop a company buying Help &#038; Manual for a few hundred dollars? 

Dr. Explain has less functionality, but it's more fully featured in the functionality it does have. 

Dr. Explain is $125 (US). Help &#038; Manual (Standard) is $299 and (Professional) is $459. While this price difference isn't massive, it's still enough for smaller companies to go with Dr. Explain.

The big selling point is the differences. Where the divergence of the product occurs. And this is with (I believe) the SnagIt-like interface for capturing a window and bullet-pointing it. 

Anyway, nuff said for the moment.

I'll email Dennis and see if we can't get a list of what's on the horizon for Dr. Explain.</description>
		<content:encoded><![CDATA[<p>Yes. I hadn&#8217;t considered this. I guess this review was written from a &#8220;New To Help Authoring&#8221; perspective.</p>
<p>Also, I believe you could run it in conjunction with the larger help authoring software. I&#8217;m not convinced it is the total solution. What it does, it does very very well. But a product like <a href="http://www.ec-software.com/" rel="nofollow">Help &#038; Manual</a> covers a far broader range of functionality.</p>
<p>And Dr. Explain doesn&#8217;t have to look at getting all that functionality. I&#8217;d like to see just a few things added that would go a long way. The ability to add images to any page. The ability to get right in and wysiwyg edit any page. And some of the functionality you are talking about, importing from existing HTML (or other base data files).</p>
<p>Now that I&#8217;m thinking it through again, the memory is coming back :). In my opinion it&#8217;s gonna rock for small to medium software projects. They need to have an edge. What&#8217;s to stop a company buying Help &#038; Manual for a few hundred dollars? </p>
<p>Dr. Explain has less functionality, but it&#8217;s more fully featured in the functionality it does have. </p>
<p>Dr. Explain is $125 (US). Help &#038; Manual (Standard) is $299 and (Professional) is $459. While this price difference isn&#8217;t massive, it&#8217;s still enough for smaller companies to go with Dr. Explain.</p>
<p>The big selling point is the differences. Where the divergence of the product occurs. And this is with (I believe) the SnagIt-like interface for capturing a window and bullet-pointing it. </p>
<p>Anyway, nuff said for the moment.</p>
<p>I&#8217;ll email Dennis and see if we can&#8217;t get a list of what&#8217;s on the horizon for Dr. Explain.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dana Cline</title>
		<link>http://devdawn.com/2006/08/15/examining-the-doctor-2/#comment-3081</link>
		<dc:creator>Dana Cline</dc:creator>
		<pubDate>Mon, 28 Aug 2006 19:07:44 +0000</pubDate>
		<guid>http://devdawn.com/2006/08/15/examining-the-doctor-2/#comment-3081</guid>
		<description>One other feature it needs, if it doesn't already have it, is the ability to import someone's help project, say, as a set of HTML files. If there's no way to move from your existing tool, then this program is fairly useless to most help authors...</description>
		<content:encoded><![CDATA[<p>One other feature it needs, if it doesn&#8217;t already have it, is the ability to import someone&#8217;s help project, say, as a set of HTML files. If there&#8217;s no way to move from your existing tool, then this program is fairly useless to most help authors&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
