You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Christoph Wilhelms <Ch...@impress.com> on 2003/01/02 10:03:32 UTC
[VOTE] FakeForrest is ready!
Hi All!
I have finished the FakeForrest Anakia/Velocity template and committed it to
the proposal/ant-site/anakia directory. It's something like a "best of both
worlds" approach (Design from forrest, but added bixed headers, tables and
source boxes from the current anakia-templates (with some color pushing).
For that reason it's time to come up with a multiple vote/proposal:
[1] We want to use Forrest for ant.apache.org (because it is soooo nice ;))
[2] Use the FakeForrest Anakia/Velocity template to generate the site until
we converted the xdocs xmls to the forrest dtd and the project.xml into a
book.xml.
[3] Probably stick to the FakeForrest approach until Forrest itself offers
bixed headers (referring to Nicola Ken Barozzi :)).
Here is of course my +1 to my complete proposal :).
Happy New Year!
Chris
P.S.: I've already updated the templates to 2003 and if you want a sneak
peak youst click here:
http://cvs.apache.org/viewcvs.cgi/*checkout*/jakarta-ant/proposal/ant-site/a
nakia/docs/index.html?rev=HEAD&content-type=text/html
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [VOTE] FakeForrest is ready!
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Robert Koberg wrote:
> Hey again,
>
>
>>-----Original Message-----
>>From: Nick Chalko [mailto:nick@chalko.com]
>>Sent: Friday, January 03, 2003 2:51 PM
>>To: forrest-dev@xml.apache.org
>>Subject: Re: [VOTE] FakeForrest is ready!
>>
[...]
>>docbook is very feature rich.
>
> yes - to the extreme! an extreme I once tried to support to my consternation...
Which is the reason why we decided to stick to our DTD.
We are open to enhancements on it though, please do ask if you think
enhancements are necessary.
There is a document that keeps the deficiencies of the DTD, that we
might fix:
http://cvs.apache.org/viewcvs/xml-forrest/etc/DTD_DEFICIENCIES.txt?rev=HEAD&content-type=text/vnd.viewcvs-markup
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: Standard DTD (was Re: [VOTE] FakeForrest is ready!)
Posted by Joerg Pietschmann <j3...@yahoo.de>.
On Saturday 04 January 2003 13:14, Steven Noels wrote:
> I just had a quick look at sdocbook - would it be a candidate for a
> mid-tier format?
More source than mid-tier I would think. It's still more semantic markup
than XHTML.
> What do you think?
DocBook is the base of LinuxDoc (i.e. there is a certain user base),
and many Linux distributions can install a (more or less) working
DocBook processing environment right out of the box.
J.Pietschmann
Re: Standard DTD (was Re: [VOTE] FakeForrest is ready!)
Posted by Steven Noels <st...@outerthought.org>.
Nicola Ken Barozzi wrote:
> I think that we should embrace a standard instead of continuing on our
> own DTD.
Support rather than embrace maybe.
I just had a quick look at sdocbook - would it be a candidate for a
mid-tier format?
> Reasons:
> - editors: standards have editors that users can really use to
> edit our docs
> - users: users know standard DTDs already, but have to take some time
> to learn ours.
> - interoperability: using a standard DTD makes it easy for other tools
> to output to that DTD for us or viceversa
>
> I had proposed XHTML 2 as a base for our new DTD; and also did a
> comparison. Nothing followed.
> If someone wants to go forward with it, here's the link; in the middle
> there is a tag-per-tag comparison:
>
> http://marc.theaimsgroup.com/?l=forrest-dev&m=102909917505608&w=2
XHTML2 is under lots of pressure IIRC. Too much, too soon.
What we could do is having such a setup:
ENTRY MID-TIER
xdocs CAP sdocbook skin xsl-fo
sdocbook ----> or ----> (x)html
xhtml2? xhtml2 rss
status
...
What do you think?
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org stevenn at apache.org
Re: Standard DTD (was Re: [VOTE] FakeForrest is ready!)
Posted by Stefano Mazzocchi <st...@apache.org>.
Jeff Turner wrote:
> Or rather, make docv11 just another format that Forrest supports.
Jeff is right on the money here.
I'm so sick of people complaining about Forrest because of the DTD. God,
it reminds me of the stupid flamewars about little-endian vs. big-endian
on CPU assembly instructions.
The idea should be: you use whatever DTD/schema you like and Forrest
will take care of the rest.
Like Steven said, publishing should not be a two-phase sequence but a
three-phase one:
original -(adaptation)-> model -(presentation)-> view
of course, this works only if the "model" schema is powerful enough to
contain all the semantics used by any 'original' schemas. So, in this
respect, probably DocBook would be the best schema for that part.
But my suggestion would be to adopt that model but keep it simple and
keep using our Document DTD and add things incrementally to make sure we
really need them (moving from document to docbook is simply too big as a
jump... but simplified docbook might not be... worth considering)
Now, how can we make that adaptation phase as transparent as possible?
--
Stefano Mazzocchi <st...@apache.org>
--------------------------------------------------------------------
Re: Standard DTD (was Re: [VOTE] FakeForrest is ready!)
Posted by Jeff Turner <je...@apache.org>.
On Mon, Jan 06, 2003 at 03:33:03PM +1100, David Crossley wrote:
...
> > Forrest needs a bit of restructuring to support multiple
> > document types.
> > Each new doctype requires (at least):
> >
> > - schemas, currently in src/resources/schema/dtd
> > - XSLTs, in src/resources/skins/common/xslt
> > - catalog in src/resources/schema
> > - sitemap mods
> >
> > I was thinking we could package these up into RPM-like bundles,
> > so users could download new doctype support as they need it.
> >
> > Forrest plugins. Hmm. Volunteers? :)
>
> This would be truly excellent to have the infrastructure
> for such plugins. In this way, business could add value
> to Forrest and sell support packages for specialised
> communities. Anyway, back to building the infrastructure.
>
> Great idea Jeff, i will help.
>
> How would it work? Would the forrest-dev community
> maintain configuration files for each supported package
> which define where Ant will get the separate pieces and
> where to insert them into the local build?
>
> Or would Forrest have separate cvs modules to hold copies
> of the various released schemas, i.e. pre-prepared packages
> of all the bits, that would be maintained by forrest-dev?
So it's a choice of when the pieces are assembled: once by a Forrest dev,
or dynamically on the user's computer.
I've implemented the first with a handful of Ant scripts (which in turn
download others..) and ViewCVS:
http://marc.theaimsgroup.com/?l=forrest-dev&m=103770809113417&w=2
The second 'pre-packaged' thing is more ambitious, but still fairly
do-able. Just a (signed) jar with a META-INF/control.xml Ant script
describing how to 'deploy' the jar contents to the Forrest installation.
--Jeff
> --David
>
Re: Standard DTD (was Re: [VOTE] FakeForrest is ready!)
Posted by David Crossley <cr...@indexgeo.com.au>.
Jeff Turner wrote:
> Nicola Ken Barozzi wrote:
> > Miles Elam wrote:
> > >Robert Koberg wrote:
> > >
> > [...]
> >
> > >Simplified DocBook I think fits the role of a round peg here.
> > >http://www.oasis-open.org/docbook/xml/simple/
> >
> > [...]
> >
> > >Have you found the same to be true of the simplified version?
> > >http://www.docbook.org/tdg/simple/en/html/sdocbook.html
> >
> > [...]
> >
> > >It was not my intention to muddy the waters here, but I thought these
> > >links might be interesting if for no other reason than to have another
> > >schema with which to compare when making your own.
> >
> > I think that we should embrace a standard instead of continuing on our
> > own DTD.
>
> +1
>
> Or rather, make docv11 just another format that Forrest supports.
Forrest already does support any format you like. It is
easy to configure for other document types. At the
xml-commons project we have mixed types, some in full
DocBook some in document-v11 type. Using the project
sitemap.xmap and cocoon.xconf it is very easy.
http://marc.theaimsgroup.com/?l=xml-commons-dev&m=104037450832414
However, we do need to make it even easier and platform
independent. I like Jeff's proposal below.
<snip/>
>
> Forrest needs a bit of restructuring to support multiple
> document types.
> Each new doctype requires (at least):
>
> - schemas, currently in src/resources/schema/dtd
> - XSLTs, in src/resources/skins/common/xslt
> - catalog in src/resources/schema
> - sitemap mods
>
> I was thinking we could package these up into RPM-like bundles,
> so users could download new doctype support as they need it.
>
> Forrest plugins. Hmm. Volunteers? :)
This would be truly excellent to have the infrastructure
for such plugins. In this way, business could add value
to Forrest and sell support packages for specialised
communities. Anyway, back to building the infrastructure.
Great idea Jeff, i will help.
How would it work? Would the forrest-dev community
maintain configuration files for each supported package
which define where Ant will get the separate pieces and
where to insert them into the local build?
Or would Forrest have separate cvs modules to hold copies
of the various released schemas, i.e. pre-prepared packages
of all the bits, that would be maintained by forrest-dev?
--David
Re: Standard DTD (was Re: [VOTE] FakeForrest is ready!)
Posted by Jeff Turner <je...@apache.org>.
On Sat, Jan 04, 2003 at 01:02:45PM +0100, Nicola Ken Barozzi wrote:
>
> Miles Elam wrote:
> >Robert Koberg wrote:
> >
> [...]
>
> >Simplified DocBook I think fits the role of a round peg here.
> >http://www.oasis-open.org/docbook/xml/simple/
>
> [...]
>
> >Have you found the same to be true of the simplified version?
> >http://www.docbook.org/tdg/simple/en/html/sdocbook.html
>
> [...]
>
> >It was not my intention to muddy the waters here, but I thought these
> >links might be interesting if for no other reason than to have another
> >schema with which to compare when making your own.
>
> I think that we should embrace a standard instead of continuing on our
> own DTD.
+1
Or rather, make docv11 just another format that Forrest supports.
> Reasons:
> - editors: standards have editors that users can really use to
> edit our docs
> - users: users know standard DTDs already, but have to take some time
> to learn ours.
> - interoperability: using a standard DTD makes it easy for other tools
> to output to that DTD for us or viceversa
>
> I had proposed XHTML 2 as a base for our new DTD; and also did a
> comparison. Nothing followed.
> If someone wants to go forward with it, here's the link; in the middle
> there is a tag-per-tag comparison:
>
> http://marc.theaimsgroup.com/?l=forrest-dev&m=102909917505608&w=2
Forrest needs a bit of restructuring to support multiple document types.
Each new doctype requires (at least):
- schemas, currently in src/resources/schema/dtd
- XSLTs, in src/resources/skins/common/xslt
- catalog in src/resources/schema
- sitemap mods
I was thinking we could package these up into RPM-like bundles, so users
could download new doctype support as they need it.
Forrest plugins. Hmm. Volunteers? :)
--Jeff
Standard DTD (was Re: [VOTE] FakeForrest is ready!)
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Miles Elam wrote:
> Robert Koberg wrote:
>
[...]
> Simplified DocBook I think fits the role of a round peg here.
> http://www.oasis-open.org/docbook/xml/simple/
[...]
> Have you found the same to be true of the simplified version?
> http://www.docbook.org/tdg/simple/en/html/sdocbook.html
[...]
> It was not my intention to muddy the waters here, but I thought these
> links might be interesting if for no other reason than to have another
> schema with which to compare when making your own.
I think that we should embrace a standard instead of continuing on our
own DTD.
Reasons:
- editors: standards have editors that users can really use to
edit our docs
- users: users know standard DTDs already, but have to take some time
to learn ours.
- interoperability: using a standard DTD makes it easy for other tools
to output to that DTD for us or viceversa
I had proposed XHTML 2 as a base for our new DTD; and also did a
comparison. Nothing followed.
If someone wants to go forward with it, here's the link; in the middle
there is a tag-per-tag comparison:
http://marc.theaimsgroup.com/?l=forrest-dev&m=102909917505608&w=2
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: [VOTE] FakeForrest is ready!
Posted by Miles Elam <mi...@geekspeak.org>.
Robert Koberg wrote:
>>-----Original Message-----
>>From: Nick Chalko [mailto:nick@chalko.com]
>>Subject: Re: [VOTE] FakeForrest is ready!
>>
>>Robert Koberg wrote:
>>
>>
>>>Docbook deals with technical _books_ (OReilly, specifically??). A
>>>
>>>
>>website is not
>>
>>
>>>a book. Why try to fit a square peg in a round hole?
>>>
Simplified DocBook I think fits the role of a round peg here.
http://www.oasis-open.org/docbook/xml/simple/
From the page:
Over the years, the notion of a "simple" DocBook subset has come up
many times. It has been observed that the number of elements in
DocBook can be a little overwhelming to the new user.
This DTD is an attempt to make a small subset of DocBook. The goals
of this subset are:
Documents written in the subset must be 100% legal DocBook documents.
This subset for single documents (articles, white papers, etc.),
so there's no need for books or sets, just 'articles'.
The markup should be the smallest practical subset, if you need
richly structured markup, use full DocBook. In particular, the
subset often selects a single element from a family of related
elements; for example, programlisting is provided, but screen is not.
>>It does do website, but it is UGLY, or at least plain.
>>When using forrest, I miss things like callouts, tags for commands, dir,
>>object, functions, keystrokes, etc.
>>
Yes and no. DocBook (and its simplified offspring) has no inherent
presentation. What you are probably describing is the LaTeX look-alike
that Norman Walsh made available as XSLT stylesheets. DocBook can be
made to look anyway you like. I'm sorry that I don't have examples
handy (we're using Simplified DocBook on our site) as I'm still working
on the XSLT for the site.
As far as missing elements, the DocBook website has long held
instructions and guidelines for using subsets and supersets of its
markup cleanly and easily. The idea here is that more people would know
DocBook than any one organization's DTD. If the organization used
DocBook plus or minus some needed elements/attributes, presumably it
would aid in the general learning curve for newbies and allow for easier
cross-pollination between projects.
>I am a bit fuzzy from the road (vacation)... but last I remember forrest expands
>on XHTML where most of these things are represented. If not, then they should
>(could) be added to the schema, without adopting all the overhead that comes
>with docbook.
>
Once again, there's a simplified variant. Also, XHTML -- while a
definite improvement over early HTML versions -- is fairly deficient in
the semantic clarity department.
>>docbook is very feature rich.
>>
Indeed.
>yes - to the extreme! an extreme I once tried to support to my consternation...
>
Have you found the same to be true of the simplified version?
http://www.docbook.org/tdg/simple/en/html/sdocbook.html
The full DocBook was far too much to handle for us in one bite and we
were about to look elsewhere when I stumbled across Simplified. With
about 100 tags, it's complete enough to get most tasks done but small
enough to learn quickly. As time moves along, we may incorporate some
more of full DocBook. By that time, it's assumed that the smaller
version will have primed us. Also, since Simplified is valid DocBook,
it leaves open the possibility that all of our articles could be
compiled together as a cohesive entity (book, manual, memoir, etc.).
-----
It was not my intention to muddy the waters here, but I thought these
links might be interesting if for no other reason than to have another
schema with which to compare when making your own.
- Miles
RE: [VOTE] FakeForrest is ready!
Posted by Robert Koberg <ro...@koberg.com>.
Hey again,
> -----Original Message-----
> From: Nick Chalko [mailto:nick@chalko.com]
> Sent: Friday, January 03, 2003 2:51 PM
> To: forrest-dev@xml.apache.org
> Subject: Re: [VOTE] FakeForrest is ready!
>
>
> Robert Koberg wrote:
>
> >Hi,
> >
> >Docbook deals with technical _books_ (OReilly, specifically??). A
> website is not
> >a book. Why try to fit a square peg in a round hole?
> >
> It does do website, but it is UGLY, or at least plain.
> When using forrest, I miss things like callouts, tags for commands, dir,
> object, functions, keystrokes, etc.
I am a bit fuzzy from the road (vacation)... but last I remember forrest expands
on XHTML where most of these things are represented. If not, then they should
(could) be added to the schema, without adopting all the overhead that comes
with docbook.
>
> docbook is very feature rich.
yes - to the extreme! an extreme I once tried to support to my consternation...
best,
-Rob
Re: [VOTE] FakeForrest is ready!
Posted by Nick Chalko <ni...@chalko.com>.
Robert Koberg wrote:
>Hi,
>
>Docbook deals with technical _books_ (OReilly, specifically??). A website is not
>a book. Why try to fit a square peg in a round hole?
>
It does do website, but it is UGLY, or at least plain.
When using forrest, I miss things like callouts, tags for commands, dir,
object, functions, keystrokes, etc.
docbook is very feature rich.
What I would love to the ability to have docbook fomrated pages in
forrest site while keeping the forrest header, menu, and footer.
R,
Nick
>
>best,
>-Rob
>
>
>
>>-----Original Message-----
>>From: Nick Chalko [mailto:nick@chalko.com]
>>Sent: Friday, January 03, 2003 2:35 PM
>>To: forrest-dev@xml.apache.org
>>Subject: Re: [VOTE] FakeForrest is ready!
>>
>>
>>Robert Koberg wrote:
>>
>>
>>
>>>What does docbook have to do with a website?
>>>
>>>
>>>
>>docbook has to do with presenting technical information. a website is
>>one way to present technical information.
>>
>>
>>
>>
>>
RE: [VOTE] FakeForrest is ready!
Posted by Robert Koberg <ro...@koberg.com>.
Hi,
Docbook deals with technical _books_ (OReilly, specifically??). A website is not
a book. Why try to fit a square peg in a round hole?
best,
-Rob
> -----Original Message-----
> From: Nick Chalko [mailto:nick@chalko.com]
> Sent: Friday, January 03, 2003 2:35 PM
> To: forrest-dev@xml.apache.org
> Subject: Re: [VOTE] FakeForrest is ready!
>
>
> Robert Koberg wrote:
>
> >What does docbook have to do with a website?
> >
> docbook has to do with presenting technical information. a website is
> one way to present technical information.
>
>
>
Re: [VOTE] FakeForrest is ready!
Posted by Nick Chalko <ni...@chalko.com>.
Robert Koberg wrote:
>What does docbook have to do with a website?
>
docbook has to do with presenting technical information. a website is
one way to present technical information.
RE: [VOTE] FakeForrest is ready!
Posted by Robert Koberg <ro...@koberg.com>.
What does docbook have to do with a website?
-Rob
> -----Original Message-----
> From: Nick Chalko [mailto:nick@chalko.com]
> Sent: Thursday, January 02, 2003 10:11 AM
> To: Ant Developers List; forrest-dev@xml.apache.org; Krysalis Developers
> Subject: Re: [VOTE] FakeForrest is ready!
>
>
> Costin Manolache wrote:
>
> >Regarding conversion:
> >
> >If the new DTD is docbook ( or a subset ): +1 to convert them.
> >If it's yet another private DTD: -1.
> >
> >
> >
> I am not a commiter at apache, but I strongly concur.
>
> R,
> Nick
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [VOTE] FakeForrest is ready!
Posted by Robert Koberg <ro...@koberg.com>.
What does docbook have to do with a website?
-Rob
> -----Original Message-----
> From: Nick Chalko [mailto:nick@chalko.com]
> Sent: Thursday, January 02, 2003 10:11 AM
> To: Ant Developers List; forrest-dev@xml.apache.org; Krysalis Developers
> Subject: Re: [VOTE] FakeForrest is ready!
>
>
> Costin Manolache wrote:
>
> >Regarding conversion:
> >
> >If the new DTD is docbook ( or a subset ): +1 to convert them.
> >If it's yet another private DTD: -1.
> >
> >
> >
> I am not a commiter at apache, but I strongly concur.
>
> R,
> Nick
>
Re: [VOTE] FakeForrest is ready!
Posted by Nick Chalko <ni...@chalko.com>.
Costin Manolache wrote:
>Regarding conversion:
>
>If the new DTD is docbook ( or a subset ): +1 to convert them.
>If it's yet another private DTD: -1.
>
>
>
I am not a commiter at apache, but I strongly concur.
R,
Nick
Re: [VOTE] FakeForrest is ready!
Posted by Nick Chalko <ni...@chalko.com>.
Costin Manolache wrote:
>Regarding conversion:
>
>If the new DTD is docbook ( or a subset ): +1 to convert them.
>If it's yet another private DTD: -1.
>
>
>
I am not a commiter at apache, but I strongly concur.
R,
Nick
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [VOTE] FakeForrest is ready!
Posted by Costin Manolache <cm...@yahoo.com>.
Christoph Wilhelms wrote:
> [1] We want to use Forrest for ant.apache.org (because it is soooo nice
> [;))
Neutral 0.
> [2] Use the FakeForrest Anakia/Velocity template to generate the site
> [until
> we converted the xdocs xmls to the forrest dtd and the project.xml into a
> book.xml.
Regarding conversion:
If the new DTD is docbook ( or a subset ): +1 to convert them.
If it's yet another private DTD: -1.
> [3] Probably stick to the FakeForrest approach until Forrest itself offers
> bixed headers (referring to Nicola Ken Barozzi :)).
0.
Costin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [VOTE] FakeForrest is ready!
Posted by Rob Oxspring <ro...@apache.org>.
I'm not a committer in Ant land so none of this is binding but my 2p...
----- Original Message -----
From: "Christoph Wilhelms" <Ch...@impress.com>
To: "'Ant Developers List'" <an...@jakarta.apache.org>
Sent: Thursday, January 02, 2003 9:03 AM
Subject: [VOTE] FakeForrest is ready!
> Hi All!
>
> I have finished the FakeForrest Anakia/Velocity template and committed it to
> the proposal/ant-site/anakia directory. It's something like a "best of both
> worlds" approach (Design from forrest, but added bixed headers, tables and
> source boxes from the current anakia-templates (with some color pushing).
>
> For that reason it's time to come up with a multiple vote/proposal:
>
> [1] We want to use Forrest for ant.apache.org (because it is soooo nice ;))
+1. Admittedly it's quite nice but I'd put the reasons for now being the free and easy access to printable pages and search
facilities. Eventually the integration of various stats and building RSS feeds should be a real bonus too.
>
> [2] Use the FakeForrest Anakia/Velocity template to generate the site until
> we converted the xdocs xmls to the forrest dtd and the project.xml into a
> book.xml.
-0. Ant has ~170kb of xdocs, which doesn't seem a whole lot and I would have thought we could get a reasonable conversion done
quickly enough (especially if a few of us carve up the work) that the benefits of a FakeForrest transition period would be pretty
small. I would expect tweaks, tunings and corrections to follow but the initial conversion should be reletively painless - maybe
you are suggesting some reorg too? this seems to be a separate phase that would be easier after the hassle of conversion is dealt
with. Please shout me down though - I haven't looked at the forrest DTD in depth yet, just observed that it seems to include a
superset of the features used by ant.
>
> [3] Probably stick to the FakeForrest approach until Forrest itself offers
> bixed headers (referring to Nicola Ken Barozzi :)).
Here I'm lost - what's a bixed header? I've googled and eyebrowsed but with no luck, and my eyes aren't spotting the distiction from
the forrest page so I must be looking for the wrong thing:
http://xml.apache.org/forrest/index.html.
If this is a real stumbling block then +1 to a FakeForrest interim period but until then I'll stick to a bemused -0.
Rob
>
> Here is of course my +1 to my complete proposal :).
>
> Happy New Year!
> Chris
>
> P.S.: I've already updated the templates to 2003 and if you want a sneak
> peak youst click here:
> http://cvs.apache.org/viewcvs.cgi/*checkout*/jakarta-ant/proposal/ant-site/anakia/docs/index.html?rev=HEAD&content-type=text/html
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [VOTE] FakeForrest is ready!
Posted by Jeff Turner <je...@apache.org>.
On Mon, Jan 06, 2003 at 11:09:26AM +0100, Stefan Bodewig wrote:
...
> Is Forrest up to it now? I'd seriously consider using it in the
> future, though.
When Forrest doesn't suck, we'll let the world know with a 1.0 release :)
A prime requirement for non-suckiness is "don't force a specific DTD on
users". In the meanwhile, lurking Forresters will gladly help any
project wishing to get their feet wet, and would value any feature
suggestions.
http://nagoya.apache.org/wiki/apachewiki.cgi?ForrestFeatureRequests
--Jeff
> Stefan
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [VOTE] FakeForrest is ready!
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 2 Jan 2003, Christoph Wilhelms
<Ch...@impress.com> wrote:
> I have finished the FakeForrest Anakia/Velocity template and
> committed it to the proposal/ant-site/anakia directory.
Cool. The only thing I don't like is that <subsection>s don't render
as prominently as they did before. See the contributors page, in
Mozilla 1.2.1 there is no visual difference between "Active Members"
and "Bruce Atherton".
We used to render subsections like the questions in the FAQ (i.e. a
lighter shade of blue than a section) and I liked that.
Yet another nit, there seems to be a spacing issue, the table with Ant
versions in the FAQ and the following "I get checksum errors" are too
close to each other IMHO.
> For that reason it's time to come up with a multiple vote/proposal:
>
> [1] We want to use Forrest for ant.apache.org (because it is soooo
> nice ;))
Is Forrest up to it now? I'd seriously consider using it in the
future, though.
> [2] Use the FakeForrest Anakia/Velocity template to generate the
> site until we converted the xdocs xmls to the forrest dtd and the
> project.xml into a book.xml.
I like the new layout, but then I have a tradition of not voting on
graphics issues 8-)
> [3] Probably stick to the FakeForrest approach until Forrest itself
> offers bixed headers (referring to Nicola Ken Barozzi :)).
Whatever boxed headers may be ...
> P.S.: I've already updated the templates to 2003 and if you want a
> sneak peak youst click here:
Or go to ant.apache.org directly ;-)
Stefan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>