<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div><div><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Exactly my motivation for building it was:<br>1) Make the canvas API more approachable for developers who know html -<br>"what's the Seaside equivalent for <xxxx> </xxxx>"<br>2) Ease the designer -> developer workflow.<br>3) Eliminate one of the arguments against using Seaside from developers who<br>are used to template based frameworks.<br><br>There's a presentation I gave in Barcelona, at last year's ESUG -<br><a href="http://www.slideshare.net/nickager/seafox">http://www.slideshare.net/nickager/seafox</a><span class="Apple-converted-space"> </span>- it's a little out of date and<br>focuses on the firefox plug-in rather than the online translator, but<br>provides some background.<br><br>Nick</span></blockquote></div><br></div><div>Oh cool, and thanks for the info. I think that I like the online translator best!</div><div><br></div><div>T.</div><div><br></div><div>Ted Wrinch</div></body></html>