Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 74916 invoked from network); 23 Nov 2004 23:08:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 23 Nov 2004 23:08:45 -0000 Received: (qmail 83207 invoked by uid 500); 23 Nov 2004 23:08:42 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 83153 invoked by uid 500); 23 Nov 2004 23:08:42 -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 83140 invoked by uid 99); 23 Nov 2004 23:08:42 -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 [81.209.148.130] (HELO dd2020.kasserver.com) (81.209.148.130) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 23 Nov 2004 15:08:42 -0800 Received: from [192.168.1.2] (pD9E9D31A.dip0.t-ipconnect.de [217.233.211.26]) by dd2020.kasserver.com (Postfix) with ESMTP id 491B1189A1A for ; Wed, 24 Nov 2004 00:08:35 +0100 (CET) Message-ID: <41A3C3FC.4070400@apache.org> Date: Wed, 24 Nov 2004 00:13:00 +0100 From: Torsten Curdt User-Agent: Mozilla Thunderbird 0.8 (X11/20041012) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [proposal] smaller root sitemap References: <41A38428.3040409@apache.org> In-Reply-To: X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Ralph Goers wrote: > While I agree that having a 40Kb sitemap is a bit much, I think you are > attacking the wrong problem. If you look at the default sitemap (i.e. the > one built with the default properties), the first 700+ lines are > configuration and only the last 180 are pipeline definitions. To be > honest, its never been clear to me why configuration of generators, > actions, etc. occurs in the sitemap as opposed to cocoon.xconf. Here we go again :-) ...this comes up every now and then ...but I tend to agree IMHO it's ok when you wanna override them in a sub-sitemap. But I also think that for the root sitemap the configuration should go into the cocoon.xconf. Although the question is if this helps the readability of the cocoon.xconf > Frankly, I'd rather see a cocoon.xconf in every directory that has a > sitemap.xmap. The sitemap would only have the pipelines. Cocoon.xconf > would have the generators, actions, etc. + stuff that should be configured > only when a sitemap is entered for the first time. Hm... from a SoC POV you are probably right ...although I am still not sure if I like that idea. But one thing is for sure a pain ...removing all the crap from the default sitemap as well as the cocoon.xconf when you start a new project is no fun. Not sure if the "we wanna show all what's available"-approach helps users to find their way more easily. ...maybe some javadoc-like documentation (with the frames) would help. You select the component that you would like to use and you get a description as well as a sitemap snippet you can insert into your very basic sitemap/cocoon.xconf. ...just a RT cheers -- Torsten