Thanks for all of your comments. Looks promising.
> When used in html page it will use the HTML panel and when added in the
> FOP page will produce the FOP markup.
You don't happen to use that in a Swing application as well? :)
I guess I will try that Wicket Tester hint in a Swing environment. J
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 w
what you can do is have wicket generate the necessary xml you need
with wickettester and postprocess that yourself into the pdf.
you can override page#getmarkuptype() to return "xml" and wicket will
look for the xml file instead of html.
-igor
On Mon, Dec 15, 2008 at 2:14 PM, Adrian Wiesmann wr
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 i
