[Seaside] canvas translator & new version of Seafox
nick.ager at gmail.com
Thu Sep 15 08:39:34 UTC 2011
This is also very nice, but what I think people working with a designer need
> is something that translates the html literally to seaside markup, but
> doesn't do anything with the stylesheets.
> Lets say my designer gives me foo.html that will be part of a seaside
> application. He also gives me a foo.css file that handles the layout. What
> I need is seaside markup that includes the original css classes in line, so
> that I can re-use the css file that he gave me. Otherwise, if he gives me
> another page tomorrow with the same css sheet, I'll end up with at totally
> new set of derived classes, making it very hard to maintain the stylesheets.
> This may be easier than what you've done since you can ignore the css
> almost entirely, and just convert, say <div class='foo-form'/>... to html
> div class: 'foo-form' with:[...
The canvas translator  uses a rich-text editor  to capture html
content. The way the content is pasted into the editor is out of my control
and is at the whim of the OS/browser vendor. The translator simply works
with what's been pasted in. Safari and Chrome add extra style information
when you paste. Firefox doesn't produce the extra style information you see
with Safari or Chrome. For you workflow try:
1) Open the html from your designer in Firefox, open another tab containing
the canvas translator, copy from your designer's page and paste into the
2) open your designer's html page in a *text editor*, open the canvas
translator in any browser, click to the "html source" tab in the translator.
Copy from the text editor and paste into the "html source" tab. Click on the
"Seaside canvas" to see the translation into Seaside canvas methods.
3) Down the Seafox Firefox extension. Open your designer's html page in
Firefox. With Seafox installed, the bottom right-hand-side of the browser
frame should contain a Seaside star. Click on the star and the page will be
converted into Seaside canvas methods.
For you workflow, I think 2) or 3) would be the most suitable.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside