Hi, Is there any benefit to using JAI instead of JIMI? What is the instruction for installing JAI so that Oxygen can use it during FO transforms? Sean Wheller __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/
Hello, There are a couple of benefits to using JAI: - faster image processing; - JAI is still maintained by Sun and has many features not present in JIMI (image tiling, regions of interest, deferred execution, etc.), whereas JIMI is a legacy library; - JAI is an extensible API, so you can add new image processing capabilities or plug in your own implementation, although only the Sun's reference implementation is known to work well at this time; But: - Sun's implementation of JAI is not pure Java (it uses native code on Windows, Solaris and Linux but only for performance enhancements). For example Sun provides no Mac OS implementation, which certainly settles the whole issue against including JAI in <oXygen/>. Some users were able to get JAI to run on Mac OS X by downloading the pure Java version of JAI and then placing the jar files in the proper locations but this is explicitly not supported by Sun and is not accelerated to take advantage of the Macintosh architecture. According to Sun's website their JAI implementation has not yet been certified as 100% pure Java application and Sun and Apple are working on an agreement to make a Mac implementation; - JAI cannot be used with FOP versions older than 0.20.5, because these versions were not compiled with JAI support, so it will not work with <oXygen/> version 2.0.4 which includes FOP 0.20.4 (we plan to include the latest FOP version, that is 0.20.5, in the next release of <oXygen/> but we found some image rendering problems with it). This obviates your second question, Sean. Sorry. Regards, Sorin Sean Wheller wrote:
Hi,
Is there any benefit to using JAI instead of JIMI?
What is the instruction for installing JAI so that Oxygen can use it during FO transforms?
Sean Wheller
__________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
--- Sorin Ristache <sorin@sync.ro> wrote:
- JAI cannot be used with FOP versions older than 0.20.5, because these versions were not compiled with JAI support, so it will not work with <oXygen/> version 2.0.4 which includes FOP 0.20.4 (we plan to include the latest FOP version, that is 0.20.5, in the next release of <oXygen/> but we found some image rendering problems with it).
Hi Sorin, What kind of problems I have Apache FOP 0.20.5 installed as an External FO Processor and it seems to be doing a good job. I have tested it under 2.0.4 and 3.0.1, both with good results. I moved to FOP 0.20.5 for SVG support. I asked about JAI, because in 3.0.1 when transforming to FO, FOP messages that JAI is not installed and says that it is trying JIMI instead. So I was thinking that if Oxygen could use the java CLASSPATH variable or another, like JAI_HOME then installation of JAI on Win and Lin would work without a problem. As it stands now I think that Oxy only looks in the lib folder for libraries, if it does not find them it raises an exception. As a general concept I still think that Oxygen needs to be a little more flexible when it comes to replacing parts of the tool chain and additional support libs. Oxygen is still to locked into itself, instead of also being able to accommodate a more distributed operating environment. For example when instances of the different parts that constitute the tool-chain are already installed, Oxygen should be able to reuse those existing processors without having to duplicate them. Libs like JIMI and JAI are not unique to Oxygen, by enabling the IDE to utilize already installed processors and libs, the foot print of the application will be smaller and the application will be more flexible and scalable. Take this example with JAI. If I understand you correctly. As JAI is not a java app, Oxygen cannot use it and even if I install JAI to the JRE folder, Oxygen/Apache FOP will not be able to use it. Yet JAI gives me benefits that I may want to use. Certainly there must be some commercial value attached to provide an IDE that is flexible? Sean Wheller __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/
Can you obtain a PDF file from the attached file (a very short and simple XML document) using FOP 0.20.5 ? It works fine with FOP 0.20.4 and any of several different versions of DocBook XSL but not with FOP 0.20.5 and any of the DocBook XSL versions (including latest version, 1.62.4). Sean Wheller wrote:
--- Sorin Ristache <sorin@sync.ro> wrote:
- JAI cannot be used with FOP versions older than 0.20.5, because these versions were not compiled with JAI support, so it will not work with <oXygen/> version 2.0.4 which includes FOP 0.20.4 (we plan to include the latest FOP version, that is 0.20.5, in the next release of <oXygen/> but we found some image rendering problems with it).
Hi Sorin,
What kind of problems I have Apache FOP 0.20.5 installed as an External FO Processor and it seems to be doing a good job. I have tested it under 2.0.4 and 3.0.1, both with good results. I moved to FOP 0.20.5 for SVG support.
I asked about JAI, because in 3.0.1 when transforming to FO, FOP messages that JAI is not installed and says that it is trying JIMI instead.
Yes, Send to sean.wheller@syspro.com Sean __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/
HI, I can only transform to PDF if the book is removed and root is article. HTML works fine. So I guess that must be a bug in FOP 0.20.5 Have you logged an event at Apache? Sean Wheller __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/
Hi, I already found a workaround in the stylesheets myself and probably we will include FOP 0.20.5 in the next release of <oXygen/>. To use JAI in FO transformations you have to copy jai_core.jar, jai_codec.jar and mlibwrapper_jai.jar in the lib subdirectory of your <oXygen/> installation and add the name of the directory containing mlib_jai.dll and mlib_jai_mmx.dll to the PATH environment variable. Also you have to set up FOP 0.20.5 as an external FO processor. We will think about allowing the user to specify a location where JAI or other tool is already installed on the machine. Regards, Sorin Sean Wheller wrote:
HI,
I can only transform to PDF if the book is removed and root is article.
HTML works fine.
So I guess that must be a bug in FOP 0.20.5
Have you logged an event at Apache?
Sean Wheller
__________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/
--- Sorin Ristache <sorin@sync.ro> wrote:
Hi,
I already found a workaround in the stylesheets myself and probably we will include FOP 0.20.5 in the next release of <oXygen/>.
Thats great. But does that mean that the XSL's shipped will be a modified version of those on docbook.sf.net? I know that the extensions etc. are not bundled. But I always thought that the XSL's were 1:1 the same as those on SF.
To use JAI in FO transformations you have to copy jai_core.jar, jai_codec.jar and mlibwrapper_jai.jar in the lib subdirectory of your <oXygen/> installation and add the name of the directory containing mlib_jai.dll and mlib_jai_mmx.dll to the PATH environment variable. Also you have to set up FOP 0.20.5 as an external FO processor.
Thanks, I will try this and then write a new article for oxygenxml.com. There is already an article on how to install an external FO processor. BTW this also includes an installtion for JIMI. Perhaps if I do a general article on Image Handling and inlcude both JIMI and JAI in one article, it would be better. The FO Processor article could just XREF to this new article.
We will think about allowing the user to specify a location where JAI or other tool is already installed on the machine.
Oh well, one more xmas wish that I can scratch off my list <sigh/>. Maybe next year :-) Sean Wheller __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/
Sean Wheller wrote:
--- Sorin Ristache <sorin@sync.ro> wrote:
Hi,
I already found a workaround in the stylesheets myself and probably we will include FOP 0.20.5 in the next release of <oXygen/>.
Thats great. But does that mean that the XSL's shipped will be a modified version of those on docbook.sf.net? I know that the extensions etc. are not bundled. But I always thought that the XSL's were 1:1 the same as those on SF.
Just a minor modification. Otherwise DocBook documents having an FO tree that contains blank-body sections cannot be rendered to PDF documents with Apache FOP 0.20.5. You already tried that with the very short and simple document I sent you. When a future version of FOP handles blank-body sections correctly or the DocBook stylesheets on SF are made compatible with FOP the stylesheets included in <oXygen/> will be 1:1 the same as the SF ones.
To use JAI in FO transformations you have to copy jai_core.jar, jai_codec.jar and mlibwrapper_jai.jar in the lib subdirectory of your <oXygen/> installation and add the name of the directory containing mlib_jai.dll and mlib_jai_mmx.dll to the PATH environment variable. Also you have to set up FOP 0.20.5 as an external FO processor.
Thanks, I will try this and then write a new article for oxygenxml.com. There is already an article on how to install an external FO processor. BTW this also includes an installtion for JIMI. Perhaps if I do a general article on Image Handling and inlcude both JIMI and JAI in one article, it would be better. The FO Processor article could just XREF to this new article.
A general article on Image Handling would be OK. Regards, Sorin
participants (2)
-
Sean Wheller -
Sorin Ristache