Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 61853 invoked from network); 16 Apr 2005 20:47:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 16 Apr 2005 20:47:11 -0000 Received: (qmail 43270 invoked by uid 500); 16 Apr 2005 20:47:10 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 43213 invoked by uid 500); 16 Apr 2005 20:47:09 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 43200 invoked by uid 99); 16 Apr 2005 20:47:09 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=FORGED_RCVD_HELO X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from natnoddy.rzone.de (HELO natnoddy.rzone.de) (81.169.145.166) by apache.org (qpsmtpd/0.28) with ESMTP; Sat, 16 Apr 2005 13:47:08 -0700 Received: from 192.168.2.3 ([80.26.243.203]) by post.webmailer.de (8.13.1/8.13.1) with ESMTP id j3GKl3eJ026000; Sat, 16 Apr 2005 22:47:04 +0200 (MEST) Subject: Re: using view/viewHelper From: Thorsten Scherler To: Diwaker Gupta Cc: forrest dev In-Reply-To: <1b0b455705041613052a290663@mail.gmail.com> References: <1b0b455705041516337cbea147@mail.gmail.com> <1113618257.10841.0.camel@localhost.localdomain> <1b0b4557050415215353a3cdc@mail.gmail.com> <1113659515.8860.9.camel@localhost.localdomain> <1b0b455705041613052a290663@mail.gmail.com> Content-Type: text/plain Date: Sat, 16 Apr 2005 22:47:02 +0200 Message-Id: <1113684422.8860.27.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I will have to go right now, but a quick response on that. On Sat, 2005-04-16 at 13:05 -0700, Diwaker Gupta wrote: > I was looking at nav-main.ft, and found that the background images in > the CSS were using URLs of the form '/skin/images/xxxx.gif' -- this > assumes that the deployed forrest site is deployed a domain whose top > level contains a skin directory. That is, this will NOT work if my > website is deployed at say http://foo.com/bar/home because /skin will > (wrongly) try to resolve to http://foo.com/skin > Yeah, you are right. Actually it was a workaround that I still need to fix. > A simple solution is to use relative URLs. URLs in CSS are resolved > relative to the location of the CSS file, not the HTML file. And since > all the images reside in skin/images after deployment, simply changing > /skin/images/xxx.gif to images/xxx.gif solves the problem. > Hmm, that is not that easy. It need a {$root}images/xxx.gif because images/xxx.gif will only work for top level dirs and not subdirs. > I would also like to suggest that we convert all GIFs to PNGs -- GIFs > has patent problems, and PNG is a better format anyways. > Knock yourself out. ;-) I just took the scale-dev package. I will apply all enhancement bugs on css, but this time I will not develop the css because I am not a web designer and it takes me hours to do. ;-) Thanks again for your suggestions. salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)