Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 24091 invoked from network); 4 Nov 2004 14:22:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 4 Nov 2004 14:22:21 -0000 Received: (qmail 27671 invoked by uid 500); 4 Nov 2004 14:22:17 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 27592 invoked by uid 500); 4 Nov 2004 14:22:16 -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 27581 invoked by uid 99); 4 Nov 2004 14:22:16 -0000 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_WHOIS,FORGED_RCVD_HELO,SPF_HELO_PASS X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from [196.25.240.78] (HELO ctb-mesg6.saix.net) (196.25.240.78) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 04 Nov 2004 06:22:14 -0800 Received: from sean.site (ndn-64-57.telkomadsl.co.za [165.165.64.57]) by ctb-mesg6.saix.net (Postfix) with ESMTP id 5F89B1608C for ; Thu, 4 Nov 2004 16:22:06 +0200 (SAST) From: Sean Wheller Reply-To: sean@inwords.co.za Organization: In Words To: dev@forrest.apache.org Subject: Re: [RT] plugin infrastructure Date: Thu, 4 Nov 2004 16:18:28 +0200 User-Agent: KMail/1.6.2 References: <4188E497.4080803@apache.org> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200411041618.28547.sean@inwords.co.za> X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Thursday 04 November 2004 15:30, Nicola Ken Barozzi wrote: > I'm thinking of the DocBook plugin and plugins that output the DocBook > as Sean has shown... so there is a dependency > > =A0 =A0DocBook_outputting_plugin-> Docbook_plugin -> Forrest > > A solution to this would be Cocoon Blocks, but they would still > need some sort of automatic resolution for us to be of use. Sorry to cut this message so short. There are lots of good ideas in it.=20 However, at the risk of sounding stupid and being totally simplistic, perha= ps=20 there is another solution. Perhaps a solution is to force some level of filesystem organization on use= rs.=20 By this I mean, that if a user has Docbook files, then they should store th= em=20 in the same folder. If a person has OO.org files they will be in another=20 folder. This means that we can allow the user to specify the content type=20 expected by the folder. Instead of matching by file extension, we match by= =20 folder. All resources, including images are stored within this folder.=20 =46orrest does not try to determine image locations, css, javascript etc.=20 locations. This is defined by the transformation stylesheets. =46orrest would need properties to be provided so that supported content ty= pes=20 are mapped or associated with 0 or more paths. When a property is not set =3D "0", that content type is seen as non-exista= nt in=20 the system. When set it to a value of "1" it will automatically look for th= e=20 paths where such content type resides and the plug-in and sitemap to use. I also think that mapping to a path is more efficient than mapping explicit= ly=20 to files with a given extension. Does anyone think this could work? =2D-=20 Sean Wheller Technical Author sean@inwords.co.za http://www.inwords.co.za