<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Boxes and Arrows: Comments by Isaac Csandl</title>
    <link>http://www.boxesandarrows.com/person/16926</link>
    <pubDate>Sun, 08 Jun 2008 23:45:46 GMT</pubDate>
    <description>Comments by Isaac Csandl</description>
    <item>
      <description>&lt;p&gt;I don&amp;#8217;t get why you&amp;#8217;d go to all this trouble to prototype in anything other than &lt;span class="caps"&gt;HTML&lt;/span&gt;+CSS (with the help of a good JavaScript library like Dojo or Scriptaculous). I guess if you know Flash and &lt;span class="caps"&gt;NOT&lt;/span&gt; JavaScript it might make sense because it&amp;#8217;s a tool you know better. But otherwise, why not prototype and get a good chunk of the actual work done at the same time? If you prototype in the medium that the app is ultimately going to use, then you just have to integrate the real backend with your prototypes and refine things some more in the process and presto, you&amp;#8217;ve eliminated tons of redundant/unnecessary work.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/quick-and-easy-flash#content_22244</link>
      <guid>http://www.boxesandarrows.com/view/quick-and-easy-flash#content_22244</guid>
      <pubDate>Sun, 08 Jun 2008 23:45:46 GMT</pubDate>
      <author>Isaac Csandl</author>
    </item>
    <item>
      <description>&lt;p&gt;Oh, and if you&amp;#8217;re writing standards-complaint (X)HTML from get-go, you&amp;#8217;re going to save a good bit of time when it comes to browser testing and accessibility too.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/quick-and-easy-flash#content_22245</link>
      <guid>http://www.boxesandarrows.com/view/quick-and-easy-flash#content_22245</guid>
      <pubDate>Sun, 08 Jun 2008 23:48:07 GMT</pubDate>
      <author>Isaac Csandl</author>
    </item>
  </channel>
</rss>

