Re: Preview for a general XSL-FO processing API

2004-11-28 Thread Jeremias Maerki
I've uploaded the sources (ALv2) to http://www.maerki.org/jeremias/dev/jafop/ In the meantime, I've improved a few things: - javadocs improved a bit - added support for specifying a userconfig.xml file for the FOP maintenance branch implementation (through FOProcessorFactory.setAttribute("userconf

Re: Preview for a general XSL-FO processing API

2004-11-28 Thread Jeremias Maerki
Hi Victor On 27.11.2004 16:53:54 Victor Mote wrote: > I looked at the doc, and I think this is all pretty useful. I'd like to > spend some more time on it later, and I think I will probably write a FOray > implementation after I get 0.2 released. Here are some preliminary thoughts: I finally down

Re: Preview for a general XSL-FO processing API

2004-11-27 Thread The Web Maestro
This all sounds great to me. I like the sound of it very much. As for the javadocs stuff, there's ongoing discussion on the Forrest DEV list[1] which discusses 'RAW' files (the category in which Javadocs fall). Since that isn't ready yet, perhaps we'll have to go for some other javadocs imp

RE: Preview for a general XSL-FO processing API

2004-11-27 Thread Victor Mote
Jeremias Maerki wrote: > I've talked about it before, so in case anybody is interested > I've uploaded the Javadocs [1] for a general XSL-FO > processing API I've been working on during the last few > weeks. It's basically my API proposal that is (or rather was) > on the Wiki. I've called it J

Re: Preview for a general XSL-FO processing API

2004-11-27 Thread Jeremias Maerki
I'm extremely sorry about not making it clearer that I don't intend to launch a new API discussion for FOP or that I don't want to force anyone to do anything. This JAFOP thing is just a personal project I thought others might be interested in. Thank you for your suggestions. However, I don't thin

Re: Preview for a general XSL-FO processing API

2004-11-26 Thread Glen Mazza
Jeremias Maerki wrote: If there's enough interest I can put the source code for the API plus implementations on my website (or to a SF project or somewhere else). I believe this common API could be interesting in the following months when FOP HEAD advances. It can be used to easily switch implement