[Seaside] canvas translator & new version of Seafox
ljw1001 at gmail.com
Wed Sep 14 23:30:37 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:[...
Does this make sense (and does it seem useful)?
On Wed, Sep 14, 2011 at 5:31 PM, Nick Ager <nick.ager at gmail.com> wrote:
> Hi Larry,
> Seafox is fantastic, but is it possible to output the seaside markup using
>> the original css selectors rather than generating new css classes? It would
>> make it easier to work with an outside designer.
> I've added a checkbox beneath the edit box, which allows you to disable
> style -> class transformation.
> I originally added the style -> class transformation as I noticed that in
> Safari and Chrome, the browser attempts to maintain the style of page by
> adding style attributes to the elements which often makes the translation
> difficult to read. Firefox doesn't appear suffer from this issue.
> Hope this helps
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside