<br><br><div class="gmail_quote">On Tue, Apr 13, 2010 at 8:19 PM, Nevin Pratt <span dir="ltr"><<a href="mailto:nevin@bountifulbaby.com">nevin@bountifulbaby.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000"><div class="im">
<br>
<blockquote type="cite">
<div class="gmail_quote"><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I hope there's another solution, other than external style sheets,
because as I peruse my 44 #style methods in my package, I rediscover
that I need to dynamically calculate some widths and heights, so in
some cases I need to implement styles based on individual instances.<br>
<br>
Do people ever combine external style sheets and #style methods?<br>
<br>
<br>
</blockquote>
<br>
</div>
I realize the down-side of not having external style sheets, but having
*everything* in the Smalltalk environment sure is a hard-to-resist and
very sweet siren song of convenience. Putting everything in the image
gives you refactoring ability, plus a whole bunch more.<br>
<br>
But it also means having *no* external style sheets-- instead leaving
you with having *all* of your style info inside the Smalltalk image.<br>
<br>
And, it's a siren song I find myself succumbing to more and more. So,
yes, some people do in fact combine external style sheets and #style
methods. :-)<br>
<br>
And, yes, doing so does have a down-side.<br>
</blockquote>
<div><br>
But really, a few lines in a WAFileLibrary method isn't truly an
"external" style sheet and not much of a down side is it? Does it use
that much server resources? Won't the client agent cache the bits?
Seems a lot less cumbersome than all that Apache stuff. <br>
<br>
Still the calculated measurements might require a kludge. Perhaps a
calculated class would do the trick if the calculation results in a
discrete and small number of outcomes.<br>
<br>
John<br>
</div>
</div>
</blockquote>
<br></div>
Why even do that, then?<br>
<br>
It depends on who you want to have the ability to modify a CSS style:
(1) a graphic artist, or (2) a Smalltalk programmer.<br>
<br>
If the answer to that question is that it is fine having it be the
Smalltalk programmer who modifies the CSS (which, in effect, this
decision also defines much of what the downside is), I personally think
the #style methods are the most convenient, and nothing else is really
even needed.<br>
<br>
Nevin<br>
<br></div></blockquote><div> </div><div>I agree although if you're as terrible at css as I am, hunting through methods to change pixel counts and the like can be arduous, so having all the CSS in one spot is a bit more convenient.<br>
<br>But in Sigrid's case the inline CSS isn't working because the client isn't updating according to the formatting returned with the Ajax response. Those styles need to be in the head section beforehand, so either WAFileLibrary or external files are required. <br>
John<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div bgcolor="#ffffff" text="#000000">
</div>
<br>_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><a href="http://jmck.seasidehosting.st">http://jmck.seasidehosting.st</a><br>