You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by Clay Leeds <cl...@medata.com> on 2004/10/16 21:03:52 UTC
FOP Web Site Update (was Re: cvs commit: xml-fop/src/documentation/content/xdocs news.xml team.xml)
Thanks Glen! I was planning to update the site to indicate Luca's
'promotion'.
Believe it or not, I'm actually about to update the xml-fop web site.
I've been waiting for Forrest 0.6 to be released so that the changes
won't get wiped away when we switch over to it. Unfortunately the
process will involve replacing all files in the xdocs/ directory. I
will need do a DIFF on the files in xdocs/ that changed after August 2
(August 2 is the date I'm using to generate the 0.6 site--it's a long
story of why I pick that date, and the thread can be found in the
forrest-dev/user logs).
My intention is to bring xml-fop up-to-date next week (I'll be out of
town this weekend).
Speaking of which, does anyone know when xml.apache.org will be updated
to forrest-0.6? I guess that's a question for either
dev@forrest.apache.org or infrastructure@...
If anyone has any questions (or the command to diff all files in the
xdocs/ path after August 2), that would be great!
Web Maestro Clay
On Oct 16, 2004, at 11:44 AM, gmazza@apache.org wrote:
> gmazza 2004/10/16 11:44:32
>
> Modified: src/documentation/content/xdocs news.xml team.xml
> Log:
> Moved Luca to the committer's list, updated news section.
>
> Revision Changes Path
> 1.21 +6 -2 xml-fop/src/documentation/content/xdocs/news.xml
>
> Index: news.xml
> ===================================================================
> RCS file:
> /home/cvs/xml-fop/src/documentation/content/xdocs/news.xml,v
> retrieving revision 1.20
> retrieving revision 1.21
> diff -u -r1.20 -r1.21
> --- news.xml 24 Apr 2004 19:37:22 -0000 1.20
> +++ news.xml 16 Oct 2004 18:44:32 -0000 1.21
> @@ -25,6 +25,10 @@
> </header>
> <body>
> <section>
> + <title>8 October 2004 - New Committer</title>
> + <p>Welcome Luca Furini!</p>
> + </section>
> + <section>
> <title>24 April 2004 - New Committer</title>
> <p>Welcome Simon Pepping!</p>
> </section>
>
>
>
> 1.34 +5 -5 xml-fop/src/documentation/content/xdocs/team.xml
>
> Index: team.xml
> ===================================================================
> RCS file:
> /home/cvs/xml-fop/src/documentation/content/xdocs/team.xml,v
> retrieving revision 1.33
> retrieving revision 1.34
> diff -u -r1.33 -r1.34
> --- team.xml 11 Jun 2004 21:04:06 -0000 1.33
> +++ team.xml 16 Oct 2004 18:44:32 -0000 1.34
> @@ -32,6 +32,9 @@
> <li id="cb"><link
> RENAME_FILE_TO_USE_href="mailto:bowditch_chris@hotmail.com">Chris
> Bowditch</link> (CB)
> is a Java/VB Programmer from England.</li>
> <li id="ad"><link
> RENAME_FILE_TO_USE_href="mailto:adelmelle@apache.org">Andreas
> Delmelle</link> (AD)</li>
> + <!-- Luca prefers the mail address with "AT", to stop spam,
> etc. -->
> + <li><link RENAME_FILE_TO_USE_href="mailto:lfurini AT
> cs.unibo.it">Luca Furini</link>
> + is a student of Computer Studies at the University of
> Bologna (Italy)</li>
> <li id="cg"><link
> RENAME_FILE_TO_USE_href="mailto:chrisg@apache.org">Christian
> Geisert</link> (CG)</li>
> <li id="ph"><link
> RENAME_FILE_TO_USE_href="mailto:pherweg@web.de">Peter Herweg</link>
> (PH) is helping to
> integrate the jfor project's RTF support into the
> upcoming FOP 1.0 version.
> @@ -66,9 +69,6 @@
> Newfoundland. While developing a taste for good
> seafood, he still isn't ready
> for seal flipper (even if it's fresh). He is currently
> assisting the FOP
> project on memory and performance issues.</li>
> -<!-- Luca prefers the mail address with "AT", to stop spam, etc. -->
> - <li><link RENAME_FILE_TO_USE_href="mailto:lfurini AT
> cs.unibo.it">Luca Furini</link>
> - is a student of Computer Studies at the University of
> Bologna (Italy)</li>
> </ul>
> </RENAME_FILE_TO_USE_section>
> <RENAME_FILE_TO_USE_section id="founder">
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-cvs-unsubscribe@xml.apache.org
> For additional commands, e-mail: fop-cvs-help@xml.apache.org
>
>
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: FOP Web Site Update (was Re: cvs commit: xml-fop/src/documentation/content/xdocs news.xml team.xml)
Posted by Clay Leeds <cl...@medata.com>.
On Oct 16, 2004, at 2:38 PM, Peter B. West wrote:
> Clay Leeds wrote:
>> If anyone has any questions (or the command to diff all files in the
>> xdocs/ path after August 2), that would be great!
>
> Clay,
>
> In a working directory, try
>
> cvs update
> cvs diff -kk -D 2004-08-02 -u src/documentation/content/xdocs
>
> Peter
Thanks! I'll check that out when I begin the process.
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: FOP Web Site Update (was Re: cvs commit: xml-fop/src/documentation/content/xdocs
news.xml team.xml)
Posted by "Peter B. West" <li...@pbw.id.au>.
Clay Leeds wrote:
> Thanks Glen! I was planning to update the site to indicate Luca's
> 'promotion'.
>
> Believe it or not, I'm actually about to update the xml-fop web site.
> I've been waiting for Forrest 0.6 to be released so that the changes
> won't get wiped away when we switch over to it. Unfortunately the
> process will involve replacing all files in the xdocs/ directory. I will
> need do a DIFF on the files in xdocs/ that changed after August 2
> (August 2 is the date I'm using to generate the 0.6 site--it's a long
> story of why I pick that date, and the thread can be found in the
> forrest-dev/user logs).
>
...
> If anyone has any questions (or the command to diff all files in the
> xdocs/ path after August 2), that would be great!
Clay,
In a working directory, try
cvs update
cvs diff -kk -D 2004-08-02 -u src/documentation/content/xdocs
Peter
Re: FOP Web Site Update
Posted by Clay Leeds <cl...@medata.com>.
On Nov 7, 2004, at 6:46 AM, Glen Mazza wrote:
>>> Clay Leeds wrote:
>>
>> On a related note, IIRC I wanted to change the color scheme to Red -
>> Amber - Green (stop light analogy: No - Partial - Full compliance--I'm
>> aware of the argument about something either being compliant or it's
>> not ;-))
>
> That's fine -- just keep in mind though that one limitation of this
> page,
> not reasonably fixable, is that compliance is ultimately a
> renderer-specific
> issue (i.e., the results of some properties and FO's may be
> implemented in
> some render-types but not yet in others.) So you may not want to go
> overboard on this page, as there is already an overall limitation to
> its
> accuracy. Still, this page has been a useful source of information
> for our
> users, possibly our most-viewed page.
That 'sounds' like something that could be put in the Notes column.
>>> [BTW, If you can change to the bright red color for the mouse-hover
>>> like the Web Services TLP has that would be nice.]
>>
>> Try it now:
>>
>> http://homepage.mac.com/webmaestro/xml-fop/xml-graphics/
>>
>> It's not 'bright' red (it's dark red - #660000), but I think the
>> contrast is subtle without being brash. Would you prefer #ff0000?
>>
>
> Either are fine for me. I don't have much experience with web site
> design,
> so I'll defer to you on these matters.
>
> Glen
Okey doke!
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: FOP Web Site Update
Posted by Glen Mazza <gr...@yahoo.com>.
> > Clay Leeds wrote:
>
> On a related note, IIRC I wanted to change the color scheme to Red -
> Amber - Green (stop light analogy: No - Partial - Full compliance--I'm
> aware of the argument about something either being compliant or it's
> not ;-))
>
That's fine -- just keep in mind though that one limitation of this page,
not reasonably fixable, is that compliance is ultimately a renderer-specific
issue (i.e., the results of some properties and FO's may be implemented in
some render-types but not yet in others.) So you may not want to go
overboard on this page, as there is already an overall limitation to its
accuracy. Still, this page has been a useful source of information for our
users, possibly our most-viewed page.
> > [BTW, If you can change to the bright red color for the mouse-hover
> > like the Web Services TLP has that would be nice.]
>
> Try it now:
>
> http://homepage.mac.com/webmaestro/xml-fop/xml-graphics/
>
> It's not 'bright' red (it's dark red - #660000), but I think the
> contrast is subtle without being brash. Would you prefer #ff0000?
>
Either are fine for me. I don't have much experience with web site design,
so I'll defer to you on these matters.
Glen
Re: FOP Web Site Update
Posted by Clay Leeds <cl...@medata.com>.
On Nov 5, 2004, at 6:41 PM, Glen Mazza wrote:
> Clay Leeds wrote:
>> Well, it didn't happen "next week" or even the week after. Getting
>> the FOP Standards Compliance page[1] up to snuff has been, shall we
>> say... challenging. But I've finally got content (the table of
>> 'compliance'!) displaying.
>>
>> Unfortunately, we're still not there, as the "link" portion (which
>> serves as a veritable "Table of Contents" for the table) is not being
>> generated yet. More importantly, the color-code system isn't working
>> yet, either (the bgcolor is always 'white'). Also, the "Citation"
>> links are not generated either.
>>
>> These should all prove relatively simple to resolve (especially if I
>> had some help from someone who knows how to make that portion work:
>> are you listening Keiron, Glen or Christian ;-) wink!). Or, I could
>> just continue plodding through the muck and see if I can figure it
>> out.
>
> The compliance page is quite difficult to understand, IIRC one needs
> to be fairly knowledgable about Cocoon sitemaps. But I last looked at
> it before I was a committer. I don't think the colors/sorting by
> compliance level are that important, however. The XSL spec lists each
> FO (and property, I believe) in terms of one of three "compliance
> levels"--but we don't need to duplicate that information on this page
> anymore. I think most people go to this page to determine if property
> X or formatting object Y is available, regardless of its listed
> compliance level in the specification.
My intention at this point is to make the page work as well as it did
before. Once that is achieved (and the FO + SVG transformations are
either resolved or workarounds are made) I will put the new site live.
As for the bgcolor of the table-cell I think helps one see,
at-a-glance, the level of compliance. That is an important 'feature' to
have--bordering on showstopper IMO.
On a related note, IIRC I wanted to change the color scheme to Red -
Amber - Green (stop light analogy: No - Partial - Full compliance--I'm
aware of the argument about something either being compliant or it's
not ;-))
> [BTW, If you can change to the bright red color for the mouse-hover
> like the Web Services TLP has that would be nice.]
Try it now:
http://homepage.mac.com/webmaestro/xml-fop/xml-graphics/
It's not 'bright' red (it's dark red - #660000), but I think the
contrast is subtle without being brash. Would you prefer #ff0000?
> One thing perhaps we should change sometime, is to remove/replace our
> leading graphic on our home page [1]. For a newbie to XSL, it looks
> silly: "See with FOP, you need to create 75 lines of XSL in order to
> get one line of output!" Hopefully we will have something better to
> replace it with in the future.
Good idea. I recall being perplexed myself with that. Of course, that
includes the soup-to-nuts information for an entire page, including
page margins and page-sequence. I'm thinking of at least adding an
image to the 'page'.
> Thanks,
> Glen
>
> [1] http://homepage.mac.com/webmaestro/xml-fop/images/document.jpg
Thanks for your comments!
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: FOP Web Site Update
Posted by Glen Mazza <gr...@yahoo.com>.
Clay Leeds wrote:
> Well, it didn't happen "next week" or even the week after. Getting the
> FOP Standards Compliance page[1] up to snuff has been, shall we say...
> challenging. But I've finally got content (the table of 'compliance'!)
> displaying.
>
> Unfortunately, we're still not there, as the "link" portion (which
> serves as a veritable "Table of Contents" for the table) is not being
> generated yet. More importantly, the color-code system isn't working
> yet, either (the bgcolor is always 'white'). Also, the "Citation"
> links are not generated either.
>
> These should all prove relatively simple to resolve (especially if I
> had some help from someone who knows how to make that portion work:
> are you listening Keiron, Glen or Christian ;-) wink!). Or, I could
> just continue plodding through the muck and see if I can figure it out.
The compliance page is quite difficult to understand, IIRC one needs to
be fairly knowledgable about Cocoon sitemaps. But I last looked at it
before I was a committer. I don't think the colors/sorting by
compliance level are that important, however. The XSL spec lists each
FO (and property, I believe) in terms of one of three "compliance
levels"--but we don't need to duplicate that information on this page
anymore. I think most people go to this page to determine if property X
or formatting object Y is available, regardless of its listed compliance
level in the specification.
[BTW, If you can change to the bright red color for the mouse-hover like
the Web Services TLP has that would be nice.]
One thing perhaps we should change sometime, is to remove/replace our
leading graphic on our home page [1]. For a newbie to XSL, it looks
silly: "See with FOP, you need to create 75 lines of XSL in order to
get one line of output!" Hopefully we will have something better to
replace it with in the future.
Thanks,
Glen
[1] http://homepage.mac.com/webmaestro/xml-fop/images/document.jpg
Re: FOP Web Site Update
Posted by Clay Leeds <cl...@medata.com>.
On Oct 16, 2004, at 12:03 PM, Clay Leeds wrote:
> My intention is to bring xml-fop up-to-date next week (I'll be out of
> town this weekend).
Well, it didn't happen "next week" or even the week after. Getting the
FOP Standards Compliance page[1] up to snuff has been, shall we say...
challenging. But I've finally got content (the table of 'compliance'!)
displaying.
Unfortunately, we're still not there, as the "link" portion (which
serves as a veritable "Table of Contents" for the table) is not being
generated yet. More importantly, the color-code system isn't working
yet, either (the bgcolor is always 'white'). Also, the "Citation" links
are not generated either.
These should all prove relatively simple to resolve (especially if I
had some help from someone who knows how to make that portion work: are
you listening Keiron, Glen or Christian ;-) wink!). Or, I could just
continue plodding through the muck and see if I can figure it out.
Finally, there are a bunch of files in alt.design which don't render
content. Considering the fact that alt.design may be moving on to
Defoe[3], that problem may be moot (don't worry, Peter! I intend to
help you get your content working... it just may not be a part of the
new and improved FOP web site 'launch').
For the current state of the FOP web site, you can always point your
browser to:
http://homepage.mac.com/webmaestro/xml-fop/
[1]
http://xml.apache.org/fop/compliance.html
[2]
http://homepage.mac.com/webmaestro/xml-fop/compliance.html
[3]
http://defoe.sourceforge.net/
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>