Frankly, migrating this kind of extension could be a problem. But I'm not sure. At any rate, there's no "layout()" method anymore and the FO tree itself had a few changes, too. If I were you I wouldn't implement something like that as a FOP extension but as a generic, SAX-based pre-processor which is independent of the FO processor. That would make the thing much more versatile.
On 30.05.2006 13:13:16 Raphael Parree wrote: > > The extension performs syntax checking and color highlighting of various > languages (JAVA, JSP, HTML, XML, SQL, HQL, EJBQL etc). It does not generate > SVG, but produces FO where it changes the font attributes. > > It extends the FObj and relies on the layout method to call an addText > method for each token. I can't recall from which example I obtained the > skeleton code (especially the addText method). Do you think it will be an > easy transition? I have been postponing the move, but am aware that one day > I will have to make it ;) > > > > > > -----Original Message----- > From: Jeremias Maerki [mailto:[EMAIL PROTECTED] > Sent: 30 May 2006 12:40 > To: fop-users@xmlgraphics.apache.org > Subject: Re: LazyFont NullPointerException > > The extension API has been stable for a while. A few months ago I've > added some additional gadgets I needed for Barcode4J. I don't expect any > major changes anymore. Backwards-incompatible changes are highly > unlikely, but no guarantees. > > So far, there's no documentation for writing extensions. I usually point > people at Barcode4J as the prime example. :-) The examples directory in > the distribution (MathML and plan extensions) can also help. > > The migration shouldn't be too difficult. A few things have changed but > most of your custom code can stay the same. I'm pretty confident that > you can do the migration in 2 or 3 hours max if your extension simply > generates SVG. > > Now, I'm curious: What kind of extensions did you implement? > > On 30.05.2006 11:57:13 Raphael Parree wrote: > > Hi, > > > > I would like to move to 0.92beta, but have so far been reluctant to make > the > > move due to the FOP extension we have written. Is it safe to start porting > > the extensions (IOW is the extension API stable?). Is there documentation > > available on writing extensions for the new release (or even better on how > > to migrate your extensions?) > > > Jeremias Maerki > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
