Exactly my motivation for building it was:
1) Make the canvas API more approachable for developers who know html -
"what's the Seaside equivalent for <xxxx> </xxxx>"
2) Ease the designer -> developer workflow.
3) Eliminate one of the arguments against using Seaside from developers who
are used to template based frameworks.
There's a presentation I gave in Barcelona, at last year's ESUG -
http://www.slideshare.net/nickager/seafox - it's a little out of date and
focuses on the firefox plug-in rather than the online translator, but
provides some background.
Nick
Oh cool, and thanks for the info. I think that I like the online translator best!
T.
Ted Wrinch
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Locked
