Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 74164 invoked from network); 10 Nov 2004 17:42:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 10 Nov 2004 17:42:10 -0000 Received: (qmail 95438 invoked by uid 500); 10 Nov 2004 17:42:09 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 95349 invoked by uid 500); 10 Nov 2004 17:42:08 -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 95335 invoked by uid 99); 10 Nov 2004 17:42:08 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from [212.23.3.140] (HELO pythagoras.zen.co.uk) (212.23.3.140) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 10 Nov 2004 09:42:05 -0800 Received: from [82.69.78.226] (helo=[192.168.0.2]) by pythagoras.zen.co.uk with esmtp (Exim 4.30) id 1CRwTn-0006eV-VF for dev@forrest.apache.org; Wed, 10 Nov 2004 17:42:00 +0000 Message-ID: <419252E7.7060501@apache.org> Date: Wed, 10 Nov 2004 17:41:59 +0000 From: Ross Gardler User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@forrest.apache.org Subject: Re: [RT] Forrest templates for second generation skining - towards Corium References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Originating-Pythagoras-IP: [82.69.78.226] X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Thorsten Scherler wrote: > Hello devs, again, ;-) > > the following mail is an aggregation and consolidation of different > mails I wrote in this ml. I added some new concepts to the topic. I really like the ideas you propose in this RT, although I admit I have not fully explored all the possibilities. However, I think we may have a use case for this functionality, see the thread Re: [RT] plugin infrastructure, in my most recent mail (sent immediately before this one) I have cross-linked to this thread. Can you take a look at it and see if your RT can solve the problem we have there. Ross