Re: Antwort: fo wysiwig editor
You might also want to take a look at Scriptura from Inventive Designers (http://www.inventivedesigners.com/scriptura) In short... it's a GUI designer for XSL-FO documents. You can merge XML or JDBC data, add barcodes, use conditions, etc... It's focused on report generation, but you can also use it without specifying data to generate static pages. It's a commercial product but there's a free trial available. Disclaimer: I work for Inventive Designers ;-) - Erik Vanherck - System Programmer Designer Inventive Designers Visit http://www.inventivedesigners.com Visit http://www.iserieslinux.com for Linux on iSeries information ! Phone: +32 - 3 - 8210170 Fax: +32 - 3 - 8210171 Email: [EMAIL PROTECTED] Computers in the future may weigh no more than 1.5 tons. - Popular Mechanics, forecasting the relentless march of science, 1949 |+--- || [EMAIL PROTECTED]| || eln.mpg.de | || | || 09/30/2002 02:05 | || PM | || Please respond to| || fop-dev | || | |+--- ---| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Re: Antwort: fo wysiwig editor | ---| Hi, I checked out XSLfast. It's a nice start. But not advanced enough for professional print in my opinion. Marc - Original Message - From: Oleg Tkachenko [EMAIL PROTECTED] Date: Monday, September 30, 2002 12:50 pm Subject: Re: Antwort: fo wysiwig editor [EMAIL PROTECTED] wrote: Exactly, i wasnt intending to suggest that you guys pick this work up. But this forum seems the best to maybe chat about it and even spin another group off. Plus there is lots of expertise out there and I may have missed a piece of software. btw, guys from jCatalog, which actually developed fop's awt viewer ended up with xslfast, see http://www.jcatalog.com/products/xslfast/index.htm. I cherish a hope *someday* our clumsy awt viewer will grow into a full-fledged xsl editor :) -- Oleg Tkachenko Multiconn International, Israel --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
release 0.20.4 - custom fonts broken
Extract from the Changes file : - BaseDir property is now used for loading custom fonts (Bug #7608) (thanks to Arnd Beissner and Brian O'Kelley) Applying this fix broke some stuff as far as I can tell. Fop ships with a config file that has this property commented out. As a result basedir appears to be null and FOP tries loading fonts with something like nullfonts/metrics/arial.xml which of course does not evaluate to a decent filename. Ok after figuring that out I set the basedir to ./ which is in my case correct for loading fonts. Doing this however breaks SVG cause it tries to set the basedir as the url of the SVGElement causing the following exception to be thrown java.net.MalformedURLException: no protocol: ./ at java.net.URL.init(URL.java:473) at java.net.URL.init(URL.java:376) at java.net.URL.init(URL.java:330) at org.apache.fop.svg.SVGElement.layout(Unknown Source) at org.apache.fop.fo.flow.InstreamForeignObject.layout(Unknown Source) at org.apache.fop.fo.flow.BlockContainer.layout(Unknown Source) at org.apache.fop.fo.flow.Flow.layout(Unknown Source) at org.apache.fop.fo.flow.Flow.layout(Unknown Source) at org.apache.fop.fo.pagination.PageSequence.format(Unknown Source) at org.apache.fop.apps.StreamRenderer.render(Unknown Source) at org.apache.fop.fo.FOTreeBuilder.endElement(Unknown Source) snip A better solution to the font loading problem would be something like a system property I think (eg. if you were to define org.apache.fop.fontbasedir and prepend it to the embedded font filename). At least this solution would allow the font base dir to be specified at runtime which is important for embedding. Erik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
newbie developer questions
I have been playing around with FOP for a few days now and I certainly like it. The entire xsl:fo thing kinda reminds me of LaTeX which I love. But I find the way FOP is build rather difficult to comprehend. Is there someone who can point me to a document or that can explain in some lines what the overal design is. I understand most of the subsections but I have a hard time comprehending the overal process and which classes belong to which part of the rendering process. Thx, Erik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
