forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Brondsema <d...@brondsema.net>
Subject Re: multiple skin descriptors, skin versions
Date Wed, 04 Feb 2004 02:53:41 GMT
Quoting Nicola Ken Barozzi <nicolaken@apache.org>:

> Dave Brondsema wrote:
> ...
> > So each skin needs to declare what version it is and what versions of
> > forrest it is compatible with.  We could put this in the skins.xml
> > along with the other info (url, name, etc) of the skin.  However, the
> > version info needs to be self-contained in the skin and remain in a file
> > on the local installation of forrest.  skins.xml files are temporary on
> > local installations.
> 
> IIRC I had added a filename convention too, so a skin would be for example:
> 
>   skinname-f0.5-0.3.jar (version 0.3 compatible with forrest 0.5)
> 

I like this.  Simpler is better.

> But I still don't see why I would want an "old" skin for my Forrest (IE 
> why get skinname-f0.5-0.2.jar if skinname-f0.5-0.3.jar is available?)
> 

I agree.

> So, in the sake of simplicity, and following what happens with Mozilla 
> skins, I propose that we define a skin version, and that this scheme is 
> applied to the filenames of the skins just as it happens for Mozilla.
> 

The file names of the themes don't seem to follow any pattern.  Where do you see
this?

> To be able to update a skin, what I propose is to make the skin 
> downloader add in the local unpacked skin the publish date if the skin 
> on the site: in this way, in subsequent checks it can easily see if the 
> skin has changed, and propose an update.
> 
> WDYT?
> 

Sounds good to me.

-- 
Dave Brondsema 
dave@brondsema.net 
http://www.brondsema.net - personal 
http://www.splike.com - programming 
http://csx.calvin.edu - student org 

Mime
View raw message