Adrian, is not a strange question, I've implemented it and works very well.
And in some use cases is a perfect choice.
In my implementation I use a FopPage that declares page#getmarkuptype() {
return "fop"}
The nice thing is that all panel added in that page will look for an
associated markup will a suffix ".fop" (instead of .html).
This means that you can have a panel implementing a common business logic
with two "skins", one html and one fop.
When used in html page it will use the HTML panel and when added in the FOP
page will produce the FOP markup.
Paolo
On Mon, Dec 15, 2008 at 11:14 PM, Adrian Wiesmann <awiesm...@somap.org>wrote:
> Hello everybody
>
> A quick question out of curiosity. Has anybody played around or tried to
> generate XSL-FO from within your Wicket project?
>
> What I mean is this:
>
> - Add an XML file to every HTML file.
> - Tell Wicket to use the XML instead of the HTML file for the markup.
> - Have Wicket do the markup inheritance magic and "rendering" of a FO file
> (instead of plain HTML).
> - Use the resulting FO to render PDF with Apache FOP.
> - Present the PDF file instead the HTML to the client.
>
> Anyone did so? Anyone played with Wicket and did so in a Swing application
> (instead the web environment)?
>
> I know, these questions may sound strange, but I am currently thinking
> about the possibilities of Wicket's markup inheritance and if it is
> possible (and makes sense) to use Wicket as a reports generator. Not what
> it is intended to do, but just pretend everything makes sense. :)
>
> Thanks for your comments.
>
> Cheers,
> Adrian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
