<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Using 280Slides (Ajax slideshow maker): Real World Experiences</title>
	<atom:link href="http://softwareas.com/using-280slides-ajax-slideshow-maker-real-world-experiences/feed" rel="self" type="application/rss+xml" />
	<link>http://softwareas.com/using-280slides-ajax-slideshow-maker-real-world-experiences</link>
	<description>Mahemoff's Podcast/Blog - Web, Programming, Usability from the Author of 'Ajax Design Patterns' (AjaxPatterns.org)</description>
	<lastBuildDate>Sat, 24 Jul 2010 21:06:54 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: mahemoff</title>
		<link>http://softwareas.com/using-280slides-ajax-slideshow-maker-real-world-experiences/comment-page-1#comment-311937</link>
		<dc:creator>mahemoff</dc:creator>
		<pubDate>Fri, 15 Aug 2008 09:01:59 +0000</pubDate>
		<guid isPermaLink="false">http://softwareas.com/?p=474#comment-311937</guid>
		<description>&lt;p&gt;Ross,&lt;/p&gt;

&lt;p&gt;Thanks very much for your comments and +5 for actually making some changes already!!!&lt;/p&gt;

&lt;p&gt;With auto-save, one thing you could do is show time since last save (or till next save). It would take a little screen space and require a timer, but I thought some kind of feedback like that is worth it to help the user understand the saving model. Alternatively, an auto-save checkbox.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Ross,</p>

<p>Thanks very much for your comments and +5 for actually making some changes already!!!</p>

<p>With auto-save, one thing you could do is show time since last save (or till next save). It would take a little screen space and require a timer, but I thought some kind of feedback like that is worth it to help the user understand the saving model. Alternatively, an auto-save checkbox.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Ross Boucher</title>
		<link>http://softwareas.com/using-280slides-ajax-slideshow-maker-real-world-experiences/comment-page-1#comment-311643</link>
		<dc:creator>Ross Boucher</dc:creator>
		<pubDate>Fri, 15 Aug 2008 01:36:48 +0000</pubDate>
		<guid isPermaLink="false">http://softwareas.com/?p=474#comment-311643</guid>
		<description>&lt;p&gt;Thanks for writing about us!&lt;/p&gt;

&lt;p&gt;The cut and paste issue is a complicated one.  Unfortunately, you can&#039;t really copy and paste from your own button in a universal way.  Our copy/paste works by intercepting the browser&#039;s  native copy and paste events, which only fire when you use the command-c, command-v keyboard shortcuts (or ctrl for windows).  &lt;/p&gt;

&lt;p&gt;I did fix the paste placement issue.  Pasted objects are now offset from each other at regular intervals.&lt;/p&gt;

&lt;p&gt;I also changed our text selection color to match the native selection color, and added in a bit of transparency in browsers that support it.&lt;/p&gt;

&lt;p&gt;As for auto-save, we do in fact have it.  It turns out that autosaving is a challenging UI problem.  You want it to be transparent to the user, and yet be available when its needed.  The way our autosave works is designed to do exactly that.  &lt;/p&gt;

&lt;p&gt;You&#039;ll never know autosave is doings its thing unless the application crashes on you.  If that happens, when you try to open a saved document, we&#039;ll notice that you have a newer autosaved version, and prompt you to open that instead (there&#039;s also a warning indicator on the file in the open panel).  &lt;/p&gt;

&lt;p&gt;Essentially, doing it this way makes autosave a recovery tool, not a replacement for regular saving.  The manual save when you want to &quot;check in&quot; the state of your document model is well established, and something people are comfortable with.  Although this isn&#039;t necessarily the last word on the topic, I think our autosave mechanism achieves a reasonable balance.&lt;/p&gt;

&lt;p&gt;With respect to undo, we&#039;ve made more things undoable with our latest release. Now, so far as I can tell, the only action that cannot be undone is changing the color of something.  This is because when you choose colors via the color wheel, we register 100s of undos, which becomes a pain very quickly.  We&#039;re working on a solution to this, but I do not know when it will be available.&lt;/p&gt;

&lt;p&gt;Everything else is great feedback, and we&#039;ll be looking into it all in the future.  Thanks again for writing, and keep in touch as you continue to use 280 Slides!  &lt;/p&gt;

&lt;p&gt;By the way, you may want to check out our latest feature: Import.  Now you can import your existing PPT, PPTX, and ODP documents.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Thanks for writing about us!</p>

<p>The cut and paste issue is a complicated one.  Unfortunately, you can&#8217;t really copy and paste from your own button in a universal way.  Our copy/paste works by intercepting the browser&#8217;s  native copy and paste events, which only fire when you use the command-c, command-v keyboard shortcuts (or ctrl for windows).  </p>

<p>I did fix the paste placement issue.  Pasted objects are now offset from each other at regular intervals.</p>

<p>I also changed our text selection color to match the native selection color, and added in a bit of transparency in browsers that support it.</p>

<p>As for auto-save, we do in fact have it.  It turns out that autosaving is a challenging UI problem.  You want it to be transparent to the user, and yet be available when its needed.  The way our autosave works is designed to do exactly that.  </p>

<p>You&#8217;ll never know autosave is doings its thing unless the application crashes on you.  If that happens, when you try to open a saved document, we&#8217;ll notice that you have a newer autosaved version, and prompt you to open that instead (there&#8217;s also a warning indicator on the file in the open panel).  </p>

<p>Essentially, doing it this way makes autosave a recovery tool, not a replacement for regular saving.  The manual save when you want to &#8220;check in&#8221; the state of your document model is well established, and something people are comfortable with.  Although this isn&#8217;t necessarily the last word on the topic, I think our autosave mechanism achieves a reasonable balance.</p>

<p>With respect to undo, we&#8217;ve made more things undoable with our latest release. Now, so far as I can tell, the only action that cannot be undone is changing the color of something.  This is because when you choose colors via the color wheel, we register 100s of undos, which becomes a pain very quickly.  We&#8217;re working on a solution to this, but I do not know when it will be available.</p>

<p>Everything else is great feedback, and we&#8217;ll be looking into it all in the future.  Thanks again for writing, and keep in touch as you continue to use 280 Slides!  </p>

<p>By the way, you may want to check out our latest feature: Import.  Now you can import your existing PPT, PPTX, and ODP documents.</p>]]></content:encoded>
	</item>
</channel>
</rss>
