<!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] Working with CSS designers</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>That's pretty much what I had here, image stores all resources and knows how to serve them via /css /i /js, but apache defined these 3 aliases straight to the file system with a copy of the files in deployed environment. In the past week I moved everything to S3 as an experiment and so far it worked out great.<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 - general discussion <seaside@lists.squeakfoundation.org><BR>
Sent: Sun Mar 11 11:34:43 2007<BR>
Subject: Re: [Seaside] Working with CSS designers<BR>
<BR>
What I do is take advantage of the fact that Comanche is a full web<BR>
server. I have a htdocs directory like one would have with apache with<BR>
an /images directory. I can verify the image can be served just by<BR>
surfing to it as I would with apache. Then my seaside app can simply<BR>
reference the resources where they are (e.g. /images/logo.png).<BR>
<BR>
If needed, I don't think it would be too hard to configure apache to<BR>
take over the static content later, but it is nice for speed to just use<BR>
Comanche while developing.<BR>
<BR>
Boris Popov wrote:<BR>
><BR>
> In our experience #2 worked best. Our designer mocks up a page in<BR>
> html, styles it, I reproduce the code in seaside and voila. All the<BR>
> styles are linked externally (linktostyle: in updateroot:) although<BR>
> image is able to serve the files as well to take advantage of source<BR>
> control as well as simplify develoment setup. In deployment the<BR>
> resource URL points to an outside server that has a copy of the files.<BR>
> I'm planning on blogging a little more about the details in the weeks<BR>
> leadind up to my report at smalltalk solutions too.<BR>
><BR>
> Cheers!<BR>
><BR>
> -Boris<BR>
> (Sent from a BlackBerry)<BR>
><BR>
> ----- Original Message -----<BR>
> From: seaside-bounces@lists.squeakfoundation.org<BR>
> <seaside-bounces@lists.squeakfoundation.org><BR>
> To: The Squeak Enterprise Aubergines Server - general discussion.<BR>
> <seaside@lists.squeakfoundation.org><BR>
> Sent: Sat Mar 10 20:36:50 2007<BR>
> Subject: [Seaside] Working with CSS designers<BR>
><BR>
> I'd like to get some ideas on how to work with css editors. How do you<BR>
> work with them? What is your workflow for receiving and installing<BR>
> updated css stylesheets? I can think of a few ways, I'm sure there are<BR>
> more:<BR>
><BR>
> 1. Give them the image and let them run the image locally.<BR>
> If you do this, what is their workflow updating css files and viewing<BR>
> content? The only way I can get css to work when running a image locally<BR>
> is to use FileLibrary and to change the FileLibrary methods themselves.<BR>
> I haven't been successful finding a way to get seaside/pier to find css<BR>
> files that are external. Oh.. I take that back. If I use David's<BR>
> method[1], I can place the css files under FileRoot and the Kom server<BR>
> finds them. But PNGs referenced in the css files aren't found. Don't<BR>
> know why.<BR>
> I guess the css designer would need to deliver the text of the css<BR>
> methods and the webmaster can install however the web server is serving<BR>
> the css files.<BR>
><BR>
> 2. Fake it and don't give them anything. Let them create their own html<BR>
> content for testing. I assume that this is the common practice.<BR>
><BR>
> 3. Give them access to /seaside/<application> so they can toggle the<BR>
> halos and place css stylesheets using the "Style Editor" halo. As with<BR>
> #1, I don't know where to place PNG files so that css stylesheets can<BR>
> actually find the PNGs. Is anybody using this method to change css?<BR>
><BR>
> 4. others?<BR>
><BR>
> I'd like to hear what you do, since you guys have been running seaside<BR>
> sites much longer than me!<BR>
><BR>
> thanks,<BR>
> brad<BR>
><BR>
><BR>
> ==<BR>
> [1]<BR>
> <A HREF="http://www.shaffer-consulting.com/david/Seaside/GettingSoftware/index.html">http://www.shaffer-consulting.com/david/Seaside/GettingSoftware/index.html</A>)<BR>
><BR>
> --<BR>
> brad fuller<BR>
> <A HREF="http://www.Sonaural.com/">http://www.Sonaural.com/</A><BR>
> +1 (408) 799-6124<BR>
><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>
><BR>
> ------------------------------------------------------------------------<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>
> <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>