> This looks very nice! I like decreasing barriers to entry (no cygwin
> necessary)!
Doesn't Java mean portable? ;)
> I don't have time to test it right now, but if a windows XP user can give
> it a go and tell us it works, I'll be happy to commit it.
I'm more concerned about Windows NT.
> The other thing that might be nice is to remove build.sh/build.cmd/etc
> from httpd-2.0 and instead place them, together with all the necessary
> libraries in a seperate CVS repository where they can just be checked out
> into the right place. I am a little uncomfortable with the fact that we
> are placing .cmd and .sh files into a directory that is accessible by
> default for everyone who installs apache. It isn't executable by default,
> but with a slight configuration error...
>
> What do people think about that?
I've had some thoughts along that line as well, but even more rigorous.
The XML files are a kind of source files as well. Although you can look at a
single XML file with a 'XML client' (like a web browser), the generated HTML
references other HTML files. In an installation, this would mean that the
XML files are useless and you would need an XSLT processor to read them. To
overcome this, there are two options (Option three being a bit more work
;) ).
1. Move the XML files to the 'build tree' Joshua just suggessted. Before
release, the HTML files will be generated and packed.
2. Hack the style sheets to use links to XML files by default and if a
parameter is set (for instance by Ant), links to HTML files.
<xsl:param name="filetype" select="'xml'" />
....
<a href="{name}.{$filetype}">
(3. 'mod_xslt' in default distro)
I'll be willing to get option 2 implemented if that seems a good idea.
Vincent de Lau
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
