Working with CSS designers
Locked
 
|
I'd like to get some ideas on how to work with css editors. How do you
work with them? What is your workflow for receiving and installing updated css stylesheets? I can think of a few ways, I'm sure there are more: 1. Give them the image and let them run the image locally. If you do this, what is their workflow updating css files and viewing content? The only way I can get css to work when running a image locally is to use FileLibrary and to change the FileLibrary methods themselves. I haven't been successful finding a way to get seaside/pier to find css files that are external. Oh.. I take that back. If I use David's method[1], I can place the css files under FileRoot and the Kom server finds them. But PNGs referenced in the css files aren't found. Don't know why. I guess the css designer would need to deliver the text of the css methods and the webmaster can install however the web server is serving the css files. 2. Fake it and don't give them anything. Let them create their own html content for testing. I assume that this is the common practice. 3. Give them access to /seaside/<application> so they can toggle the halos and place css stylesheets using the "Style Editor" halo. As with #1, I don't know where to place PNG files so that css stylesheets can actually find the PNGs. Is anybody using this method to change css? 4. others? I'd like to hear what you do, since you guys have been running seaside sites much longer than me! thanks, brad == [1] http://www.shaffer-consulting.com/david/Seaside/GettingSoftware/index.html) -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: Working with CSS designers
|
|
In our experience #2 worked best. Our designer mocks up a page in html, styles it, I reproduce the code in seaside and voila. All the styles are linked externally (linktostyle: in updateroot:) although image is able to serve the files as well to take advantage of source control as well as simplify develoment setup. In deployment the resource URL points to an outside server that has a copy of the files. I'm planning on blogging a little more about the details in the weeks leadind up to my report at smalltalk solutions too. _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
In reply to this post by Brad Fuller
> 4. others?
Get an instance of the Seaside image running on some server and provide FTP access for the style-sheets. Most of the designers use editors with FTP integration anyway. Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: Working with CSS designers
|
|
In reply to this post by Boris Popov, DeepCove Labs (SNN)
What I do is take advantage of the fact that Comanche is a full web
server. I have a htdocs directory like one would have with apache with an /images directory. I can verify the image can be served just by surfing to it as I would with apache. Then my seaside app can simply reference the resources where they are (e.g. /images/logo.png). If needed, I don't think it would be too hard to configure apache to take over the static content later, but it is nice for speed to just use Comanche while developing. Boris Popov wrote: > > In our experience #2 worked best. Our designer mocks up a page in > html, styles it, I reproduce the code in seaside and voila. All the > styles are linked externally (linktostyle: in updateroot:) although > image is able to serve the files as well to take advantage of source > control as well as simplify develoment setup. In deployment the > resource URL points to an outside server that has a copy of the files. > I'm planning on blogging a little more about the details in the weeks > leadind up to my report at smalltalk solutions too. > > Cheers! > > -Boris > (Sent from a BlackBerry) > > ----- Original Message ----- > From: [hidden email] > <[hidden email]> > To: The Squeak Enterprise Aubergines Server - general discussion. > <[hidden email]> > Sent: Sat Mar 10 20:36:50 2007 > Subject: [Seaside] Working with CSS designers > > I'd like to get some ideas on how to work with css editors. How do you > work with them? What is your workflow for receiving and installing > updated css stylesheets? I can think of a few ways, I'm sure there are > more: > > 1. Give them the image and let them run the image locally. > If you do this, what is their workflow updating css files and viewing > content? The only way I can get css to work when running a image locally > is to use FileLibrary and to change the FileLibrary methods themselves. > I haven't been successful finding a way to get seaside/pier to find css > files that are external. Oh.. I take that back. If I use David's > method[1], I can place the css files under FileRoot and the Kom server > finds them. But PNGs referenced in the css files aren't found. Don't > know why. > I guess the css designer would need to deliver the text of the css > methods and the webmaster can install however the web server is serving > the css files. > > 2. Fake it and don't give them anything. Let them create their own html > content for testing. I assume that this is the common practice. > > 3. Give them access to /seaside/<application> so they can toggle the > halos and place css stylesheets using the "Style Editor" halo. As with > #1, I don't know where to place PNG files so that css stylesheets can > actually find the PNGs. Is anybody using this method to change css? > > 4. others? > > I'd like to hear what you do, since you guys have been running seaside > sites much longer than me! > > thanks, > brad > > > == > [1] > http://www.shaffer-consulting.com/david/Seaside/GettingSoftware/index.html) > > -- > brad fuller > http://www.Sonaural.com/ > +1 (408) 799-6124 > > > _______________________________________________ > Seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > ------------------------------------------------------------------------ > > _______________________________________________ > Seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: Working with CSS designers
|
|
In reply to this post by Brad Fuller
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. _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
In reply to this post by Jason Johnson-3
Jason Johnson wrote:
> What I do is take advantage of the fact that Comanche is a full web > server. I have a htdocs directory like one would have with apache with > an /images directory. I can verify the image can be served just by > surfing to it as I would with apache. Then my seaside app can simply > reference the resources where they are (e.g. /images/logo.png). Hmmm... I can do the same thing using the way David does it[1], but I can never get any browser to render images. For instance, in Firefox, clicking on any png/jpg/gif in the directory listing results in: "The image “http://localhost:9999/path/box-bottom-right.png” cannot be displayed, because it contains errors." But, there are no errors in the graphics files. Is this a mime error with Kom? > If needed, I don't think it would be too hard to configure apache to > take over the static content later, but it is nice for speed to just use > Comanche while developing. Exactly, that's what I want to do. I have apache serving static files from directories, but I want a easy way to develop away from the live site. >> == >> [1] >> http://www.shaffer-consulting.com/david/Seaside/GettingSoftware/index.html) >> _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: Working with CSS designers
|
|
Brad Fuller wrote:
> Jason Johnson wrote: >> What I do is take advantage of the fact that Comanche is a full web >> server. I have a htdocs directory like one would have with apache >> with an /images directory. I can verify the image can be served just >> by surfing to it as I would with apache. Then my seaside app can >> simply reference the resources where they are (e.g. /images/logo.png). > > Hmmm... I can do the same thing using the way David does it[1], but I > can never get any browser to render images. For instance, in Firefox, > clicking on any png/jpg/gif in the directory listing results in: > > "The image “http://localhost:9999/path/box-bottom-right.png” cannot be > displayed, because it contains errors." > > But, there are no errors in the graphics files. Is this a mime error > with Kom? I saw this too the other day. My brother-in-law does all my graphics work and the last picture he sent me said that. But it looked funny when loaded from the file system (i.e. no web server) as well. I told him and he resaved it with his graphics program and now it works. _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
In reply to this post by Boris Popov, DeepCove Labs (SNN)
Boris Popov wrote:
> 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. what is "S3"? -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
RE: Working with CSS designers
|
|
Amazon Simple Storage Service (Amazon S3),
http://www.amazon.com/gp/browse.html?node=16427261 We use it to store all our external resources for deployment, although I'm a little disappointed they don't have data centers in EU or Asia, so latency is a bit of an issue from there. We are considering alternate hosting options that have more worldwide leaf nodes as well in the meantime. Cheers! -Boris -- +1.604.689.0322 DeepCove Labs Ltd. 4th floor 595 Howe Street Vancouver, Canada V6C 2T5 http://tinyurl.com/r7uw4 [hidden email] CONFIDENTIALITY NOTICE This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments. Thank you. > -----Original Message----- > From: [hidden email] [mailto:seaside- > [hidden email]] On Behalf Of Brad Fuller > Sent: Wednesday, March 14, 2007 11:21 AM > To: Seaside - general discussion > Subject: Re: [Seaside] Working with CSS designers > > Boris Popov wrote: > > 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. > > what is "S3"? > > -- > brad fuller > http://www.Sonaural.com/ > +1 (408) 799-6124 > > > _______________________________________________ > Seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
Boris Popov wrote:
> Amazon Simple Storage Service (Amazon S3), > > http://www.amazon.com/gp/browse.html?node=16427261 > > We use it to store all our external resources for deployment, although > I'm a little disappointed they don't have data centers in EU or Asia, so > latency is a bit of an issue from there. We are considering alternate > hosting options that have more worldwide leaf nodes as well in the > meantime. It looks nice an inexpensive. So, you run your web server one place and the data another? -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
RE: Working with CSS designers
|
|
Yes, we host our seaside application here, but all the resources it uses
live in our S3 bucket somewhere in the Amazon :) -Boris -- +1.604.689.0322 DeepCove Labs Ltd. 4th floor 595 Howe Street Vancouver, Canada V6C 2T5 http://tinyurl.com/r7uw4 [hidden email] CONFIDENTIALITY NOTICE This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments. Thank you. > -----Original Message----- > From: [hidden email] [mailto:seaside- > [hidden email]] On Behalf Of Brad Fuller > Sent: Wednesday, March 14, 2007 12:16 PM > To: Seaside - general discussion > Subject: Re: [Seaside] Working with CSS designers > > Boris Popov wrote: > > Amazon Simple Storage Service (Amazon S3), > > > > http://www.amazon.com/gp/browse.html?node=16427261 > > > > We use it to store all our external resources for deployment, > > I'm a little disappointed they don't have data centers in EU or Asia, so > > latency is a bit of an issue from there. We are considering alternate > > hosting options that have more worldwide leaf nodes as well in the > > meantime. > > It looks nice an inexpensive. So, you run your web server one place and > the data another? > > -- > brad fuller > http://www.Sonaural.com/ > +1 (408) 799-6124 > > > _______________________________________________ > Seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
Boris,
About S3, how does that work for the domain name and URL? If your application is http://www.myapp.com/ , how do you serve the images/css/js from the same domain? Or do you just point to Amazon (I assume that this is an Amazon domain name)? But then, in an https environment, doesn't that trigger a warning on the browser side? Thanks, Thierry _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
RE: Working with CSS designers
|
|
When deploying, the application gets configured with a resource URL
pointing to S3, app preferenceAt: #resourceBaseUrl put: 'https://s3.amazonaws.com/bucketname/' , self version The browser won't show a warning because resources are secure and browser trusts the CA, you'd only get a warning if you were serving non-secure resources from a secure page (note the https in the URL), Cheers! -Boris -- +1.604.689.0322 DeepCove Labs Ltd. 4th floor 595 Howe Street Vancouver, Canada V6C 2T5 http://tinyurl.com/r7uw4 [hidden email] CONFIDENTIALITY NOTICE This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments. Thank you. > -----Original Message----- > From: [hidden email] [mailto:seaside- > [hidden email]] On Behalf Of Thierry Thelliez > Sent: Monday, May 07, 2007 1:11 PM > To: Seaside - general discussion > Subject: Re: [Seaside] Working with CSS designers > > Boris, > > About S3, how does that work for the domain name and URL? If your > application is http://www.myapp.com/ , how do you serve the > images/css/js from the same domain? > > Or do you just point to Amazon (I assume that this is an Amazon domain > name)? But then, in an https environment, doesn't that trigger a > warning on the browser side? > > > Thanks, > Thierry > _______________________________________________ > Seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
| Free forum by Nabble | Edit this page |