From dev-return-23573-apmail-forrest-dev-archive=forrest.apache.org@forrest.apache.org Wed Apr 19 01:50:03 2006 Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 30300 invoked from network); 19 Apr 2006 01:50:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 19 Apr 2006 01:50:03 -0000 Received: (qmail 66877 invoked by uid 500); 19 Apr 2006 01:50:02 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 66831 invoked by uid 500); 19 Apr 2006 01:50:02 -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 66816 invoked by uid 99); 19 Apr 2006 01:50:02 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Apr 2006 18:50:02 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [65.77.211.84] (HELO www2.kc.aoindustries.com) (65.77.211.84) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Apr 2006 18:50:01 -0700 Received: from fo2.kc.aoindustries.com (www2.kc.aoindustries.com [65.77.211.84]) by www2.kc.aoindustries.com (8.13.1/8.13.1) with ESMTP id k3J1neac011723 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 18 Apr 2006 20:49:40 -0500 Received: from localhost (localhost [[UNIX: localhost]]) by fo2.kc.aoindustries.com (8.13.1/8.13.1/Submit) id k3J1ndJF011650 for dev@forrest.apache.org; Tue, 18 Apr 2006 20:49:39 -0500 X-Authentication-Warning: fo2.kc.aoindustries.com: indexgeo set sender to crossley@apache.org using -f Date: Wed, 19 Apr 2006 11:49:33 +1000 From: David Crossley To: dev@forrest.apache.org Subject: Re: [jira] Commented: (FOR-639) define terminology for the various aspects of Dispatcher Message-ID: <20060419014933.GB21972@igg.indexgeo.com.au> References: <20060415004444.GA21972@igg.indexgeo.com.au> <200604150143.k3F1hW5g023457@mail.e-wire.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200604150143.k3F1hW5g023457@mail.e-wire.net.au> User-Agent: Mutt/1.4.2.1i X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Gav.... wrote: > David Crossley wrote: > > Gav.... wrote: > > > > > > Getting back to CSS and plugins then, why is it that a lot (but not > > > All) of plugins have a complete set of skins + css or themes + css ? > > > Surely the plugin would/should adhere to the styling and layout of the > > > Site it belongs to, then add specific css as/if needed? > > > > Ah, i wonder if i detect a misunderstanding. > > For the "Skins" side of things there is just a > > directory structure for additional skin-specific > > resources e.g. javascript and css and images. > > > > Depending on the skin name, Cocoon will find the > > relevant resources automatically. See the sitemap > > matches for resources in main/webapp > > > > For Dispatcher i don't know how extra plugin-specific > > and theme-based resources are handled. > > So, can we make the plugin compatibile with both skins > And themes? What does the main forrest site use, Being enabled as "skins" is the default for all of Forrest. The Dispatcher is work-in-progress in the whiteboard. > I see > A skin and a theme enabled in default.forrest.properties. They are not "enabled". Those are the default values if the user does not provide any values. So for example if they add the Dispatcher plugins via their forrest.properties and do not provide any "project.theme" property, then project.theme=common is the default. -David