You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Dave Brondsema <da...@brondsema.net> on 2003/12/11 20:22:25 UTC
[RT] custom skin in multiple projects
With my work on forrestbot and the current discussion of custom skins I
realized I will want to use one custom skin for many projects. I don't
think it's fitting to put it in the Forrest package, nor to put it in all
the projects' src directories.
I'd like to be able to have an external location (any specified directory)
that forrest will look for skins. Is this a good idea?
--
Dave Brondsema
dave@brondsema.net
http://www.brondsema.net - personal
http://www.splike.com - programming
http://csx.calvin.edu - Calvin club
Re: [RT] custom skin in multiple projects
Posted by David Crossley <cr...@indexgeo.com.au>.
Dave Brondsema wrote:
> With my work on forrestbot and the current discussion of custom skins I
> realized I will want to use one custom skin for many projects. I don't
> think it's fitting to put it in the Forrest package, nor to put it in all
> the projects' src directories.
>
> I'd like to be able to have an external location (any specified directory)
> that forrest will look for skins. Is this a good idea?
Can this achieved by the recently added "fetch-skins" task?
Perhaps it can first look for a local "skins descriptor" file.
--David
Re: [RT] custom skin in multiple projects
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Dave Brondsema wrote:
> Quoting Nicola Ken Barozzi <ni...@apache.org>:
...
>>What you need to do to use it is explained briefly here:
>>
>> http://xml.apache.org/forrest/skin-package.html
>
> I think this would be a good solution, but currently it requires the skin to be
> available from the forrest site.
Not really, only the reference to the skin, that is actually downloaded
elsewhere.
> I think we should allow different repositories
> to be specified. The most useful would be a local repository. At my company we
> would want to have a corporate repository hosted on our intranet.
Makes sense.
> I think this would best be configured in a properties file that applies to
> forrest in general, not a single project. Perhaps any forrest.properties in
> $FORREST_HOME or $HOME would be used for default values not set in a project's
> forrest.properties. Then a user could set
> forrest.skins-descriptors=/home/me/myskins/skins.xml,http://dev.intranet/skins/skins.xml
This is one way of doing it, by making your descriptor override the
Forrest one.
I was thinking of another solution, that is to be able to specify skins
with their download URL, but since I want to enhance the descriptor to
keep also DTDs and transformation extensions, making it possible to
override the descriptor location seems a good idea.
So I would make it possible to override it boh in the project
forrest.properties and in the installed forrest properties.
forrest.extensions.descriptors=/.../ext.xml,http://dev.intranet/skins.xml
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: [RT] custom skin in multiple projects
Posted by Dave Brondsema <da...@brondsema.net>.
Quoting Nicola Ken Barozzi <ni...@apache.org>:
> Dave Brondsema wrote:
>
> > With my work on forrestbot and the current discussion of custom skins I
> > realized I will want to use one custom skin for many projects. I don't
> > think it's fitting to put it in the Forrest package, nor to put it in all
> > the projects' src directories.
>
> I'd like to remove the possibility of using the src dir to add skins, as
> it does not favor reuse. That's why I added the auto download of skin
> packages.
>
> > I'd like to be able to have an external location (any specified directory)
> > that forrest will look for skins. Is this a good idea?
>
> The fetch-skins system is done exactly for this task.
>
> What happens is that the skins are packaged in a zip, referenced in a
> descriptor on the forrest site and auto downloaded in the currently
> installed Forrest when needed.
>
> What you need to do to use it is explained briefly here:
>
> http://xml.apache.org/forrest/skin-package.html
>
I think this would be a good solution, but currently it requires the skin to be
available from the forrest site. I think we should allow different repositories
to be specified. The most useful would be a local repository. At my company we
would want to have a corporate repository hosted on our intranet.
I think this would best be configured in a properties file that applies to
forrest in general, not a single project. Perhaps any forrest.properties in
$FORREST_HOME or $HOME would be used for default values not set in a project's
forrest.properties. Then a user could set
forrest.skins-descriptors=/home/me/myskins/skins.xml,http://dev.intranet/skins/skins.xml
--
Dave Brondsema
dave@brondsema.net
http://www.brondsema.net - personal
http://www.splike.com - programming
http://csx.calvin.edu - student org
Re: [RT] custom skin in multiple projects
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Dave Brondsema wrote:
> With my work on forrestbot and the current discussion of custom skins I
> realized I will want to use one custom skin for many projects. I don't
> think it's fitting to put it in the Forrest package, nor to put it in all
> the projects' src directories.
I'd like to remove the possibility of using the src dir to add skins, as
it does not favor reuse. That's why I added the auto download of skin
packages.
> I'd like to be able to have an external location (any specified directory)
> that forrest will look for skins. Is this a good idea?
The fetch-skins system is done exactly for this task.
What happens is that the skins are packaged in a zip, referenced in a
descriptor on the forrest site and auto downloaded in the currently
installed Forrest when needed.
What you need to do to use it is explained briefly here:
http://xml.apache.org/forrest/skin-package.html
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: [RT] custom skin in multiple projects
Posted by Marshall Roch <ma...@exclupen.com>.
Dave Brondsema wrote:
> With my work on forrestbot and the current discussion of custom skins I
> realized I will want to use one custom skin for many projects. I don't
> think it's fitting to put it in the Forrest package, nor to put it in all
> the projects' src directories.
>
> I'd like to be able to have an external location (any specified directory)
> that forrest will look for skins. Is this a good idea?
I like this idea. Then the content editors have no way to screw up the
skin, and vice versa. Maybe it would even be possible to store content
and skins as separate CVS modules (I'm not big on CVS administration,
but maybe this would allow for different access rights?).
--
Marshall Roch