Thanks for the info.
On 10/27/06, Eelco Hillenius [EMAIL PROTECTED] wrote:
And ultimately, there is custom markup loading
(wicket.examples.customresourceloading), though I would only consider
that when working with 2.0.
Eelco
On 10/26/06, Juergen Donnerstag [EMAIL PROTECTED] wrote:
Does this also take into account package resources such as:add(HeaderContributor.forCss(getClass(), myPanel.css));So if I have a myPanel_foo.css defined it will chose this instead if style is set to foo?
-jsOn 10/26/06, Pierre-Yves Saumont [EMAIL PROTECTED] wrote:
Use styles. You can have several
It should.
Eelco
On 10/31/06, Jonathan Sharp [EMAIL PROTECTED] wrote:
Does this also take into account package resources such as:
add(HeaderContributor.forCss(getClass(), myPanel.css));
So if I have a myPanel_foo.css defined it will chose this instead if style
is set to foo?
-js
Hi, In many cases, it is useful to define an application wide Panel for commonly recurring parts of the user interface. Nevertheless, sometimes, it is necessary to vary only the presentation of a Panel.
As far as I understand it, the Panel is always associated with one html template with the same
Use styles. You can have several templates with different extensions,
for example loginPanel_liquid.html and loginPanel_icy.html.
Then, when you switch style from liquid to icy, Wicket will
automatically select the appropriate template.
Pierre-Yves
Erik Brakkee a écrit :
Hi,
In many
Hi Erik,
As far as I understand it, the Panel is always associated with one
html template with the same name as the panel.
Actually this is not true. You can work with styles and variations. I
have never done myself, but you can do something like:
class MyPanel extends Panel {
public
I forgot this:
to switch styles, use Session.setStyle().
Pierre-Yves
Pierre-Yves Saumont a écrit :
Use styles. You can have several templates with different extensions,
for example loginPanel_liquid.html and loginPanel_icy.html.
Then, when you switch style from liquid to icy, Wicket will
exactly, style is a per session setting whereas variation is a per
component setting.
Juergen
On 10/26/06, Pierre-Yves Saumont [EMAIL PROTECTED] wrote:
I forgot this:
to switch styles, use Session.setStyle().
Pierre-Yves
Pierre-Yves Saumont a écrit :
Use styles. You can have several
And ultimately, there is custom markup loading
(wicket.examples.customresourceloading), though I would only consider
that when working with 2.0.
Eelco
On 10/26/06, Juergen Donnerstag [EMAIL PROTECTED] wrote:
exactly, style is a per session setting whereas variation is a per
component setting.
