Re: adding fonts to fop applet
Errr--I apologize--I forgot that we had already agreed to use Avalon for configuration [1]. Sorry/Never mind... Glen [1] http://marc.theaimsgroup.com/?l=fop-devm=108337684719819w=2 --- Glen Mazza [EMAIL PROTECTED] wrote: --- Simon Pepping [EMAIL PROTECTED] wrote: - From an app: add a configuration object to the FOUseragent object, Why do you need to drag in the Avalon library for this? For the classes in question, Avalon is just providing a very thin wrapper--can't we do this directly against the JDK? Glen
Meeting Bertrand
Foplings, On Monday last, the 5th, Jenni and I met Bertrand for coffee at Mt Coot-tha, one of the surface irregularities of Brisbane dignified with the name Mountain. It does, however, offer a wonderful view of much of the city and surrounds. Bertrand and family were preparing to depart for a drive up the coast to Cairns, with spot of whale-watching at Hervey Bay. It was peculiarly exciting to meet face-to-face one of my FOP colleagues, and underlines what a strange work environment we inhabit. Here's to good, cheap hypersonic travel. http://www.mech.uq.edu.au/hyper/hyshot/ Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html
Re: Meeting Bertrand
So far, I've met Bertrand and Jörg. No surprise as they live within about 120km of my place. :-) It's really interesting what difference it makes to have someone directly in front of you. Too bad, Skype still doesn't have video conferencing support. Anyone already using a video conference application? Hardware and bandwidth available here. That would be a good work-around until we have cheap hypersonic travel. Still hoping for beaming to become available On 10.07.2004 15:59:09 Peter B. West wrote: Foplings, On Monday last, the 5th, Jenni and I met Bertrand for coffee at Mt Coot-tha, one of the surface irregularities of Brisbane dignified with the name Mountain. It does, however, offer a wonderful view of much of the city and surrounds. Bertrand and family were preparing to depart for a drive up the coast to Cairns, with spot of whale-watching at Hervey Bay. It was peculiarly exciting to meet face-to-face one of my FOP colleagues, and underlines what a strange work environment we inhabit. Here's to good, cheap hypersonic travel. http://www.mech.uq.edu.au/hyper/hyshot/ Jeremias Maerki
Re: [PROPOSAL] API Changes
--- J.Pietschmann [EMAIL PROTECTED] wrote: Glen Mazza wrote: There are two possible API changes I am wondering if we should make. Have another look at the API proposals in the old Wiki. http://nagoya.apache.org/wiki/apachewiki.cgi?FOPAvalonization Well, a bit too expansive for my (personal) tastes, at least for 1.0--but to be candid, much of it I still don't understand. Regardless, the resources we have for 1.0 IMO should be focusing on other areas (fo's/layout/renderers) at this time. Perhaps another reason for my recommendation for a spartan API similar to what we now have for 0.20.5. Our inputs I see for 1.0: --XSL FO document (or xml/xslt) --preferred render type --FOUserAgent and UserConfiguration, whatever portions of functionality/coding in each. That should be enough for us in 1.0, no? Those more elaborate API goals appear best discussed post-1.0, presumably once more vital parts of the system have been addressed. More thoughts, anyone? Simon, what would you be comfortable with API-wise in 1.0? Thanks, Glen
