Hi Vincent, thanks for your reply. As there is nothing explicit defined on the roadmap, what do you think about a general interface for replacing the pdf renderering library? We defenetly will work internally on the PDF-Export and I think if we spend time on this, we could do it in a way the community could profit of. So what's your oppinion? How could the design be? Thanks Josef -- View this message in context: http://xwiki.475771.n2.nabble.com/Using-a-commercial-pdf-rendering-library-… Sent from the XWiki- Users mailing list archive at Nabble.com.

Hi Vincent, we now took a look at the following code and a few questions came up. First of all how should the renderer interface be embedded? What name do you suggest for the new component? Which injections and annotations are needed (e.g. what kind of information includes the @Named(…) annotation)? Are there any documents where we can read something about that? Where will be defined after which implementation class of the pdf library is searched in service of the injection? Maybe in the xwiki.cfg? In that context another question is where is defined which implementation of the class PrintRendererFactory will be injected? Will the currently used PDFExport interface be obsolete by that? Should the BlockRenderer interface either be implementated directly or has it to be inherited of the AbstractBlockRenderer class? Concerning the following code: We would suggest to insert a check in the export-method to determine if a custom pdf library is configured (e.g. in the xwiki.cfg) or not. If yes it'll be used, if not the standard export remains in force. -- View this message in context: http://xwiki.475771.n2.nabble.com/Using-a-commercial-pdf-rendering-library-… Sent from the XWiki- Users mailing list archive at Nabble.com.

Sorry this was a little misleading, I meant custom pdf export implementation, which uses any pdf rendering library for example iText. vmassol wrote -- View this message in context: http://xwiki.475771.n2.nabble.com/Using-a-commercial-pdf-rendering-library-… Sent from the XWiki- Users mailing list archive at Nabble.com.

Hi Vincent, we put down a design propsal for this one here http://dev.xwiki.org/xwiki/bin/view/Design/ExportActionadaptation <http://dev.xwiki.org/xwiki/bin/view/Design/ExportActionadaptation> . We would be happy if you take a look at it and tell us what you think. If you are happy, I'll will create a jira issue and start implementing. Thanks! Regards Josef vmassol wrote > &gt; wrote: > >> Sorry this was a little misleading, I meant custom pdf export >> implementation, >> which uses any pdf rendering library for example iText. > > ok, good, iText is a good example but it works completely differently than > FOP works. For FOP we use this workflow: > http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Configuration#HCustomiz… > > For iText, it's completely different and you would build iText directly > from the events (no need to generate HTML first, and apply various > stylesheets). > > That's why in this case it would mean 2 completely different Renderers. > > Regarding hints, we could have as names: > > "fop/1.0" > "itext/1.0" > > Thanks > -Vincent > > PS: Note that using iText means shortcomings ATM, see > http://jira.xwiki.org/browse/XRENDERING-147# > >> >> >> vmassol wrote >>> Before answering your questions below I need to know what you mean by >>> "custom PDF library". >>> >>> Thanks >>> -Vincent >>> >>> On Jul 8, 2013, at 12:14 PM, jhaimerl &lt; >> >>>> >>> &gt; wrote: >>> >>>> Hi Vincent, >>>> >>>> we now took a look at the following code and a few questions came up. >>>> >>>> >>>> >>>> First of all how should the renderer interface be embedded? What name >>>> do >>>> you >>>> suggest for the new component? Which injections and annotations are >>>> needed >>>> (e.g. what kind of information includes the @Named(…) annotation)? Are >>>> there >>>> any documents where we can read something about that? >>>> Where will be defined after which implementation class of the pdf >>>> library >>>> is >>>> searched in service of the injection? Maybe in the xwiki.cfg? In that >>>> context another question is where is defined which implementation of >>>> the >>>> class PrintRendererFactory will be injected? >>>> >>>> Will the currently used PDFExport interface be obsolete by that? >>>> >>>> Should the BlockRenderer interface either be implementated directly or >>>> has >>>> it to be inherited of the AbstractBlockRenderer class? >>>> >>>> Concerning the following code: >>>> >>>> >>>> >>>> We would suggest to insert a check in the export-method to determine if >>>> a >>>> custom pdf library is configured (e.g. in the xwiki.cfg) or not. If yes >>>> it'll be used, if not the standard export remains in force. >>>> >>> >>> _______________________________________________ >>> users mailing list >> >>>> >>>> >> >> >> >> >> -- >> View this message in context: >> http://xwiki.475771.n2.nabble.com/Using-a-commercial-pdf-rendering-library-… >> Sent from the XWiki- Users mailing list archive at Nabble.com. >> _______________________________________________ >> users mailing list >> -- View this message in context: http://xwiki.475771.n2.nabble.com/Using-a-commercial-pdf-rendering-library-… Sent from the XWiki- Users mailing list archive at Nabble.com.