RE: Setup code in Driver

2003-12-22 Thread Victor Mote
Peter B. West wrote: > You have as yet only Glen's opinion about your pioneer LS proposal. It > might be worthwhile to wait for others to express theirs. I don't remember the technical rule for the mathematics of accepting proposals, but with the size of our group, a -1 from anyone pretty much k

Re: Setup code in Driver

2003-12-21 Thread Peter B. West
Victor Mote wrote: Glen Mazza wrote: --- Victor Mote <[EMAIL PROTECTED]> wrote: ... You've mentioned before, I believe, there was some things you wished to do to improve the fonts. That may be good--because most of us have not researched them. The font work has to get thrown away. It is usel

RE: Setup code in Driver

2003-12-21 Thread Victor Mote
Glen Mazza wrote: > --- Victor Mote <[EMAIL PROTECTED]> wrote: > > Also, if possible, please let me know what you > > decide. I am evaluating > > in-progress projects right now to determine which > > ones I should finish and > > which ones I should abandon as I exit the project. > > You've mention

RE: Setup code in Driver

2003-12-20 Thread Glen Mazza
--- Victor Mote <[EMAIL PROTECTED]> wrote: > Also, if possible, please let me know what you > decide. I am evaluating > in-progress projects right now to determine which > ones I should finish and > which ones I should abandon as I exit the project. You've mentioned before, I believe, there was so

RE: Setup code in Driver

2003-12-20 Thread Victor Mote
Jeremias Maerki wrote: > > The answer to your question probably lies in understanding how and why > > getContentHandler() is used without also using render(). The > FOTreeListener > > is only needed if the input document is parsed, and in fact is > only needed > > if you want to break out of parsi

Re: Setup code in Driver

2003-12-20 Thread Jeremias Maerki
On 20.12.2003 15:17:52 Victor Mote wrote: > First, my apologies for being so slow to respond. I am trying to clean up > some of this old stuff that I had flagged for followup. I also looked in the > CVS history & source, and it looks like you have not finished this yet. Right. I still got 622 unr

RE: Setup code in Driver

2003-12-20 Thread Victor Mote
Jeremias Maerki wrote (Sent: Saturday, November 08, 2003 8:28 AM) > As you may have seen in the CVS messages I have moved most of the setup > code that was in the render() method to the getContentHandler() method. > This is necessary because not everyone uses the render() methods, > sometimes you

Re: Setup code in Driver

2003-11-13 Thread Jeremias Maerki
On 13.11.2003 19:27:24 Victor Mote wrote: > Jeremias Maerki wrote: > > > Anyway, I've added some basic functionality or API tests some time ago. > > These are called during build IF JUnit is installed in your Ant > > installation. Just copying junit.jar into Ant's lib directory should do > > it.

RE: Setup code in Driver

2003-11-13 Thread Victor Mote
Jeremias Maerki wrote: > Anyway, I've added some basic functionality or API tests some time ago. > These are called during build IF JUnit is installed in your Ant > installation. Just copying junit.jar into Ant's lib directory should do > it. The build will then check if the high-level APIs for Dr

Re: Setup code in Driver

2003-11-13 Thread Jeremias Maerki
On 12.11.2003 19:11:26 Victor Mote wrote: > If we have test cases that need to be run, then we need to document that > process. The last comments I remember (from Keiron, IIRC) were that testing > was hopelessly broken and not yet worth fixing. I know Joerg has a testing > scheme in place, but I t

RE: Setup code in Driver

2003-11-12 Thread Victor Mote
Jeremias Maerki wrote: > I'm not in a fighter mood today so please change getContentHandler() > to something other than public, make sure you check the test cases > regularly, adjust the example code to the new API and keep in mind that > Cocooners will want to migrate their FOPSerializer some day

Re: Setup code in Driver

2003-11-08 Thread Glen Mazza
--- "J.Pietschmann" <[EMAIL PROTECTED]> wrote: > Glen Mazza wrote: > > Well, what is wrong with everyone using the > render() > > method for 1.0? > > Because we sell the FOP processor as a SAX endpoint, > so > that the famous > transformer.transform(source, new SAXResult( >fop.getContentHand

Re: Setup code in Driver

2003-11-08 Thread Jeremias Maerki
I'm not in a fighter mood today so please change getContentHandler() to something other than public, make sure you check the test cases regularly, adjust the example code to the new API and keep in mind that Cocooners will want to migrate their FOPSerializer some day (They use getContentHandler() a

Re: Setup code in Driver

2003-11-08 Thread J.Pietschmann
Glen Mazza wrote: Well, what is wrong with everyone using the render() method for 1.0? Because we sell the FOP processor as a SAX endpoint, so that the famous transformer.transform(source, new SAXResult( fop.getContentHandler())); can be used. Driving processing through SAX events is a major use

Re: Setup code in Driver

2003-11-08 Thread Glen Mazza
--- Jeremias Maerki <[EMAIL PROTECTED]> wrote: > As you may have seen in the CVS messages I have > moved most of the setup > code that was in the render() method to the > getContentHandler() method. > This is necessary because not everyone uses the > render() methods, Well, what is wrong with ever

Setup code in Driver

2003-11-08 Thread Jeremias Maerki
As you may have seen in the CVS messages I have moved most of the setup code that was in the render() method to the getContentHandler() method. This is necessary because not everyone uses the render() methods, sometimes you simply need to have a ContentHandler to send SAX events to. Some of our exa