<?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 on: Bookmark widget &#8211; Now with EXE support ;o)</title>
	<atom:link href="http://www.cpguru.com/2009/08/04/bookmark-widget-now-with-exe-support-o/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cpguru.com/2009/08/04/bookmark-widget-now-with-exe-support-o/</link>
	<description>Widgets, tutorials and more for Adobe Captivate</description>
	<lastBuildDate>Fri, 20 Jan 2012 13:25:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: admin</title>
		<link>http://www.cpguru.com/2009/08/04/bookmark-widget-now-with-exe-support-o/comment-page-1/#comment-4813</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Mon, 10 Aug 2009 16:22:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.captivate4.com/?p=721#comment-4813</guid>
		<description>Yes I fully agree. I actually got it working now, but I will redo it. I made the input boxes in Flash, which was the quickest way to do it. However, I decided to use a different approach for Captivate 4 and use a Text Entry Box and a userdefined variable. That way the designer will have much more control on where and how the user should enter their name/email/employee number or whatever. 

Should have everything ready in a couple of days.

/Michael</description>
		<content:encoded><![CDATA[<p>Yes I fully agree. I actually got it working now, but I will redo it. I made the input boxes in Flash, which was the quickest way to do it. However, I decided to use a different approach for Captivate 4 and use a Text Entry Box and a userdefined variable. That way the designer will have much more control on where and how the user should enter their name/email/employee number or whatever. </p>
<p>Should have everything ready in a couple of days.</p>
<p>/Michael</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: yuripeixoto</title>
		<link>http://www.cpguru.com/2009/08/04/bookmark-widget-now-with-exe-support-o/comment-page-1/#comment-4805</link>
		<dc:creator>yuripeixoto</dc:creator>
		<pubDate>Mon, 10 Aug 2009 14:59:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.captivate4.com/?p=721#comment-4805</guid>
		<description>Good to know about this. The bookmark widget working with individual bookmarks will be a must!</description>
		<content:encoded><![CDATA[<p>Good to know about this. The bookmark widget working with individual bookmarks will be a must!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Captivate Bookmark Widget &#124; Captivate 4</title>
		<link>http://www.cpguru.com/2009/08/04/bookmark-widget-now-with-exe-support-o/comment-page-1/#comment-4501</link>
		<dc:creator>Captivate Bookmark Widget &#124; Captivate 4</dc:creator>
		<pubDate>Tue, 04 Aug 2009 18:34:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.captivate4.com/?p=721#comment-4501</guid>
		<description>[...] The component has been updated on August 4th, 2009 to fix a bug where page 1 was stored as a bookmark. A new component has also been added in the download package so it is now possible to use the Bookmark Component with EXE projects published from Captivate 4. For more information read this post: http://www.captivate4.com/2009/08/04/bookmark-widget-now-with-exe-support-o/ [...]</description>
		<content:encoded><![CDATA[<p>[...] The component has been updated on August 4th, 2009 to fix a bug where page 1 was stored as a bookmark. A new component has also been added in the download package so it is now possible to use the Bookmark Component with EXE projects published from Captivate 4. For more information read this post: <a href="http://www.captivate4.com/2009/08/04/bookmark-widget-now-with-exe-support-o/" rel="nofollow">http://www.captivate4.com/2009/08/04/bookmark-widget-now-with-exe-support-o/</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

