<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>Re: [Seaside] CSS Files vs. #style</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Mostly because I never let seaside serve static resources in production but rather detach them from the image for deployment and use apache or s3. I wrote a custom solution for this early on, but I believe FileLibrary will do that for you now. Also, our designer doesn't use the application a whole lot, but rather works with either a new page he writes and styles from scratch, or more commonly now saves the generated one to use as a starting point for improvement. That let's him use the tools he's comfortable with as far as html and css editing goes, as very often code needs to change together with css to achieve certain things, new images added, changed, removed etc.. I will then take the updated styles plus resources, load them up, implement required html changes and voila! Embedded css editing maybe was useful before firebug came out as it let you change css on the fly, but let's face it, firebug does circles around the thing now :)<BR>
<BR>
Cheers!<BR>
<BR>
-Boris<BR>
(Sent from a BlackBerry)<BR>
<BR>
----- Original Message -----<BR>
From: seaside-bounces@lists.squeakfoundation.org <seaside-bounces@lists.squeakfoundation.org><BR>
To: seaside@lists.squeakfoundation.org <seaside@lists.squeakfoundation.org><BR>
Sent: Sat May 05 18:14:08 2007<BR>
Subject: [Seaside] CSS Files vs. #style<BR>
<BR>
I've read previous posts (by Avi as well as others) saying that they<BR>
typically didn't implement the method #style on a component, but instead<BR>
typically used #updateRoot: and #resourceUrl: to invoke external CSS<BR>
files. For example, Philippe Marschall wrote the following example of<BR>
use (on 7/27/06):<BR>
<BR>
MyRootComponent >> #updateRoot: anHtmlRoot<BR>
super updateRoot: anHtmlRoot.<BR>
anHtmlRoot linkToStyle: 'wherever/style.css'.<BR>
anHtmlRoot linkToScript: 'wherever/script.js'.<BR>
<BR>
And, of course, this works fine, and presumably allows your web<BR>
designers to easily change the CSS layout.<BR>
<BR>
But then, so did the #style method. And, it also is easy for your web<BR>
designers to change the CSS layout-- by toggling the halos and entering<BR>
the CSS code in the browser (via the style editor, which is the little<BR>
pencil icon when you turn halos on). And, when they do it this way, it<BR>
compiles the CSS code into the #style method of the component, thus<BR>
allowing you to carry the styles around with your image. And that<BR>
reduces dependencies, because it keeps everything in the image, instead<BR>
of splitting it out into external files.<BR>
<BR>
So, why are folks avoiding the #style method? What am I missing?<BR>
<BR>
Nevin<BR>
<BR>
_______________________________________________<BR>
Seaside mailing list<BR>
Seaside@lists.squeakfoundation.org<BR>
<A HREF="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</A><BR>
</FONT>
</P>
</BODY>
</HTML>