RE: [VOTE] Oleg for committer
> I suggest we have a vote for Oleg to be a committer. +1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: FOP developer's style guide? (Was: interface instead of implementation)
> How about using a wiki page [ ... ] +1 -- Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Where to start for an RTF renderer (was: New Developer Sugges tion)
Hi Bertrand, >> . . .anyone who wants to do it will not offend me by going ahead and doing >> it without me. >> . . . > We haven't had too many volunteers lately in this area, so this shouldn't be > a problem. Well, I left mid-afternoon yesterday to deal with a sick child; I've been back in for two hours now, and I'm still 150 emails behind, so I don't know how much time I will find to dedicate to it... > Just make sure to send your patches early, without waiting for your > enhancements to be "finished". This will help coordinating your work with > that of other developers. Will do, as soon as I figure out how to get CVS past my company's new firewall. Problems, always problems. :( -- Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: New Developer Suggestion
> = J.Pietschmann <[EMAIL PROTECTED]> > [ ... ]For working on HEAD, pick an area: > - layout core > - a renderer > - the font subsystem > - API and configuration > - parsing and property resolution > - FO extensions [ ... ] Thanks for the great suggestions. This one message taught me more about the system design than a month's worth of list-reading. And now, it's time to start looking at code. -- Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Where to start for an RTF renderer (was: New Developer Suggestion)
> Yes, we've been talking about structure-based renderers (like RTF and MIF) > vs. layout-based ones (PDF being the focal point) for some time. [ ... ] > 4) My suggestion is to first use the RTF library from jfor in binary form, by > including jfor's jar in the FOP distribution, to create the RTF document from > the StructureHandler events. The current jfor code does a similar thing where > the jfor Converter (jfor/jfor/converter/Converter) uses SAX events to drive > the jfor RTF library. This makes sense, and I will start looking at it. But, as I said up front, nobody should count on my being able to accomplish this, and anyone who wants to do it will not offend me by going ahead and doing it without me. -- Scott .sig wanders off, mumbling something about learning CVS. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: New Developer Suggestion
> = Bertrand Delacretaz <[EMAIL PROTECTED]> >> = Scott Sauyet <[EMAIL PROTECTED]> >> Does anyone have a suggestion about something I could look at fixing / >> enhancing which is not mission-critical, but which might give me a chance >> to look at a fair bit of the code? > The integration of jfor (www.jfor.org) as a structure renderer for RTF > documents is still waiting for someone to jump in. If you have good java > skills and want to tackle this one we can certainly help you find your way. I expect my Java skills are up to the task. This is all J2SE, right? I have no experience with J2ME, and only a little with J2EE. I don't really have a sense of the charter of FOP. I know that there is a an AWT Renderer as well as the PDF converter, but is that meant more as a testing system than as something critical to the central project? Or do I misunderstand? So is integrating other renderers something that the group would eventually like to do? For me, that would be a real plus, as I'm hoping to eventually work with PDLs for high-volume printers. > But note that this part of FOP is not at all related to PDF layout, fonts, > etc., it's a fairly different way of rendering documents. As of today, I know nothing about PDF syntax and little about RTF. I figure I'm going to have to learn both. I understand FO fairly well, and I speak Java fairly fluently. What do you think is first priority? So how would we expect this to integrate. What user code would change to generate an RTF document rather than a PDF one? And as to mechanics, what code should I start with? Thanks for any info, -- Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: New Developer Suggestion
Me: > So what I was hoping for is a suggestion for something that I can work > on that might be useful, but not critical to any immediate plans, > ideally something that overlaps little with currently active portions of > the project. There were no replies yesterday. Does anyone have a suggestion about something I could look at fixing / enhancing which is not mission-critical, but which might give me a chance to look at a fair bit of the code? Thanks, -- Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
New Developer Suggestion
Hi, my name is Scott Sauyet, a Java developer in Connecticut, USA. I'm new to this group. I've been reading for about a month, but have made no contributions yet. I would like to contribute. Eventually, I hope to understand the system well enough to produce a spin-off which could render output for high-volume printers, in Xerox Metacode, AFP, or some such; this would be very useful for my industry. First, obviously, I have to learn how it all works. I'm looking for a suggestion. When trying to learn a system, I usually find it easiest to have some task, some project that would improve the product. I don't want to assign any work to myself from the bug list. I don't know how much time I can dedicate to it, and I don't want anyone thinking something is being actively worked on when it's not clear if I can deliver or when it might be ready. So what I was hoping for is a suggestion for something that I can work on that might be useful, but not critical to any immediate plans, ideally something that overlaps little with currently active portions of the project. If you have any ideas, please let me know, either on or off the mailing list. Thanks, -- Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
