Return-Path: Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 54032 invoked by uid 500); 19 Aug 2003 22:30:16 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 52985 invoked from network); 19 Aug 2003 22:29:44 -0000 Received: from mhub-w3.tc.umn.edu (160.94.160.47) by daedalus.apache.org with SMTP; 19 Aug 2003 22:29:44 -0000 Received: from [24.245.76.43] by mhub-w3.tc.umn.edu with ESMTP for dev@cocoon.apache.org; Tue, 19 Aug 2003 16:51:22 -0500 Message-Id: <3F429BF2.9010507@umn.edu> Date: Tue, 19 Aug 2003 16:51:46 -0500 From: Tony Collen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [RT] Improving Sitemap and Flowscript References: <7D697757-CF6D-11D7-B9EC-000393D2CB02@apache.org> <3F428A13.6070906@pcextremist.com> In-Reply-To: <3F428A13.6070906@pcextremist.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Miles Elam wrote: > Stefano Mazzocchi wrote: &snip; >> the default sitemap is too verbose and this scares people away. I >> would like to move the default sitemap component definitions into the >> cocoon.xconf. >> >> Note that with blocks, the definitions of those components will be in >> the block.xconf as well and this will be aggregated by the block manager. > > > > Except for the fact that cocoon.xconf is too verbose and this scares > people away. While for the most part the contents of cocoon.xconf have > no direct impact on the sitemap, the components are intimately tied. Not to mention being able to inherit components from super-sitemaps. I use this all the time and I'd hate to see this go away. - Tony