forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <cross...@apache.org>
Subject Re: [jira] Commented: (FOR-639) define terminology for the various aspects of Dispatcher
Date Wed, 19 Apr 2006 01:49:33 GMT
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

Mime
View raw message