<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3157" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face="Trebuchet MS" size=2><SPAN class=984355400-23082007>Hi
there,</SPAN></FONT></DIV>
<DIV><FONT face="Trebuchet MS" size=2><SPAN
class=984355400-23082007></SPAN></FONT> </DIV>
<DIV><FONT face="Trebuchet MS" size=2><SPAN
class=984355400-23082007> is somebody thinking about the
design principle of "make fewer http requests" of YSlow to improve Seaside
apps?</SPAN></FONT></DIV>
<DIV><FONT face="Trebuchet MS" size=2><SPAN
class=984355400-23082007></SPAN></FONT> </DIV>
<DIV><FONT face="Trebuchet MS" size=2><SPAN
class=984355400-23082007> I see that with the FileLibraries we
have a very good factorization of css but the system works better if all the css
goes in one file (that may travel better gziped). We can make this at deploy
files time. We can make use of this feature "write to disk" not to write every
selector as a separated css file but in a fashion more appropiated for
production. This should be one css file with all the styles.
Concatenating CSS selectors answers we can archieve this.</SPAN></FONT></DIV>
<DIV><FONT face="Trebuchet MS" size=2><SPAN
class=984355400-23082007></SPAN></FONT> </DIV>
<DIV><FONT face="Trebuchet MS" size=2><SPAN
class=984355400-23082007> I think that we will make that point
qualified from F to A in one shot. What do you think? </SPAN></FONT></DIV>
<DIV> </DIV>
<DIV align=left><SPAN class=250542422-20122006>
<P class=MsoNormal style="MARGIN: 0cm 0cm 0pt" align=left><?xml:namespace prefix
= st1 ns = "urn:schemas-microsoft-com:office:smarttags" /><st1:PersonName
ProductID="Sebastian Sastre " w:st="on"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Trebuchet MS'">Sebastian
Sastre<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office"
/><o:p></o:p></SPAN></st1:PersonName></P></DIV></SPAN>
<DIV> </DIV></BODY></HTML>