bonjour fop-devs
bertrand delacretaz told me you might welcome some help on fop. I
would be pleased to contribute.
*** why fop ***
- i'm very interested in xml and java
- i believe in open-source and wish to contribute to a project
- bertrand told me you were a good team
*** me ***
you can get
jeremias and simon: thanks for your response. now i see better where to look.
i'll follow the maillinglist start to dig in the code.
renaud
bonjour fop-devs
i would like to work on the awt renderer. Mark (or someone else) , are
you working on it?
i checked out the code from FOP 0.20.5. is it the latest maintenance version?
thanks, renaud
On Mon, 17 Jan 2005 10:54:43 +0100, Jeremias Maerki
[EMAIL PROTECTED] wrote:
Hi Mark
We'd
for bringing back the AWT Renderer in CVS HEAD. Renaud and I
met last Friday at lots.ch.
So, Renaud, please use the code found under the fop-0_20_2-maintain
branch for reference. And happy hacking!
On 22.02.2005 05:38:58 The Web Maestro wrote:
On Feb 21, 2005, at 4:55 PM, Renaud Richardet
bonjour fop-dev's
i've been walking through the rendering process. if i understand it
rightly, an area doesn't records it's absolute position. therefore, we
have to pass the currentIPPosition, currentBPPosition all along during
the rendering process to figure out where to position an area.
what i
hello Jeremias
merci for the informations.
I wondered about that, too:
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]by=threadfrom=984481
interesting!
Victor,
in [1] you talked about dealing with the positioning of areas during
the AreaTree building. could you point me to the classes
Glen Mazza [EMAIL PROTECTED] wrote:
Looks good! Now whether you wish to do this before or
after Renaud moves the logic over is up to you two.
There's advantages/disadvantages to either method.
yes, that looks good!
Jeremias, if it's ok for the team, i would apreciate if you would do
the
Victor,
thanks for your explanations. i'll give a look into FOray when i'll
feel more confident about the layout process.
cheers, Renaud
Glen,
We can do it this way. But on second thought, I think
it would be better for Renaud to move it in as
AWTRenderer, and slowly start factoring out more and
more while things are getting settled. BTW, this will
take some time to do anyway--it isn't easy because the
renderers are so
Victor and Jeremias, thanks for your Inputs.
Victor, I've checked out your aXSL. I'll study it and come back to you
if I have questions.
Jeremias wrote:
Speaking of startVParea(), could we rename it to something more meanigfull?
Proposition: TransformPosition, or something like this.
I would be please to listen.
Renaud
Vincent Hennebert wrote:
By looking for this reference, I found the following article:
www.pi6.fernuni-hagen.de/publ/tr234.pdf
It's entitled 'On the Pagination of Complex Documents' (actually it's also
referencing Plass).
There's another article, where the top level of the algorithm is
I worked on my patch and tried to integrate you inputs. There are
still many issues, but I think the basic structure is OK. You can find
a patch attached to bug 33760.
Comments inline:
On Mon, 28 Feb 2005, Victor Mote wrote:
1. FOray has factored the FOP font logic into a separate module,
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
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,
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
Peter,
Then my comment gave you a wrong impression: the Java2DRenderer is the
(abstract) base for all renderers that use the Java2D API for
rendering. The reference renderer is still the PDFRenderer, which
inherits from AbstractRenderer directly.
Renaud
I downloaded sun's codecs [2] that Oleg used in his TIFFRenderer.
Jeremias, you mean that we can legally just put those in the FOP-code?
Following codecs are included in [2]:
- TIFF
- JPEG
- PNG
- BMP
So it should be possible to create a renderer for each of this file
formats. But do we need them
Let me sum up this tread to see if I get the picture:
* Sun's codec [1] will not be integrated.
* instead, Batik's transcoders will be used [2].
* where and how these transcoders will be made available to fop will
be discussed next week [3]
* I'll start by implementing basic functionalities for
19 matches
Mail list logo
