<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for MeshCAM Blog</title>
	<atom:link href="http://www.grzsoftware.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.grzsoftware.com/blog</link>
	<description></description>
	<lastBuildDate>Fri, 12 Aug 2011 12:57:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>Comment on MeshCAM V5 Preview Release by Gerry</title>
		<link>http://www.grzsoftware.com/blog/releases/meshcam-v5-preview-release/#comment-8783</link>
		<dc:creator>Gerry</dc:creator>
		<pubDate>Fri, 12 Aug 2011 12:57:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.grzsoftware.com/blog/?p=726#comment-8783</guid>
		<description>I prefer standard help files myself. Much quicker to use than pdf and html.</description>
		<content:encoded><![CDATA[<p>I prefer standard help files myself. Much quicker to use than pdf and html.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on MeshCAM V5 Preview Release by Robert</title>
		<link>http://www.grzsoftware.com/blog/releases/meshcam-v5-preview-release/#comment-8781</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Thu, 11 Aug 2011 20:34:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.grzsoftware.com/blog/?p=726#comment-8781</guid>
		<description>Thanks for the feedback Ted.  wxWidgets is the UI library I use and, as you pointed out, it&#039;s not that configurable without re-implementing a lot of it with the new features in mind.  

I do like the idea of the help with CTRL pressed so I&#039;ll have to think about that and see if I have a reasonable way to emulate that.</description>
		<content:encoded><![CDATA[<p>Thanks for the feedback Ted.  wxWidgets is the UI library I use and, as you pointed out, it&#8217;s not that configurable without re-implementing a lot of it with the new features in mind.  </p>
<p>I do like the idea of the help with CTRL pressed so I&#8217;ll have to think about that and see if I have a reasonable way to emulate that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on MeshCAM V5 Preview Release by Ted Milker</title>
		<link>http://www.grzsoftware.com/blog/releases/meshcam-v5-preview-release/#comment-8779</link>
		<dc:creator>Ted Milker</dc:creator>
		<pubDate>Thu, 11 Aug 2011 20:13:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.grzsoftware.com/blog/?p=726#comment-8779</guid>
		<description>One thing that I really like about ZBrush(3D high-poly modeling software, if you are not familiar) as a software is that all of the help for every tool is integrated straight into the interface.  I can hold Control over any menu or tool and get a detailed explanation of what that tool is or what the menu item is going to do.  You may not be able to facilitate this everywhere since you are using Windows dialogs and not a completely custom UI like ZBrush but you could take a page from it.

MeshCam is pretty user-friendly, you may as well extend that to the help too.  Integrate it as tooltips that pop up to explain something and push the feature on new users when they first start it.  If I hover over the image or checkbox for Waterline, it should give a decent description.  If I hover over &quot;Stepover&quot; it gives me a brief description of what that is.  Creating new tools could really use this helping users get started adding their own tools, especially since MeshCam does not come with any presets.

I would recommend not using HTML files.  They are not really searchable except page-by-page(or hacky solutions that break a lot) which is frustrating.  PDFs are fine when the page count is low but incremental searching by a word or phrase gets tedious as the file gets longer, especially if it is a commonly used word.  Make sure to have a solid table of contents for a PDF and a matching set of bookmarks so it can be accessed at any location in the PDF.  CHMs are a pretty nice balance, even if they are not OS friendly and take a bit of work to get a nice and useful set of documentation.

CHMs are definitely not that great to edit.  You could always switch to a wiki(even if only you and people you choose can edit it) if you prefer Wordpress.  Just make sure you populate it before you switch and provide an offline snapshot or something with releases.  The worst is when someone switches to a wiki and has not populated it with very much and expects the info to just pop out of nowhere.

I was just thinking as I was reading your blog posts that they would make great additions to the help files too.</description>
		<content:encoded><![CDATA[<p>One thing that I really like about ZBrush(3D high-poly modeling software, if you are not familiar) as a software is that all of the help for every tool is integrated straight into the interface.  I can hold Control over any menu or tool and get a detailed explanation of what that tool is or what the menu item is going to do.  You may not be able to facilitate this everywhere since you are using Windows dialogs and not a completely custom UI like ZBrush but you could take a page from it.</p>
<p>MeshCam is pretty user-friendly, you may as well extend that to the help too.  Integrate it as tooltips that pop up to explain something and push the feature on new users when they first start it.  If I hover over the image or checkbox for Waterline, it should give a decent description.  If I hover over &#8220;Stepover&#8221; it gives me a brief description of what that is.  Creating new tools could really use this helping users get started adding their own tools, especially since MeshCam does not come with any presets.</p>
<p>I would recommend not using HTML files.  They are not really searchable except page-by-page(or hacky solutions that break a lot) which is frustrating.  PDFs are fine when the page count is low but incremental searching by a word or phrase gets tedious as the file gets longer, especially if it is a commonly used word.  Make sure to have a solid table of contents for a PDF and a matching set of bookmarks so it can be accessed at any location in the PDF.  CHMs are a pretty nice balance, even if they are not OS friendly and take a bit of work to get a nice and useful set of documentation.</p>
<p>CHMs are definitely not that great to edit.  You could always switch to a wiki(even if only you and people you choose can edit it) if you prefer WordPress.  Just make sure you populate it before you switch and provide an offline snapshot or something with releases.  The worst is when someone switches to a wiki and has not populated it with very much and expects the info to just pop out of nowhere.</p>
<p>I was just thinking as I was reading your blog posts that they would make great additions to the help files too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on MeshCAM V5 Preview Release by Robert</title>
		<link>http://www.grzsoftware.com/blog/releases/meshcam-v5-preview-release/#comment-8778</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Thu, 11 Aug 2011 20:05:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.grzsoftware.com/blog/?p=726#comment-8778</guid>
		<description>Good call- changing it now.

-Robert</description>
		<content:encoded><![CDATA[<p>Good call- changing it now.</p>
<p>-Robert</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on MeshCAM V5 Preview Release by Randy</title>
		<link>http://www.grzsoftware.com/blog/releases/meshcam-v5-preview-release/#comment-8777</link>
		<dc:creator>Randy</dc:creator>
		<pubDate>Thu, 11 Aug 2011 18:45:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.grzsoftware.com/blog/?p=726#comment-8777</guid>
		<description>Robert, I&#039;ve been playing with the toolpath wizard some, and I think it&#039;s very good.  I like the &quot;you should use a flat endmill&quot; reminders for 2.5D tool choosing.  I&#039;d suggest having the wizard enable &quot;Don&#039;t machine top of stock&quot; by default for 2.5D jobs.  I had to check that manually.

Randy</description>
		<content:encoded><![CDATA[<p>Robert, I&#8217;ve been playing with the toolpath wizard some, and I think it&#8217;s very good.  I like the &#8220;you should use a flat endmill&#8221; reminders for 2.5D tool choosing.  I&#8217;d suggest having the wizard enable &#8220;Don&#8217;t machine top of stock&#8221; by default for 2.5D jobs.  I had to check that manually.</p>
<p>Randy</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on MeshCAM V5 Preview Release by Robert</title>
		<link>http://www.grzsoftware.com/blog/releases/meshcam-v5-preview-release/#comment-8776</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Thu, 11 Aug 2011 18:06:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.grzsoftware.com/blog/?p=726#comment-8776</guid>
		<description>I agree completely Ted- the manual will get a rewrite to become more of a guide rather than just a dry set of definitions.  That&#039;s part of the reason that the blog has started to get more &quot;How-Tos&quot;.  My plan is to publish the content here and then edit it into the manual after I get feedback.  For some reason, writing content in Wordpress is easier for me that writing it in my help file editor.

I am debating the format of the help file in the future.  Should it remain as a Windows help file, or should it become HTML or PDF.  Any thoughts?

-Robert</description>
		<content:encoded><![CDATA[<p>I agree completely Ted- the manual will get a rewrite to become more of a guide rather than just a dry set of definitions.  That&#8217;s part of the reason that the blog has started to get more &#8220;How-Tos&#8221;.  My plan is to publish the content here and then edit it into the manual after I get feedback.  For some reason, writing content in WordPress is easier for me that writing it in my help file editor.</p>
<p>I am debating the format of the help file in the future.  Should it remain as a Windows help file, or should it become HTML or PDF.  Any thoughts?</p>
<p>-Robert</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on MeshCAM V5 Preview Release by Ted Milker</title>
		<link>http://www.grzsoftware.com/blog/releases/meshcam-v5-preview-release/#comment-8775</link>
		<dc:creator>Ted Milker</dc:creator>
		<pubDate>Thu, 11 Aug 2011 17:43:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.grzsoftware.com/blog/?p=726#comment-8775</guid>
		<description>It would help new people if you updated the help files to explain what &quot;Pencil&quot;, &quot;Waterline&quot; and &quot;Parallel Finishing&quot; and other things are along with everything else in the primary workflow path(Generate Toolpaths, Tool setup screens).  You explain their options but you do not give a description of what it is going to do.

As a new trial user, I found the help file pretty much a brief sketch of the menus and windows.  The Getting Started video was more helpful in some cases.</description>
		<content:encoded><![CDATA[<p>It would help new people if you updated the help files to explain what &#8220;Pencil&#8221;, &#8220;Waterline&#8221; and &#8220;Parallel Finishing&#8221; and other things are along with everything else in the primary workflow path(Generate Toolpaths, Tool setup screens).  You explain their options but you do not give a description of what it is going to do.</p>
<p>As a new trial user, I found the help file pretty much a brief sketch of the menus and windows.  The Getting Started video was more helpful in some cases.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on MeshCAM V5 Preview Release by Randy</title>
		<link>http://www.grzsoftware.com/blog/releases/meshcam-v5-preview-release/#comment-8768</link>
		<dc:creator>Randy</dc:creator>
		<pubDate>Tue, 09 Aug 2011 20:58:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.grzsoftware.com/blog/?p=726#comment-8768</guid>
		<description>Cool, thanks Robert.  That&#039;ll be great.

Randy</description>
		<content:encoded><![CDATA[<p>Cool, thanks Robert.  That&#8217;ll be great.</p>
<p>Randy</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on MeshCAM V5 Preview Release by Robert</title>
		<link>http://www.grzsoftware.com/blog/releases/meshcam-v5-preview-release/#comment-8767</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Tue, 09 Aug 2011 17:24:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.grzsoftware.com/blog/?p=726#comment-8767</guid>
		<description>It will be changing back to a text-based format in the near future so that will absolutely be possible.

-Robert</description>
		<content:encoded><![CDATA[<p>It will be changing back to a text-based format in the near future so that will absolutely be possible.</p>
<p>-Robert</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on MeshCAM V5 Preview Release by Randy</title>
		<link>http://www.grzsoftware.com/blog/releases/meshcam-v5-preview-release/#comment-8766</link>
		<dc:creator>Randy</dc:creator>
		<pubDate>Tue, 09 Aug 2011 17:15:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.grzsoftware.com/blog/?p=726#comment-8766</guid>
		<description>I&#039;d really appreciate the ability to maintain the tool table. Since it isn&#039;t something a comma-delimited text file any more, I&#039;m not even able to do something simple like sort the tools by number.  And the only way to access the table seems to be to set up a dummy job, go to the tool picker and look at the existing table that way.  Either a stand-alone utility or a menu item in MeshCAM to bring up and edit the table would be great.  I need to keep my tool tables coordinated between MeshCAM, SheetCam and Mach3.  If I change a tool in one I need to update it in the other two also.

Randy</description>
		<content:encoded><![CDATA[<p>I&#8217;d really appreciate the ability to maintain the tool table. Since it isn&#8217;t something a comma-delimited text file any more, I&#8217;m not even able to do something simple like sort the tools by number.  And the only way to access the table seems to be to set up a dummy job, go to the tool picker and look at the existing table that way.  Either a stand-alone utility or a menu item in MeshCAM to bring up and edit the table would be great.  I need to keep my tool tables coordinated between MeshCAM, SheetCam and Mach3.  If I change a tool in one I need to update it in the other two also.</p>
<p>Randy</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Served from: grzsoftware.com @ 2012-02-04 04:30:09 by W3 Total Cache -->
