forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <>
Subject Re: skin package descriptor skins.xml
Date Thu, 02 Oct 2003 10:42:46 GMT
Nicola Ken Barozzi wrote:
> David Crossley wrote:
> > I just banged some text in for the "description" element.
> > Nicola Ken, would you please tweak that text. Is it really
> > based on forrest-site?
> Yup.
> > Could you add a few words about the
> > differences. 
> I'd like to remove them ASAP rather than keep them, I just removed some 
> stuff without thinking much ;-)
> The question is: should we move the krysalis-skin out of Forrest?
> I'm +1 to it.

Oh yeah, great idea - do it. We just point to one real-life
example to start with.

> > It would be good to provide a leading example
> > for the descriptor.
> ?

I mean, the best way to encourage good use is to lead by example.
Describe the initial skin to the best of our ability. That will
then encourage others to write good descriptors.

> > We should discuss the needs of the skins.xml descriptor.
> > 
> > So far we have some attributes for the <skin> element ...
> >  name="testskin"
> >  author="Nicola Ken Barozzi"
> >  website=""
> >  url=""
> > and then a <description> element for some text.
> > 
> > It would be nice if the "website" was actually a page that gave some
> > information about the skins, rather than just a simple credit URL.
> Yeah, but that's up to the skin creator, ...

Yes i agree. We should drop the "website" attr altogether.
If they want to have an "About my skin" page then they can
put it as the index.html page of the "url" attr.

> ... and I don't really want to 
> publish anything about these "skins" ;-)

(Uh, oh. Does that smiley thing mean that this is a joke?)

Actually that raises a serious issue with this skins descriptor file.
We, the Apache Forrest project don't want to get into the role of
certify/support/approve/promote/... so we just have minimal info.

> What I'd like to add is an img="" url with a preview of the skin.

I agree ... probably mandatory, so that we can do the "themes" page.

We need two things rather than just "img" ...
... explicit dimensions (force-scaled if they don't adhere)
... large screenshot or live site demo

> Then I'd like to add a stylesheet for it to Forrest, and have it render 
> like here:

Of course. We expect no less.

> The only difference I see is that we don't provide versions of the skins 
> on the page; it's made to have users only provide an initial url and be 
> able to update skins and image previews without having to notify us each 
> single time.

Yes, keep it simple.


View raw message