>If anyone is feeling adventurous, try out the CVS version of Maverick. >Heterogeneous transforms work great!
Excellent! >Yes, we definitely want to put the FOP transform in an opt-fop >package... Jim, would you like CVS access to maintain it? Maybe add a >little documentation or a sample webapp? :-) CVS acccess would be great. I've already expanded FopTransform actually to support all of the output formats fop supports (http://xml.apache.org/fop/output.html) that make sense in a web environment (pdf, postscript, svg, mif, xml, text). AWT says it pops open an AWT window, and print is for printing from the command line, so I left those out. I also left out PCL, but can add it if there is demand. So far I have only got results with pdf and postscript. I'm getting a class not found exception with SVG so I'm probably one of the batik jars. xml and text are both throwing index out of bounds exceptions--I'm pretty sure that is a problem with FOP itself. I don't have Adobe Framemaker, so I can't even test mif. Anyway--I'll keep plugging along--I still need to port it to the new interfaces. Hopefully I'll have a little sample web app and some basic documentation ready this weekend or by early next week. The config changes to support the new outputs are minimal: This will still work and will produce pdf's (pdf is the default): <transform type="fop"/> but now you can also do: <transform type="fop" output="ps"/> valid output options are "pdf", "postscript", "ps" (postscript), "svg", "xml", "txt", "text", and "mif" --jim _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Mav-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mav-user
