It's exciting to be part of wicket community.
Thanks a lot friends for your enthusiastic responses.
I will go through the resources you have shared.
On Fri, Sep 21, 2012 at 6:13 PM, Decebal Suiu wrote:
> Hi
>
> I will release today or Monday a wicket-dashboard project on github. This
> project i
This is really amazing Sebastien.
wicket-jquery-ui is really feature rich.
Is the demo site a wicket app?
On Mon, Sep 24, 2012 at 1:38 AM, Sébastien Gautrin <
sebastien.gaut...@gmail.com> wrote:
> Wow,
>
> This is simply terrific. I will sift through all this in the next weeks.
>
> All I can say
Wow,
This is simply terrific. I will sift through all this in the next weeks.
All I can say is a big thanks for everything!
Sébastien
On 22/09/12 19:00, Sebastien wrote:
Hi Sebastien.
wicket-jquery-ui has the goal to integrate jQuery UI widgets as Wicket
components; but it's also designed to
Perfect !!!
Thanks !!!
> > > Oscar Besga Arcauz < < <
-Sebastien escribió: -
Para: users@wicket.apache.org
De: Sebastien
Fecha: 23/09/2012 16:55
Asunto: Re: Avoid panel's extra div
oops: setRenderBodyOnly(true);
On Sun, Sep 23, 2012 at 4:53 PM, Sebastien wrote:
> Hi Oscar,
oops: setRenderBodyOnly(true);
On Sun, Sep 23, 2012 at 4:53 PM, Sebastien wrote:
> Hi Oscar,
>
> If I understand, the problem is that the div of the parent page is
> rendered, right?
> If so, you can decide to not render the parent component's tag by using
> myPanel.getRenderBodyOnly(true);
>
>
Hi Oscar,
If I understand, the problem is that the div of the parent page is
rendered, right?
If so, you can decide to not render the parent component's tag by using
myPanel.getRenderBodyOnly(true);
Hope this helps,
Sebastien.
On Sun, Sep 23, 2012 at 4:17 PM, Oscar Besga Arcauz wrote:
> Hi wic
Hi wickers
I am using a lot of panels in my wicket webapp, with the usual
add(new MyPanel("myPanel"));
But I was thinking if there is a wicket tag that can avoid using the extra
panel, like
I've tried with wicket:panel, wicket:container, wicket:enclosure with no
luck...
I'm
I'm having a strange problem with page load times slowing down significantly.
Its strange but it seems related to the total size of the JavaScript
contribution being made to the header. We include common JavaScript
required by all of our pages in a base class (things like jquery). In total
there