Hi Thorsten,
Yeah, wicket is beautiful haha! Whenever I encounter a tricky problem, I always
find a nice and clean way to handle it with wicket.
One of the reasons it is my framework of choice.
Regarding the transformer behavior: yeah, that is probably a good fit for you.
On another note: why
Guten Tag Thorsten Schöning,
am Sonntag, 15. Mai 2016 um 11:14 schrieben Sie:
> So next I will have a look at extending
> AbstractTransformerBehavior with its "tranform" method.
Hi,
this was far easier to use, beautiful Wicket... Sadly I saw it too
late and wasted quite some hours on the former
Guten Tag Thorsten Schöning,
am Samstag, 14. Mai 2016 um 19:26 schrieben Sie:
> [...]instead I would like to have one
> place, e.g. "resultsContainer" itself, to process the markup in such a
> way that this parent container of all markup generates unique ids,
> changes the "headers" references to
Guten Tag Bas Gooren,
am Samstag, 14. Mai 2016 um 11:45 schrieben Sie:
> Can you show us some code (html and java) - perhaps as a github
> gist or similar? It’s not 100% clear to me what you are asking.
Find my table at the bottom, it is coming from one panel and contains
different Wicket
Hi Thorsten,
Can you show us some code (html and java) - perhaps as a github gist or
similar? It’s not 100% clear to me what you are asking.
For page-unique ids, simply let wicket render the components and call
setOutputMarkupId(true).
If you want to control the ids yourself, cal
Hi all,
I have a page where one and the same table (in terms of markup) is
rendered multiple times with different data at the same time, simply
underneath each other. The markup uses "id" and "headers" attributes,
but with static values in the markup and with multiple instances of
the table this
