Some issues with Wickext

[Papegaaij]

Hello,

We've recently added Wickext to our project, and I must say, it greatly helps
in integrating JQuery in a Wicket project. However, we did discover some
issues.

First of all, there seems to be a bug in SlideUp. The chainLabel method
returns 'slideUp()', where it probably should return 'slideUp' (without the
braces).

The second problem is with the WickextUIPlugin annotation. This annotation is
not inherited by subclasses. I don't think it is logical to create subclasses
of a WickextUIPlugin that are no longer WickextUIPlugins. I think the
@Inherited annotation should be added to WickextUIPlugin.

The third issue is a bit more difficult to solve. On some pages we have many
Wickext components (up to 300). This results in many small script tags, like
  $(document).ready(function() {
    $('#tristate8b').click(clickTriStateCheckBox);
    ;
  });
I don't know if this really is a problem, but it seems to make loading the
page take quite long. For this, I do not yet know a solution, because to solve
this, all fragments must be collected and rendered in a single header
contributor. Perhaps, this header contributor can be placed on the page, but
at instantiation of the components, it is not yet known to which page they
will be added.

Finally, the version of JQuery included with Wickext is quite old. Is there a
reason why Wickext still uses 1.2.5 and not 1.2.6 or even 1.3.1? I've locally
upgraded the version to 1.3.1 and did not notice any problems (although I must
admit we do not use all components).

Best regards,
Emond Papegaaij

[Lionel Armanet]

Hello Emond,

First of all thanks for your feedbacks, we hope using WickeXt was
helpful for your project.

For the issues you noticed:

> First of all, there seems to be a bug in SlideUp. The chainLabel method
> returns 'slideUp()', where it probably should return 'slideUp' (without the
> braces).

I'll look at his bug ASAP to emit a patched version.

> The second problem is with the WickextUIPlugin annotation. This annotation
> is
> not inherited by subclasses. I don't think it is logical to create
> subclasses
> of a WickextUIPlugin that are no longer WickextUIPlugins. I think the
> @Inherited annotation should be added to WickextUIPlugin.

Ok, I'll do this with the patch release too.

> The third issue is a bit more difficult to solve. On some pages we have many
> Wickext components (up to 300). This results in many small script tags, like
>   $(document).ready(function() {
>     $('#tristate8b').click(clickTriStateCheckBox);
>     ;
>   });

For that part, we are correcting the problem. In facts, we are merging
the WickeXt project with another french project (called
jQuery4Wicket).
The problem with the current version is that there's one "onDomReady"
event per component, that's why it's a loading problem for your pages.
For the 1.0 release, there'll be only one "onDomReady" event loading
all components.

> Finally, the version of JQuery included with Wickext is quite old. Is there
> a
> reason why Wickext still uses 1.2.5 and not 1.2.6 or even 1.3.1? I've
> locally
> upgraded the version to 1.3.1 and did not notice any problems (although I
> must
> admit we do not use all components).

We'll upgrade all jQuery libs in the 1.0 version. The project will
bind a lot of jQuery and jQuery UI components.

> Best regards,
> Emond Papegaaij

Thansk again, don't hesitate if you have further questions.

--
__________________________________

Lionel Armanet
http://www.wickext.org
gmail: lionel.armanet*at*gmail.com

[Papegaaij]

On Monday 26 January 2009 14:24:52 Lionel Armanet (via Nabble) wrote:
> Hello Emond,
>
> First of all thanks for your feedbacks, we hope using WickeXt was
> helpful for your project.
<cut: two minor issues>

It's great to hear that these issues will be fixed soon. WickeXt greatly
reduces the amount of work that needs to be done to use JQuery from Wicket.
Before, we generated javascript tags with our components (inside the html
body), which required quite a lot of javascript templates.

> > The third issue is a bit more difficult to solve. On some pages we have
> > many Wickext components (up to 300). This results in many small script
> > tags, like $(document).ready(function() {
> >     $('#tristate8b').click(clickTriStateCheckBox);
> >     ;
> >   });
>
> For that part, we are correcting the problem. In facts, we are merging
> the WickeXt project with another french project (called
> jQuery4Wicket).
> The problem with the current version is that there's one "onDomReady"
> event per component, that's why it's a loading problem for your pages.
> For the 1.0 release, there'll be only one "onDomReady" event loading
> all components.

How does JQuery4Wicket solve this? I tried to come up with a solution, but
Wicket makes it very difficult to collect information in a single
HeaderContributor.

> > Finally, the version of JQuery included with Wickext is quite old. Is
> > there a
> > reason why Wickext still uses 1.2.5 and not 1.2.6 or even 1.3.1? I've
> > locally
> > upgraded the version to 1.3.1 and did not notice any problems (although I
> > must
> > admit we do not use all components).
>
> We'll upgrade all jQuery libs in the 1.0 version. The project will
> bind a lot of jQuery and jQuery UI components.

When do you think 1.0 will be released?

Best regards,
Emond Papegaaij

[Lionel Armanet]

Hello,

> How does JQuery4Wicket solve this? I tried to come up with a solution, but
> Wicket makes it very difficult to collect information in a single
> HeaderContributor.

To solve that problem, we are using a single header contributor
managed by the application listener (it's still in experimental mode,
but we obtained great results with the new generation process).

> When do you think 1.0 will be released?

The 1.0 should be released near the end of March. This new version
will come with a new name for the project (which is for the moment
under discussion ;-) ).

We'll make an announcement soon to give a roadmap about the future of
WickeXt - JQuery4Wicket.


--
__________________________________

Lionel Armanet
http://www.wickext.org
gmail: lionel.armanet*at*gmail.com

[Papegaaij]

On Monday 26 January 2009 14:24:52 Lionel Armanet (via Nabble) wrote:
> Hello Emond,
>
> First of all thanks for your feedbacks, we hope using WickeXt was
> helpful for your project.
>
<cut some wickext issues>

We just discovered a problem with WickextEventBehavior. This class tries to
attach a CoreJavaScriptHeaderContributor to the Page of the component in the
bind method. This makes it impossible to add the behavior to a component that
has not yet been added to the page (for example when inside the constructor of
the component). I think the solution is to remove 'getPage()' and simply add
the contributor to the component itself.

Best regards,
Emond Papegaaij