From dev-return-13607-apmail-forrest-dev-archive=forrest.apache.org@forrest.apache.org Sun Nov 07 22:25:46 2004 Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 14725 invoked from network); 7 Nov 2004 22:25:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 7 Nov 2004 22:25:46 -0000 Received: (qmail 68969 invoked by uid 500); 7 Nov 2004 22:25:45 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 68932 invoked by uid 500); 7 Nov 2004 22:25: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 Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 68920 invoked by uid 99); 7 Nov 2004 22:25:44 -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 [68.230.241.32] (HELO fed1rmmtao07.cox.net) (68.230.241.32) by apache.org (qpsmtpd/0.28) with ESMTP; Sun, 07 Nov 2004 14:25:43 -0800 Received: from [192.168.0.3] (really [68.109.82.172]) by fed1rmmtao07.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20041107222541.IHCR3261.fed1rmmtao07.cox.net@[192.168.0.3]> for ; Sun, 7 Nov 2004 17:25:41 -0500 Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: References: <4188E497.4080803@apache.org> <418BB394.3090909@apache.org> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Clay Leeds Subject: Re: [RT] plugin infrastructure Date: Sun, 7 Nov 2004 14:24:38 -0800 To: dev@forrest.apache.org X-Mailer: Apple Mail (2.619) X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Here's a little question... On Nov 7, 2004, at 2:09 PM, Nicola Ken Barozzi wrote: >>>>> - sitemap.xmap - this provides the infrastructure matchers (i.e. >>>>> site.xml, faq.xml, issues.xml), as such it will be mounted before >>>>> *any* of the Forrest matches. This sitemap can override any >>>>> behaviour within Forrest) >>>>> >>>>> - source.xmap - this provides the source matchers (i.e. **.xml), >>>>> it is mounted in forrest.xmap before the default forrest **.xml >>>>> behaviour and therefore can override that default behaviour but it >>>>> will not interfere with any internal Forrest infrastructure >>>>> matches, or any other plugins infrastructure matches. >>>>> >>>>> - output.xmap - this provides (surprise!) the output matchers >>>>> (i.e. **.html, **.pdf, **.slides), it is mounted before any of the >>>>> default matchers for Forrest and so can override this default >>>>> behaviour Does it make sense to call them: - input.xmap (instead of source.xmap) - output.xmap? That way, it's immediately clear what's happening. Otherwise, a newbie may not 'get it'... (I hope this isn't like asking if they can make the Panama Canal a 'few feet wider'? ;-)) Web Maestro Clay -- Clay Leeds - Webmaster/Developer - Medata, Inc. - PGP Public Key: