Re: Good job! / Re: Integration of TIFFRenderer in FOP

Thanks to Glen for raising the issue. The ideal approach is if Oleg would pack up his TIFFRenderer and donate it to the ASF accompanied with a software grant [1], but Oleg is a FOP committer and has a CLA on file. So if Oleg attaches a ZIP with the sources for the TIFFRenderer (ALv2 already applied

Re: Integration of TIFFRenderer in FOP

Relationship to which PDF renderer? The one that directly creates PDF (PDFRenderer) or the one that creates PDF through JPS (normal PrintRenderer as defined in the Wiki painting to a Graphics2D instance provided by JPS) using a StreamPrintService? That's the two choices. Obviously, you will be tak

Re: cvs commit: xml-fop/src/java/org/apache/fop/render/awt/viewer PreviewDialog.java

No. It's quite ok like this. It is in line with my vision how renderers should be made available to FOP in the future (dynamic registration like the FOP extensions). It's clear that the AWT preview doesn't manifest a certain type of file that has an officially defined MIME type. But nobody is block

Good job! / Re: Integration of TIFFRenderer in FOP

Glen, Thanks for your mail. It's good you raised the legal issue. Peter, let me answer you last mail [1] here: You are right that the wiki is still vague about the detailled implementation of the different renderers. Actually, I haven't started to think about it until today. I will put my ideas

Re: cvs commit: xml-fop/src/java/org/apache/fop/render/awt/viewer PreviewDialog.java

The "application/awt" MIME type doesn't exist. I think Jeremias wanted this to be null instead for output types that lack a MIME type, correct? Thanks, Glen --- [EMAIL PROTECTED] wrote: > > +/** The MIME type for AWT-Rendering */ >public static final String MIME_TYPE = > "applicati

Re: Integration of TIFFRenderer in FOP

Yeah, Peter makes me want to do that sometimes myself... ;) Glen --- vivek gupta <[EMAIL PROTECTED]> wrote: > How to leave this group. Please help me to > unsubscribe. > > > > --- "Peter B. West" <[EMAIL PROTECTED]> wrote: > > Renaud Richardet wrote: > > > Oleg, > > > > > > I'm currently wo

Good job! / Re: Integration of TIFFRenderer in FOP

Team, Oleg's TIFF Renderer is under the Mozilla license[1], not the Apache one (also apparently some of the code is from Sun?). Is the former compatible with the latter? If not, I would like Oleg to switch the license on it before we proceed further in putting it into FOP. Renaud--thanks for yo

Re: Integration of TIFFRenderer in FOP

Send an e-mail to: [EMAIL PROTECTED] Be sure to use the e-mail address from which you subscribed. On Mar 8, 2005, at 4:03 PM, vivek gupta wrote: How to leave this group. Please help me to unsubscribe. --- "Peter B. West" <[EMAIL PROTECTED]> wrote: Renaud Richardet wrote: Oleg, I'm currently workin

Re: Integration of TIFFRenderer in FOP

How to leave this group. Please help me to unsubscribe. --- "Peter B. West" <[EMAIL PROTECTED]> wrote: > Renaud Richardet wrote: > > Oleg, > > > > I'm currently working on the AWTRenderer. The > basic idea is to create > > a Java2DRenderer which provides the (abstract) > technical foundation. >

Re: Integration of TIFFRenderer in FOP

Renaud Richardet wrote: Oleg, I'm currently working on the AWTRenderer. The basic idea is to create a Java2DRenderer which provides the (abstract) technical foundation. Other renderers can subclass Java2DRenderer and provide the concrete output paths [1]. I think it would be a good idea to integrat

Re: Skype-conference on page-breaking?

Jeremias Maerki wrote: > Luca, do you think your total-fit approach may be written in a way to > handle changing available IPDs and that look-ahead can be disabled to > improve processing speed at the cost of optimal break decisions? I think that a first fit algorithm could be implemented in two

Re: Integration of TIFFRenderer in FOP

Renaud Richardet wrote: I'm currently working on the AWTRenderer. The basic idea is to create a Java2DRenderer which provides the (abstract) technical foundation. Other renderers can subclass Java2DRenderer and provide the concrete output paths [1]. I think it would be a good idea to integrate your

Re: Integration of TIFFRenderer in FOP

On Mar 8, 2005, at 7:23 AM, Renaud Richardet wrote: I think it would be a good idea to integrate your TIFFRenderer, as you propose in [2]. Would you like to integrate it yourself? Otherwise I would like to do it. I think that would be great! Just be careful when you do, that the output isn't res

Integration of TIFFRenderer in FOP

Oleg, I'm currently working on the AWTRenderer. The basic idea is to create a Java2DRenderer which provides the (abstract) technical foundation. Other renderers can subclass Java2DRenderer and provide the concrete output paths [1]. I think it would be a good idea to integrate your TIFFRenderer, a

DO NOT REPLY [Bug 32612] - [PATCH] refactoring of knuth line breaking code.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

RE: DO NOT REPLY [Bug 33760] New: - [Patch] current AWTRenderer

Renaud Richardet wrote: > > 1. FOray has factored the FOP font logic into a separate module, > > cleaned it up significantly, and made some modest > improvements. A few > > weeks ago, I aXSL-ized it as well, which means that it is > written to a > > (theoretically) independent interface: > >

Re: DO NOT REPLY [Bug 33760] New: - [Patch] current AWTRenderer

Thanks for integrating my patch in FOP. > > But how can I get an awt.Image from a FopImage? > > I've modified your patch to demonstrate, but it needs some additional > work to handle the different color models. Probably the image package > should be extended to provide the necessary information/

Re: DO NOT REPLY [Bug 33760] New: - [Patch] current AWTRenderer

By the way, Renaud, you should sign and send an ICLA (Individual Contributor license agreement) to the ASF if you haven't done so already. http://www.apache.org/licenses/#clas Just so we're on the safe side. After all you're not just doing little bug fixes. Thanks! Jeremias Maerki

DO NOT REPLY [Bug 33760] - [Patch] current AWTRenderer

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: DO NOT REPLY [Bug 33760] New: - [Patch] current AWTRenderer

On 08.03.2005 03:18:21 Renaud Richardet wrote: > On Mon, 28 Feb 2005 , Jeremias Maerki wrote: > > > > AbstractRenderer: I moved what I could reuse from PDFRenderer to > > > AbstractRenderer: renderTextDecorations(), handleRegionTraits(), and > > > added the > > > needed empty methods. > > > >