Re: FOP Web Site Update

2004-11-07 Thread Clay Leeds
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 - #66), but I think the
contrast is subtle without being brash. Would you prefer #ff?
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 - [EMAIL PROTECTED]
Webmaster/Developer - Medata, Inc. - http://www.medata.com/
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc


Re: FOP Web Site Update

2004-11-06 Thread Clay Leeds
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 - #66), but I think the 
contrast is subtle without being brash. Would you prefer #ff?

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 - [EMAIL PROTECTED]
Webmaster/Developer - Medata, Inc. - http://www.medata.com/
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc


Re: FOP Web Site Update

2004-11-05 Thread Clay Leeds
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 - [EMAIL PROTECTED]
Webmaster/Developer - Medata, Inc. - http://www.medata.com/
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc


Re: FOP Web Site Update

2004-11-05 Thread Glen Mazza
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

2004-03-07 Thread Glen Mazza
Nice job, Clay--I'm very happy with the whole site PDF in particular.

Jeremias, would you please request write access for Clay now?

Thanks,
Glen
Clay Leeds wrote:

I thought you'd like to see a brief update on the FOP web site trials 
and tribulations. I've uploaded the web portion of the output of a 
forrest run here:

  http://homepage.mac.com/webmaestro/xml-fop_site/site/index.html

Of special note:
- Breadcrumb Trail
believe it or not, the breadcrumb is actually working as it is 
supposed to (yeah!), and we should soon have the problem fixed on our 
site. It looks funny, because it's in the 
/webmaestro/xml-fop_site/site/ path (and each dir/ leaves a 
'breadcrumb'). This problem can be easily fixed, by merely uploading a 
new version of the breadcrumb.js file.

- Whole Site HTML
- Whole Site PDF
kinda self-explanatory... :-)
I'm still having issues with 'forrest' BUILD FAILED errors that I keep 
banging my head against. We're almost there, though (I can almost 
smell it!). Many of the errors relate to such things as having forrest 
pass through files untouched (like *.svg), and how to deal with them. 
I've also had problems with our left-side navigation on the 
Development, Design  Alt Design tabs. Those problems mainly relate to 
pages which are linked in multiple tabs (Development  Alt Design tabs 
each have some Design links in there navigation links on the left). 
It might be easier to re-think that system (which is confusing, and 
IIRC gave Victor some headaches when he was doing this).

On a somewhat related note, I'd also like to update the FO templates 
used to create the PDFs for Forrest, as I believe they provide too 
much margin all around (read extra reams of paper printer when ever 
printing is initiated). Almost there!

Web Maestro Clay