From dev-return-23089-apmail-forrest-dev-archive=forrest.apache.org@forrest.apache.org Thu Mar 16 10:56:48 2006 Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 61550 invoked from network); 16 Mar 2006 10:56:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 16 Mar 2006 10:56:46 -0000 Received: (qmail 85564 invoked by uid 500); 16 Mar 2006 10:56:44 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 85397 invoked by uid 500); 16 Mar 2006 10:56:43 -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 List-Id: Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 85386 invoked by uid 99); 16 Mar 2006 10:56:43 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Mar 2006 02:56:43 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [81.80.68.197] (HELO daikiri.pcotech.fr) (81.80.68.197) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Mar 2006 02:56:42 -0800 Received: from macadam.pcotech.fr (macadam.pcotech.fr [192.168.108.3]) by daikiri.pcotech.fr (8.11.6/Aquarel-5.5.8) with SMTP id k2GAuJN04939 for ; Thu, 16 Mar 2006 11:56:19 +0100 (MET) X-Url: http://www.pcotech.fr Received: from b52.pcotech.fr ([192.168.101.124]) by macadam.pcotech.fr (SMSSMTP 4.1.0.19) with SMTP id M2006031611561811292 for ; Thu, 16 Mar 2006 11:56:18 +0100 Received: from [192.168.106.27] (dhcp-tlse-27.pcotech.fr [192.168.106.27]) by b52.pcotech.fr (8.12.8/8.12.8) with ESMTP id k2GAuIV4007286 for ; Thu, 16 Mar 2006 11:56:18 +0100 Message-ID: <44194498.9000503@pcotech.fr> Date: Thu, 16 Mar 2006 11:57:28 +0100 From: Cyriaque Dupoirieux User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: dev@forrest.apache.org Subject: Re: [branding-theme-profiler contract] References: <4416A7AB.7000809@pcotech.fr> <1142413541.8275.5.camel@localhost> <1142458424.8309.49.camel@localhost> In-Reply-To: <1142458424.8309.49.camel@localhost> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Thorsten Scherler a écrit : > Can you try, should work now. > > Ok, it works better, but I think the contract should be updated because some colors are not taken into account. I think we have two improvements to do : * first I tried to call custo.dispatcher.css in order to have a unique customised css instead of getRequest.dispatcher.css (which generates in my case several times the same file exactly) o This does not work, the custo.dispatcher.css is empty (but it's what I was expected ;-) ) * Second, the {getRequest}.dispatcher.css overrides what the pelt.css already defines. o With the skins, we had a stylesheet which generated a unique file with possibly default values... Salutations, Cyriaque, > salu2 > > El mié, 15-03-2006 a las 10:05 +0100, Thorsten Scherler escribió: > >> El mar, 14-03-2006 a las 12:23 +0100, Cyriaque Dupoirieux escribió: >> >>> Hi, >>> >>> I have tried the branding-theme-profiler contract and just change >>> the header color to 123456. >>> This value doesn't appear anywhere in the generated files ? >>> >>> Does anyone succeed to make it work ? >>> >> I tried last night and it did not work, but I think I found the >> *problems*. ;) >> >> Will apply the fix this night (need a final test). >> >> >>> (Or do I create a FOR... :-P ) >>> >> Yes, please, the issue is deeper then I thought. Please open an issue >> that we can link the fix with the issue. >> >> >>> Salutations, >>> Cyriaque, >>> >> Thanks for the report, Cyriaque. :) >> >> salu2 >>