Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 1096 invoked from network); 20 Jan 2006 12:19:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 20 Jan 2006 12:19:48 -0000 Received: (qmail 88063 invoked by uid 500); 20 Jan 2006 12:19:47 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 87733 invoked by uid 500); 20 Jan 2006 12:19:44 -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 87679 invoked by uid 99); 20 Jan 2006 12:19:43 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Jan 2006 04:19:43 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [212.23.3.142] (HELO rutherford.zen.co.uk) (212.23.3.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Jan 2006 04:17:53 -0800 Received: from [82.69.78.226] (helo=[192.168.0.2]) by rutherford.zen.co.uk with esmtp (Exim 4.34) id 1EzvCt-0005FD-Qe for dev@forrest.apache.org; Fri, 20 Jan 2006 12:17:31 +0000 Message-ID: <43D0D4D8.6090505@apache.org> Date: Fri, 20 Jan 2006 12:17:28 +0000 From: Ross Gardler User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@forrest.apache.org Subject: Re: o.a.f.themer.Coat References: <1137756304.8323.72.camel@localhost> In-Reply-To: <1137756304.8323.72.camel@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Originating-Rutherford-IP: [82.69.78.226] X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Thorsten Scherler wrote: > Hi all, > > since the last answer to Gav, where I am talking about extending themes > instead of creating new ones, I looked again in the coat theme. > > The coat theme is providing > a) one structurer - coat.fv > b) one css definition - coat.css > > For me it makes awfully lot of sense to integrate this two files into > the core themes > a) out of maintenance reasons > b) as well because the theme package providing mechanism will not be > ready for a while (since it has to be based on the final dispatcher > release) > c) it is apache stuff (a very good alternative to pelt or common) and > belongs into the core. > > wdyt? As an example of the download mechanism coat is indeed a bad example because it has no contracts or anything like that. My motivation for the theme download system is the same as being able to host plugins elsewhere, that is themes can be released under a different license if necessary, for example, there are a whole load of useful web site themes based on CSS that cannot be released under the Apache license. The second reason is that we can provide separate sample sites that show off the theme to its best advantage. If you want to move coat into the themer for the above reasons that is fine, as long as we are able to provide separate sample sites for each theme (again in the case of the coat theme, it doesn't provide any contracts so doesn't actually need a sample site yet). Ross Ross