<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div style="word-wrap:break-word">This could help ease the acceptance of Seaside in some commercial environments as it should make it easier to add html from designers' files into Seaside html code. In the absence of a tool like this it might appear that template file technologies, like <a href="http://ASP.Net" target="_blank">ASP.Net</a> and RoR, provide a much more natural way to do this. </div>
</blockquote><div><br></div><div>Exactly my motivation for building it was:</div><div>1) Make the canvas API more approachable for developers who know html - "what's the Seaside equivalent for <xxxx> </xxxx>"</div>
<div>2) Ease the designer -> developer workflow.</div><div>3) Eliminate one of the arguments against using Seaside from developers who are used to template based frameworks.</div><div><br></div><div>There's a presentation I gave in Barcelona, at last year's ESUG - <a href="http://www.slideshare.net/nickager/seafox">http://www.slideshare.net/nickager/seafox</a> - it's a little out of date and focuses on the firefox plug-in rather than the online translator, but provides some background.</div>
<div><br></div><div>Nick</div><div><br></div><div><br></div><div><br></div><div><br></div></div>