Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: forrest-dev@xml.apache.org
Message-ID: <1083770254.4099058ed97e8@secure.solidusdesign.com>
Date: Wed,  5 May 2004 11:17:34 -0400
From: Dave Brondsema <dave@brondsema.net>
To: forrest-dev@xml.apache.org
Subject: Re: [DEVOTE] Solving the skinconf riddle
References: <c6oa7i$iqf$1@sea.gmane.org> <1083323942.2035.162.camel@ighp>
  <c6tl6s$9mm$1@sea.gmane.org> <1083385469.5609.92.camel@ighp>
  <c73osu$2p9$1@sea.gmane.org> <1083567826.31080.225.camel@ighp>
  <c754rv$dji$1@sea.gmane.org> <1083743144.2081.119.camel@ighp>
  <c7amon$i0s$2@sea.gmane.org> <1083768919.2082.133.camel@ighp>
In-Reply-To: <1083768919.2082.133.camel@ighp>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2.1

Quoting David Crossley <crossley@apache.org>:

> Nicola Ken Barozzi wrote:
> > David Crossley wrote:
> > > Nicola Ken Barozzi wrote:
> > > 
> > >>Each skin would have the complete version instead, with the 
> > >><!--@required--> tag stuff or the required="" attribute, from which 
> > >>Forrest would dynamically create the skinconf.xsl file that is now done 
> > >>"by hand".
> > >>
> > >>Given that this file would be made by skin authors and that it's better 
> > >>to keep a single schema for skinconfs maybe it's better to use the <!--@
> 
> > >>annotations for this file instance.
> > > 
> > > 
> > > I too am confused as to how it hangs together. Is this it? ...
> > > 
> > > Each skin has a skinconf.xml (or is that skindef.xml) which is
> > > managed by the skin creator people, not the users. It has the
> > > documentation comments and the "@required" comments and has
> > > all possible features.
> > 
> > Correct.
> > 
> > > There is a build task that generates certain files from that:
> > > * skinconf.xsl which injects default values
> > 
> > This is to be done in the sitemap IMHO, no build-time stuff.
> 
> You are right. My discussion points were more intended to define
> what was generated rather than how or when.
> 
> > > * skinconf-vXY.rng which enables validation of users' skinconf.xml
> > 
> > Correct. Validation is a build-time task, so it there is no issue in 
> > having it generated at that point.
> > 
> > > * skinconf.xml which is an example file for users to apply
> > > to their project skinconf.xml if they need to over-ride or
> > > disable certain features.
> > 
> > Hmmm, I was thinking instead of including a page in the Forrest docs 
> > with the documentation and an example version for cut-and-paste.
> 
> That too. It would also be good to have an actual xml file
> that people can diff with their project skinconf.xml
> 
> Okay, it seems that we are on the same wavelength.
> 
> What is the next step?
> 
> --David
> 

Make a branch and start doing it? :-)

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