Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: pass (herse.apache.org: domain of brian.dube@gmail.com
 designates 66.249.82.237 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
        b=nVMHz5zKWzEWXg6MxH90pPz6WrkFjbEJxfwsjhHvwIB/XWD23f/VMLj07inBbl67vWgqhjAP+mAygw3I+H6XjwkyeHmCRlFipABIWchhmdDYe/OyMHf1ELdpXf3dmtaXvnhChMHI1z0vTeoSA4XIhZOWfdUOP0sJvJIyvliF78g=
Message-ID: <462CA3C7.4000009@gmail.com>
Date: Mon, 23 Apr 2007 07:17:11 -0500
From: Brian M Dube <brian.dube@gmail.com>
User-Agent: Icedove 1.5.0.10 (X11/20070329)
MIME-Version: 1.0
To: dev@forrest.apache.org
Subject: Re: Skin plugin
References: <462A107B.50505@gmail.com>
 <20070423040128.GE1760@igg.indexgeo.com.au>
In-Reply-To: <20070423040128.GE1760@igg.indexgeo.com.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

David Crossley wrote:
> I am not yet clear about your main aim. Is it to move
> the existing functionality out of the core and leave it
> at that (a legacy system)? Or is it to create a framework
> as described above which would enable future development
> of skins functionality as well as dispatcher.

If community support of skins is questionable, then a flexible framework 
seems to me the way to go.

> Not sure what to do about the different skins.
> There would be a similar discussion in the archives about
> when the Dispatcher work established the f.a.o.themes.core
> plugin.

> Let us continue to express our needs for a little
> while on this dev list, before launching into the
> actual development.

Fair enough. For one of my projects I tested a modification to the 
Forrest build files that leaves out (unused) skin resources when 
building dispatcher sites. It would be great if this case is handled 
when skins move out of core.

Brian