Re: AW: manual with css
[EMAIL PROTECTED] wrote: What do people think about this? first look is good, some differences, but I have to look deeper into that. One difference is that the lines in the tables are not changed - I did not want to modify the html files much. Another difference is that I put a background to pre sections to make the examples standout a little. (comparing echo-css with subant) Is ee like a soft grey? yep. RGB 00=black FF=white The generated docs are generated from the xdocs right? no. Java-Sources --XDoclet-- HTML This is nearly correct, however examples (if present) and other sections are provided in the xdocs. Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: manual with css
[EMAIL PROTECTED] wrote: What do people think about this? first look is good, some differences, but I have to look deeper into that. (comparing echo-css with subant) Is ee like a soft grey? yep. RGB 00=black FF=white The generated docs are generated from the xdocs right? no. Java-Sources --XDoclet-- HTML First shot of autogenerating the manual from the sources (somewhere in the proposal section) As an aside, I'm converting the current html in docs/manual to docbook format, (copying them, renaming them as foo.xml and then replacing all the damn tags), Lot of work - but with a future? Well I'll continue doing it, as I'm really into the docbook format now, it's just so clean! I dont want to keep you doing that (it seems that you like doing that :) but we should port that to a more solid base. Which means: supported by the Ant team. ATM the manual is written in HTML. Our vision is writing the manual inside the java sources and generate the readable form via XDoclet. One of the ideas was *.java --XDoclet-- *.xml --Forrest-- *.html, *.pdf and let Forrest do creating a complete Ant manual as one pdf file using its aggregate facility. Ok, XDoclet would indeed rock to extract documentation from inside the source. Forrest, sorry I thought that was for websites (sort of like velocity), but I haven't studied it properly. When I've finished (and it's not as manual as it would first appear, although I could do with a transform html tables into docbook tabels script), the manual will be entirely in xml which can then be converted with a style task into html, pdf (via fop) or whatever. and I'm finding more than a few unclosed tags, spelling mistakes etc. report them :-) I'm fixing them as I transfer the html to xml, but I'm not fixing the original html (doh!) Kev - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: manual with css
I found another style:
/* first row */
table tr:first-child td {
background-color: cc;
color:00;
}
which uses a pseudo-class selector [1] of CSS 2.1. The table header in
subant
has this special colors, but the old manual (javac) has only a
tabletrtdb so
it´s difficult to select the cells. Works with Firefox 1.0, IE 6.0 ignores
that.
By searching I found two interesting resources: CSS hacks browser
detection [2] with
nice infos and links and browser support - Selectors [3] which lists the
browsesr and
their support of selectors (other features in separate tables linked there).
Jan
[1] http://www.w3.org/TR/CSS21/selector.html#first-child
[2]
http://www.webcredible.co.uk/user-friendly-resources/css/hacks-browser-detec
tion.shtml
[3]
http://www.westciv.com/style_master/academy/browser_support/selectors.html
-Ursprüngliche Nachricht-
Von: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Gesendet am: Montag, 7. März 2005 13:53
An: [EMAIL PROTECTED]
Betreff: Re: manual with css
On Mon, 07 Mar 2005, Peter Reilly [EMAIL PROTECTED] wrote:
I have been looking at using a little css to make the hand-made ant
manual pages look a bit like the generated ant manual pages.
+1
I would like to add a reference to the css file for
the non-generated pages. It probablly should be
a different stylesheet file that the antmanual.css as
that one should also be used by the generated pages.
Wouldn't it be cleaner to
(1) add that to antmanual.css
(2) make the xdocs proposal reference antmanual.css
(3) make the xdocs proposal not create any bgcolor attributes or
font elements at all
?
I don't know enough about the inner workings of the xdocs proposal to
know how easy (2) and (3) would be, though.
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: manual with css
[EMAIL PROTECTED] wrote:
I found another style:
/* first row */
table tr:first-child td {
background-color: cc;
color:00;
}
which uses a pseudo-class selector [1] of CSS 2.1.
I would rather not use stuff that needs modern versions of
browers.
The table header in
subant
has this special colors, but the old manual (javac) has only a
tabletrtdb so
it´s difficult to select the cells.
We could change the td to th for the first row (by a script). But the
current bolding by hand should be enough.
Peter
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
AW: AW: manual with css
I agree it would be better not to rely on modern features. But older browser
just ignore that so it would be just an extra. And IMO this is only an
iterim
because of the autogen-stuff.
Jan
-Ursprüngliche Nachricht-
Von: Peter Reilly [mailto:[EMAIL PROTECTED]
Gesendet am: Montag, 7. März 2005 15:41
An: Ant Developers List
Betreff: Re: AW: manual with css
[EMAIL PROTECTED] wrote:
I found another style:
/* first row */
table tr:first-child td {
background-color: cc;
color:00;
}
which uses a pseudo-class selector [1] of CSS 2.1.
I would rather not use stuff that needs modern versions of
browers.
The table header in
subant
has this special colors, but the old manual (javac) has only a
tabletrtdb so
it´s difficult to select the cells.
We could change the td to th for the first row (by a
script). But the
current bolding by hand should be enough.
Peter
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: manual with css
Kev Jackson wrote: ... Forrest, sorry I thought that was for websites (sort of like velocity), but I haven't studied it properly. ... When I've finished (and it's not as manual as it would first appear, although I could do with a transform html tables into docbook tabels script), the manual will be entirely in xml which can then be converted with a style task into html, pdf (via fop) or whatever. That's what Forrest does. Forrest now can generate a site using html as a source, even dirty html (it uses jtidy), so *if* the idea is to go with Forrest, I'd just not do the task of converting all the docs. Besides, pure html is much easier to edit, as any decent html editor may do. -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: AW: manual with css
[EMAIL PROTECTED] wrote: I agree it would be better not to rely on modern features. But older browser just ignore that so it would be just an extra. And IMO this is only an iterim because of the autogen-stuff. Yes, but I think that the autogen stuff should use css, and in that case the css should be as simple as possible. Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
