Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 90309 invoked from network); 4 May 2006 07:35:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 4 May 2006 07:35:28 -0000 Received: (qmail 30131 invoked by uid 500); 4 May 2006 07:35:21 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 30065 invoked by uid 500); 4 May 2006 07:35:21 -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 30023 invoked by uid 99); 4 May 2006 07:35:21 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 May 2006 00:35:21 -0700 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, 04 May 2006 00:35:20 -0700 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 k447Ytp18763 for ; Thu, 4 May 2006 09:34:55 +0200 (MET DST) 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 M2006050409345514716 for ; Thu, 04 May 2006 09:34:55 +0200 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 k447YrFf005444 for ; Thu, 4 May 2006 09:34:53 +0200 Message-ID: <4459AF45.4090909@pcotech.fr> Date: Thu, 04 May 2006 09:37:41 +0200 From: Cyriaque Dupoirieux User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: dev@forrest.apache.org Subject: Re: status of skins and dispatcher for 0.8 release References: <20060502050911.GB2100@igg.indexgeo.com.au> <44578DC1.705@apache.org> <1146596582.8354.41.camel@localhost.localdomain> <4457B4DB.7090106@apache.org> <1146609941.8354.73.camel@localhost.localdomain> <20060504043628.GF16193@igg.indexgeo.com.au> <4459A7FD.10901@apache.org> In-Reply-To: <4459A7FD.10901@apache.org> Content-Type: text/plain; charset=ISO-8859-1; 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 le 04/05/2006 09:06 Ross Gardler a �crit : > David Crossley wrote: >> Thorsten Scherler wrote: >> > [SNIP] > Nice overlap with Ferdinands proposal for a clear development > proposal. Lets use this as a test case. I'll be proposing the Daisy > plugin too once I have enough time to document it a little better. We > can use both the Daisy and the Dispatcher/themer plugins as test cases. > > One thing that will have to happen before the Dispatcher comes out of > core is to resolve the plugin dependency issues. > > Some time ago we agreed that plugins should not have any dependencies > on one another. We also acknowledged that here may come a time in > which such a dependency is required. This may be it, but the plugin > architecture does not currently support dependencies. We need to > create the concept of "features" which are collections of plugins that > work together to achieve a specific goal. I think we need to specify the concept of "feature" for plugins and the notion of plugin dependency of "features". Try to explain : * Plugin A implement the Feature 1 * Plugin B also implement the feature 1 * Plugin C depends on the feature 1 For instance, Plugin C is the dispatcher and Plugins A and B two implementations of the core.theme So what ? Projects can select their implementations : If a project specifies project.required.plugins=C, A, it's OK, If a project specifies project.required.plugins=C, B, it's OK too - but with a different behaviour or rendering, Salutations, Cyriaque, > > We can return to this after the 0.8 release though. > > Ross > >