I'm simply forwarding this to you guys. Clay, would you please try to
take care of this for the FOP website?
Is there anyone from our two projects who will be there?
(Without the right president in place and without someone paying for a
ticket to fly over, I won't be there. ;-) Looking forward
Hi FOP devs,
I' ve developed a form extension for XSL-FO for an university project.
It's an extension to FO like the fox extensions. With it you can declare
and define the usual form elements like edit fields, radio buttons,
check boxes, combo boxes, list boxes, comment fields and buttons.
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project xml-fop has an issue affecting its community integration.
This issue affects 1
Hello Fopsters,
I have attached first phase (a working example) of the refactoring I was
talking about in my previous mails. Please let me know, if this change is
acceptable for you. If it is, I will finish it afterwards.
Change description:
1) new interface: org.apache.fop.area.AreaFactory
I'd rather we have pluggable LayoutManagers -- 1.0's
emphasis and I think our previous agreement with
Finn/Simon -- than have pluggable Area objects (where
much of layout used to be in 0.20.5.) I'm not sure if
Fop can realistically handle both at this time.
As for complexity, in our LM's, with
Current source code does not compile under J2SE 5 due to the use of variables
called enum. This is now a reserved word.
These errors are inside the org.apache.fop.render.rtf package.
thank you
--
bobby abraham
