I agree with Jon.  And hardware acceleration is in tension with the generality of the extreme generality of formulating images as general (computable) functions on space (and hence arbitrary non-linear transformations, etc).
<br><br>*Unless*, you abandon the traditional acceleration of a fixed set of 2D (or 3D) primitives and transformations and instead compile into graphics processor code as in <a href="http://conal.net/Vertigo">http://conal.net/Vertigo
</a>.<br><br>BTW, I&#39;d love to find one or more enthusiastic collaborators to help create and release open-source, cross-platform, and successors to Pan &amp; Vertigo.&nbsp; Anyone interested?<br><br>&nbsp; - Conal<br><br><div><span class="gmail_quote">
On 8/7/07, <b class="gmail_sendername">Jon Harrop</b> &lt;<a href="mailto:jon@ffconsultancy.com">jon@ffconsultancy.com</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Tuesday 07 August 2007 21:22:00 Frank Buss wrote:<br>&gt; I assume to make it fast, a good idea would be to cache some calculations...<br><br>If you want to make it fast you should be using hardware acceleration.<br><br>
--<br>Dr Jon D Harrop, Flying Frog Consultancy Ltd.<br>OCaml for Scientists<br><a href="http://www.ffconsultancy.com/products/ocaml_for_scientists/?e">http://www.ffconsultancy.com/products/ocaml_for_scientists/?e</a><br>_______________________________________________
<br>Haskell-Cafe mailing list<br><a href="mailto:Haskell-Cafe@haskell.org">Haskell-Cafe@haskell.org</a><br><a href="http://www.haskell.org/mailman/listinfo/haskell-cafe">http://www.haskell.org/mailman/listinfo/haskell-cafe
</a><br></blockquote></div><br>