jijopaulose / wiquery Goto Github PK

java.lang.IllegalArgumentException: reference cannot be null is raised when 
using resizable 
behavior.

View here: http://n2.nabble.com/newbie-problem-td3011076.html#a3011076

Version: 1.0-alpha

The bugfix will result in a new patched version of 1.0-alpha

Here is an implementation of DraggableAjaxBehavior with support for the 
onStop event.  Currently does not support onDrag or onStart.

J'ai un iColorPicker sur un TextField dont le JS ne doit être lancé qu'une
fois. Hors naturellement on dépose le behavior de ce color picker
directement sur le TextField. Du coup, le JSStatement est exécuté autant de
fois qu'il y a de TextField dans ma page, et à l'exécution, et je me
retrouve avec plein de iColorPicker associé à mon TextField !

Un autre cas d'utilisation est pour les tooltips.

Il faudrait pouvoir dire à WiQuery que, pour certains Behaviors, il ne faut
pas insérer le statement de chacun. Plusieurs pistes:
- pouvoir mettre un Id de behavior, à la manière des Id de ResourceReference
- détecter les doublons de script, en utilisant la méthode equals(..) (ou
autre) sur les statements au moment de l'écriture dans la page
- mettre certains behavior en singleton, mais cette solution ne me plaît
pas car, pour mon cas, je pourrais vouloir mettre certains color picker
avec une table de couleur et d'autres color picker avec une autre table de
couleur, le singleton ne pourrait pas simplement répondre à ça.

L'id sur les behaviors me paraît le plus simple, de la responsabilité du
développeur.

The receive and update events of the SortableAjaxBehavior have a sorted index 
field, however looking at the javascript behind this I see:

'+$(this).children('li').index(" + SortableBehavior.UI_ITEM + ")+'"

This will not work if the child is not an li (I am seeing -1 returned as I am 
using div's)

I have modified the code so that it uses the sortable toArray function to send 
the full list of dom ids to the server, and then works out the updated index on 
the server.

Patch attached, but I haven't tested it on anything but my code, but may give 
you a good starting point.

Currently the user of Wiquery have to extend WickextWebApplication to
register WickextPluginInstantiationListener or do it manually (copy/paste
the code from WickextWebApplication).

With the attached patch the logic is moved to an implementation of
org.apache.wicket.IInitializer.

Additionally I made WickextPluginInstantiationListener a singleton to be
able to set/get the theme resource. Maybe there is better way ...

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

update wiquery-presentation-examples pom to wiquery 1.0 and add a Start class 
for launching jetty

Feature for the 1.0.2

Add an option / annotation to disable auto-import of JavaScript / CSS
resources.

Description : The auto-import can cause conflicts in existing applications.
The solution would be to provide an option to select which resources to ignore.

http://methvin.com/splitter/

What steps will reproduce the problem?
1. Bundle wiquery-examples-1.0 with wicket 1.4.4
2. Deploy it to a Tomcat
3. (Firefox + Firbug Networking enabled) Goto to the 'Dialog examples'

What is the expected output? What do you see instead?
It takes a few ms to load the page, but then the 'load' event takes 20s to
complete.

What version of the product are you using? On what operating system?
wiquery 1.0, wicket 1.4.4

Please provide any additional information below.
Here is a running instance:
http://79.125.22.98:8100/we/?wicket:bookmarkablePage=:org.odlabs.wiquery.example
s.dialog.DialogPage

JsStatement.self() and JsStatement.document() are not accessible from
outside. I don't understand why. I suggest to set them public.

wiQuery 1.0-m2 use Wicket 1.4-rc2 version. The actual version of the
framework is now 1.4.1

We will change the pom.xml to upgrade to 1.4.1

It would be excellent if the generated JS code used the jQuery() function
instead of $().  This would avoid issues with prototype.

Great work btw!

-- James

SlideUp effect generates a wrong chain label.

Drag & drop broken after AJAX update. See the example in attachments. Just 
"mount" the panel TestDraggable.java and drag the draggable to the droppable.  
After AJAX refresh dragdrop no longer works.

I think it would be good to allow Options to take an IModel.

This would be helpful in many situations, for example, the title of the 
Dialog could be made to use a StringResourceModel so this can be 
internationalized and read from properties file

Thoughts?

What steps will reproduce the problem?
I want implement plugin for tooltipe
http://pupunzi.open-lab.com/2009/02/07/mbtooltip/

but it use tag attribute for Tooltip
so I decided use   AttributeAppender
public class ToolTip extends AttributeAppender implements IWiQueryPlugin {

    private static final long serialVersionUID = 1L;

    private Options options;

    public ToolTip(String attributeName, IModel<String> tooltipe) {
        super(attributeName, tooltipe, " ");
        options = new Options();
    }

    @Override
    public void contribute(WiQueryResourceManager wiQueryResourceManager) {

wiQueryResourceManager.addJavaScriptResource(TooltipJavaScriptResourceReference.
get());
        wiQueryResourceManager.addCssResource(TooltipCssResourceReference.get());

    }

    @Override
    public JsStatement statement() {
        return new JsQuery(this).$().chain("test", options.getJavaScriptOptions());
    }

}

but JsQuery constructor take only Component

Indeed, if you read the documentation
(http://docs.jquery.com/UI/Draggable#option-cursorAt), we can have many
properties and a gap for each of them.

We must the implementation, where we have only an enumeration (that's
really weird)

The documentation for a quickstart project showed in the Wiki is
out-of-date. I'm submitting the correct implementation for the quickstart.

Hope this helps.
Cheers,
Mauro Ciancio.

What steps will reproduce the problem?
Run attached quickstart (uses m2)
go to localhost:8080
-you should see the alert
click on 'Ajax Link'
-you see the alert even though the tabs component is added on the ajax request 
target, not the Alert plugin

What is the expected output? What do you see instead?
Change to m1 and it works as you expect.

It appears that anytime a wiquery component is added to the ajax request 
target, all 
statements from all wiquery components on that page are added to the target and 
executed in m2.

Regards - Richard Wilkinson
Developer,
jWeekend: OO & Java Technologies - Development and Training
http://jWeekend.com

Add any kind of option ot a DraggableBehaviour

e.g (new DraggableBehavior()).setOpacity(0.75f)

yields a null pointer exception.

Presumable this is because the options are never initialised in
DraggableBehaviour.java:

    // Properties
    private Options options;


Compare with DroppableBehaviour.java:

        // Properties
        private Options options = new Options();

Hi,

The application [1] contains to classes LayoutPlugin and Layout defining
integrations with [2]. I think the former is meant to be used as top level
layout while the latter to be used as the layout of a inner div. IMHO there
is no need for creating separate classes for this. So, I have modified the
later to be able to cope with both use cases. See Layout class on the
attachment (on zip format). Additionally it will be nice to release this as
a separate plugin project. Maybe as part of the github plugins repository?
The zip also contains sample pages illustrating how to use the plugin in
both scenarios: full page (FullTestPage) vs div (OnDivTestPage).

Best,

Ernesto 

References

1-wiquery-presentation-examples
2-http://layout.jquery-dev.net/

If setters returned 'this', it would be possible to chain calls when using
WiQuery components.

What steps will reproduce the problem?
Go to a page with that uses ThemeHelper, for example i added a 
SortableBehavior.  This throws a NPE because it cant get the default theme.

This turns out to be because i dont have a httpsession yet, and theme 
helper tries to put the default theme into the httpsession, which as it is 
null, fails.

using 1.0-m1 from svn

Attached is a quickstart to demonstrate the problem, navigate through the 
jqueryp link on homepage.

This problem could be solved by either storing the theme somewhere else (eg 
the wicket session, but this would require a custom session, or maybe in 
the application class?), or creating the httpsession.

I realize that for most users they will have a httpsession, its only when 
all the pages up to the page with the ThemeHelper are stateless and put 
nothing into the session, meaning that it isn't created.

I have temporaily fixed this im my code by returning the theme in 
ThemeHelper.getTheme() rather than setting it to httpsession and getting it 
out again.

According to http://api.jquery.com/toggle/ toggle does accept a duration
while Toggle effect does not accept one.

What is the expected output? What do you see instead?

JQueryUICoreRenderingListener.DEFAULT_THEME is private. I am trying to
override our company default theme with the default one from WiQuery, but
this is impossible because DEFAULT_THEME is private. 
What is the use of a private static field if it is only used in 1 line
within WiQuery?

I expected DEFAULT_THEME to be public so I can use it to overide our
company theme.

What version of the product are you using? On what operating system?
Wiquery 1.0

What steps will reproduce the problem?
1.Use a draggable behavior
2.Add options

What is the expected output? What do you see instead?

The component should have applied the given options, instead options are lost.

Please use labels and text to provide additional information.

Issue from Ben's mail:

"Hello,
I was just checking out the 1.0-m1.1 jar to see if we could start
using it. It looks like DraggableBehavior is not adding the options
at line 131. Its been fixed in the m2 branch but would be a nice to
have in m1.x. if possible?

       public JsStatement statement() {
               return new JsQuery(getComponent()).$().chain("draggable");
       }

should be:
      public JsStatement statement() {
               return new JsQuery(getComponent()).$().chain("draggable",
                               this.options.getJavaScriptOptions());
       }

Ben"

Allow to choose which elements are sortable. Now it is possible only with <li>.
Patch attached.

WiQuery v1.0 
CoreJavaScriptResourceReference

shouldn't the method below be synchronized?

public static CoreJavaScriptResourceReference get() 

Hey Guys,

Sorry about the earlier post (Issue 25), I accidently hit the submit button
before I completed the issue I was reporting.  The issue is the wiquery
sample site: http://www.wiquery.org/wiquery-examples-1.0/ is rendering a
runtime exception the moment you click on one of the components listed on
the sample site.

To reproduce issue:

1) Go to the site containing the wiquery sample components:
http://www.wiquery.org/wiquery-examples-1.0/
2) Click on one of the components such as "tabs", "accordian",
"datepicker", etc.
3) Runtime exception is displayed on the screen instead of the actual
components.

What steps will reproduce the problem?
1. Add a slider to a page / panel
2. add(new Slider("slider", 0, 10));

What is the expected output? What do you see instead?

NPE since the Slider does not initialize the Options

Fix:

A patch for this is attached, but essentially, i have changed the 
constructor to this:

public Slider(String id, Number min, Number max) {
        super(id);
        options = new Options();
        this.setMin(min);
        this.setMax(max);
    }

(note i also changed the setMin, setMax, getMin, getMax methods to work 
with Number rather than int (uses a float internally)

What steps will reproduce the problem?
1. Just use the WiQueryEventBehavior (or WiQueryAbstractBehavior) 

What is the expected output? What do you see instead?

The javascript JsStatement (and similar) generated output is lost.

After page refresh, the statement() method generated JsStatement loses
statement. See the explanation below


What version of the product are you using? On what operating system?
1.0-Alpha, but the problem was noticed in 1.0-SNAPSHOT-r44-d1239057663270
initially.


Please provide any additional information below.

The problem seems to be WiQueryCoreHeaderContributor renderHead method:
the WiQueryAbstractBehavior bind(Component component) is called once, after
the page component is installed. In this method the contributor plugin
(behavior) is placed (contributor.addPlugin(this);).

Now WiQueryCoreHeaderContributor renderHead inserts all the statements
correctly the first time, because it sees the behaviors plugins plugged in
the bind method of WiQueryAbstractBehavior. The problem is, that after
doing that, plugins.clear(); is called, successfully clearing all the
plugins, which are not initialized until new page instance is built.

Am I doing something wrong there?

That's a proposal.

It was hard to me to create a 2-Dimensions array class option.

I tried to use ICollectionItemOptions but it doesn't really feet my needs
due to the "values()" method which return a simple IListItemOption array
whereas I needed a String[][], so I wrote mine from scratch (easily done of
course)

Generifying IComplexOption would allow a better, fine grained use of these
classes. But that's a huge job.

Hi,

Is there any possiblity to create sections dynamically? I was expecting 
something like an 
"addSection" method or a way to subclass the accordion class (similar to the 
wicket-stuff accordion 
implementation), but did not find a way how to do this with the wiQuery 
Accordion implementation.

Thanks in advance!

It would be great to have a maven repository, even if current version is 
still a snapshot.

-> Create release (empty ?) and snapshot (with 1.0-snapshot)  ?

wiQuery use the jQuery UI 1.7.1. It seems that a lot of patch and upgrade
were reported to the actual version, the jQuery UI 1.7.2.

So, we will upgrade our jQuery UI resources.

What steps will reproduce the problem?
1. Create a page with an empty panel in it
2. Create a panel with a DataPicker in it
3. Make sure your locale is english
4. Replace the empty panel with the panel containing the DatePicker
5. Append some extra javascript to run after ajax completes

What is the expected output? What do you see instead?

The panel should get replaced and the the extra javascript should run.
Instead, javascript stops executing because ui.datepicker-en.js cannot be 
found. A 404 error is shown.

What version of the product are you using? On what operating system?

1.0-m2

Solution:

A simple solution is to add an empty ui.datepicker-en.js file to the 
following location:

org/odlabs.wiquery/ui/datapicker/i18n/ui.datepicker-en.js

I'm sure there would be better solutions than this, but that's what I did 
to get it working.

I'm using a WiQuery datepicker (its great, btw) on a page with a JGrowlBehavior 
component. Both 
add different versions of the jquery.js javascript file to the page, with the 
result that the 
JGrowlBehavior breaks. Is there a way for both components to interact with the 
application so that 
jquery.js is only added once to the page?

It seems that JQuery foresees this and has a noConflict() mode which should 
allow it to be included 
multiple times without causing collisions...

JsQuery.renderHead() calls response.renderJavaScriptReference(), which
causes SharedResources to store a
WiqueryGeneratedJavaScriptResourceReference instance in its internal map. 

So each time JsQuery.renderHead() is invoked, another instance of the same
JS code is leaked. The resources are then never removed during the
application lifecycle... The SharedResources instance lives in Application,
not in Session, so each time a new
WiqueryGeneratedJavaScriptResourceReference is allocated, it is leaked
until the application restart!

I believe session-scoped resources should never be referenced from the
Application object. So another way of managing these resources is needed. I
think all resources should be rendered directly into the page's content by
default. However, this would be unsuitable for large chunks of script. Not
sure how to handle these cases correctly.

Another problem is that the client may never even request this reference
(deliberately or because the client is a bot). This leads to the same leak
(and is another reason why dynamic resources should not be stored in the
Application scope). I'm not sure how to solve this correctly, but probably
some kind of timer is needed that will remove the outdated references that
haven't been picked up.

To reproduce:
1. Add a DraggableAjaxBehavior to a web markup container.
2. Run in, the rendering will fail

Clues to resolve the bug: the callback script to perform an ajax request is 
made in the onBind 
callback, and onBind is call before the component is added to the webpage.

Stack trace:

java.lang.IllegalStateException: No Page found for component [MarkupContainer 
[Component id 
= ajaxDropzone]]
     at org.apache.wicket.Component.getPage(Component.java:1729)
     at org.apache.wicket.RequestCycle.urlFor(RequestCycle.java:825)
     at org.apache.wicket.Component.urlFor(Component.java:3265)
     at 
org.apache.wicket.behavior.AbstractAjaxBehavior.getCallbackUrl(AbstractAjaxBehav
ior.java:124)
     at 
org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.getCallbackScript(AbstractDef
aultAjaxBehavi
or.java:118)
     at 
org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.getCallbackScript(AbstractDef
aultAjaxBehavi
or.java:106)
     at 
org.odlabs.wiquery.ui.droppable.DroppableAjaxBehavior.onBind(DroppableAjaxBehavi
or.java:17)
     at org.apache.wicket.behavior.AbstractAjaxBehavior.bind(AbstractAjaxBehavior.java:78)
     at org.apache.wicket.Component.add(Component.java:961)
     at org.odlabs.wiquery.panels.DropablePanel.<init>(DropablePanel.java:47)
     at org.odlabs.wiquery.HomePage$4.onClick(HomePage.java:86)
     at org.apache.wicket.ajax.markup.html.AjaxFallbackLink$1.onEvent(AjaxFallbackLink.java:73)
     at org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:166)
     at 
org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjax
Behavior.java
:299)
     at 
org.apache.wicket.request.target.component.listener.BehaviorRequestTarget.proces
sEvents(Beha
viorRequestTarget.java:105)
     at 
org.apache.wicket.request.AbstractRequestCycleProcessor.processEvents(AbstractRe
questCyclePr
ocessor.java:92)
     at org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1192)
     at org.apache.wicket.RequestCycle.step(RequestCycle.java:1271)
     at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1370)
     at org.apache.wicket.RequestCycle.request(RequestCycle.java:501)
     at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:455)
     at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:288)
     at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1139)
     at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:378)
     at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
     at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
     at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
     at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
     at 
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollecti
on.java:230)
     at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
     at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
     at org.mortbay.jetty.Server.handle(Server.java:324)
     at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:535)
     at 
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.ja
va:865)
     at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:539)
     at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
     at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
     at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
     at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)

I'm using the latest Firefox on a Mac OS X system. The examples at:

http://www.wickext.org/wiquery-examples-1.0/

are all almost entirely broken.

Google hosts several AJAX APIs - amongst others also JQuery
(http://code.google.com/apis/ajaxlibs/documentation/#jquery). 

Could you include an option for the developer to either deploy the JQuery
libraries with the Wicket installation (current status) or to use the
Google hosted JQuery API? The second case enables the developer to remove
request loads from the Wicket installation. 

When I try to use FadeOut effect, exception is thrown (tested with wicket
1.4.3 & 1.4.5)


sample code:
FadeOut fadeOut = new FadeOut(EffectSpeed.SLOW);
EffectBehavior eb = new EffectBehavior(fadeOut);
Label label = new Label("test", "TEST LABEL");
label.setOutputMarkupId(true);
label.add(eb);
add(label);

exception:
org.apache.wicket.WicketRuntimeException: Cannot modify component hierarchy
after render phase has started (page version cant change then anymore)
     at org.apache.wicket.Component.checkHierarchyChange(Component.java:3511)
     at org.apache.wicket.Component.addStateChange(Component.java:3444)
     at org.apache.wicket.Component.add(Component.java:966)
     at org.odlabs.wiquery.core.javascript.JsQuery.contribute(JsQuery.java:156)
     at
org.odlabs.wiquery.core.effects.EffectBehavior.renderHead(EffectBehavior.java:89
)
     at org.apache.wicket.Component.renderHead(Component.java:2699)
     at
org.apache.wicket.markup.html.internal.HtmlHeaderContainer$1.component(HtmlHeade
rContainer.java:231)
     at
org.apache.wicket.MarkupContainer.visitChildren(MarkupContainer.java:878)
     at
org.apache.wicket.MarkupContainer.visitChildren(MarkupContainer.java:918)
     at
org.apache.wicket.markup.html.internal.HtmlHeaderContainer.renderHeaderSections(
HtmlHeaderContainer.java:222)
     at
org.apache.wicket.markup.html.internal.HtmlHeaderContainer.onComponentTagBody(Ht
mlHeaderContainer.java:137)
     at org.apache.wicket.Component.renderComponent(Component.java:2617)
     at org.apache.wicket.MarkupContainer.onRender(MarkupContainer.java:1512)
     at org.apache.wicket.Component.render(Component.java:2448)
     at org.apache.wicket.MarkupContainer.autoAdd(MarkupContainer.java:229)
     at
org.apache.wicket.markup.resolver.HtmlHeaderResolver.resolve(HtmlHeaderResolver.
java:80)
     at
org.apache.wicket.markup.resolver.ComponentResolvers.resolve(ComponentResolvers.
java:81)
     at org.apache.wicket.MarkupContainer.renderNext(MarkupContainer.java:1418)
     at org.apache.wicket.MarkupContainer.renderAll(MarkupContainer.java:1528)
     at org.apache.wicket.Page.onRender(Page.java:1545)
     at org.apache.wicket.Component.render(Component.java:2448)
     at org.apache.wicket.Page.renderPage(Page.java:914)
     at
org.apache.wicket.request.target.component.BookmarkablePageRequestTarget.respond
(BookmarkablePageRequestTarget.java:262)
     at
org.apache.wicket.request.AbstractRequestCycleProcessor.respond(AbstractRequestC
ycleProcessor.java:105)
     at
org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1258)
     at org.apache.wicket.RequestCycle.step(RequestCycle.java:1329)
     at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1428)
     at org.apache.wicket.RequestCycle.request(RequestCycle.java:545)
     at
org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:468)
     at
org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:301)
     at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt
erChain.java:235)
     at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.
java:206)
     at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:2
30)
     at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:1
75)
     at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
     at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
     at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109
)
     at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
     at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
     at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Pr
otocol.java:581)
     at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
     at java.lang.Thread.run(Thread.java:619)

Slider stores min and max values as float and tries to retrieved then as
integers. As shown below

/**Sets the minimum  value of the slider.
     * @param min
     * @return instance of the current component
     */
    public Slider setMin(Number min) {
        this.options.put("min", min.floatValue());
        return this;
    }

    /**
     * @return the min option value
     */
    public Number getMin() {
        if(this.options.containsKey("min")){
            return this.options.getInt("min");
        }

        return 0;
    }

This causes a java.lang.ClassCastException: java.lang.Float when getMin()
is called (on options line 110).

It would be useful to be able to get the rendered JsStatement String without 
the 
semicolon on the end. 
It is possible to change JsStatement so that render can optionally return with 
out appending ';' to the end, or add another method which like this:

public CharSequence renderWithoutSemiColon(){
    return this.statement.toString();
}

feel free to change the method name :)

Regards - Richard Wilkinson
Developer,
jWeekend: OO & Java Technologies - Development and Training
http://jWeekend.com

The progress bar example does not work with the 1.0-Alpha version.

The progress bar value is always set to the value in the callback of the 
button, on user click, whatever is the value set initially.

Java Code:
        Button button = new Button("increaseProgress");
    final ProgressBar pgbar = new ProgressBar("progress");
    pgbar.setValue(0); //initial pgbar value
    button.add(new WiQueryEventBehavior(new Event(MouseEvent.CLICK) {

        private static final long serialVersionUID = 1L;

        @Override
        public JsScope callback() { 
                  // set progress bar value to 13
           pgbar.setValue(13);
           return JsScope.quickScope(pgbar.update().render());
        }

    }));

At the initialisation of the page, the javascript code in the ajax response 
is:
<evaluate>
<![CDATA[      
  $('#increaseProgressf').bind('click', function() {
       $('#progress10').progressbar('option', 'value', 13);
});]]>
</evaluate>
<evaluate>
<![CDATA[       
 $('#progress10').progressbar();
 $('#progress10').progressbar('option', 'value', 13);]]>
</evaluate>

instead of (as previously):

<evaluate>
   <![CDATA[      
  $('#examples13 code').chili();                 
$('#progress14').progressbar();
$('#progress14').progressbar('option', 'value', 0);]]>
</evaluate>
<evaluate>
<![CDATA[    
    $('#increaseProgress15').bind('click', function() {
         $('#progress14').progressbar('option', 'value', 13);
});]]>
</evaluate>

Hi,

If you want to subclass a WiQuery UI component anonymously, you can't 
because you cannot annotate an anonymous inner class.

This means that the core ui resources wont be added to the page.

It also means that someone subclassing normally will have to remember to 
add on the @WiQueryUIPlugin

Thanks,

Richard Wilkinson - jWeekend.com

When using the WiQueryResourceManager and adding a css resource, those css 
resources are not gziped.

This is because WiQueryResourceManager uses a normal ResourceReference rather 
than a CompressedResourceReference as the wicket CSSPackageResource uses.

This isnt really a bug, but a nice enhancement.

Thanks,

Richard Wilkinson - jweekend.com

JsQuery.renderHead(IHeaderResponse, IRequestTarget) écrit le javascript du
JsStatement même si le code javascript rendu est vide.
Cela n'améliore pas les performances du navigateur lorsque beaucoup de
Component n'ont rien à faire ! en Ajax notamment, car Wicket évalue chacune
des expressions vides (mis dans le <evaluate></evaluate>)

ci-joint un version modifiée de la classe avec un simple if/then/else

JsQuery should use the following code to open and close javascript tags:

response.renderString(JavascriptUtils.SCRIPT_OPEN_TAG
+ onreadyStatement.render() + JavascriptUtils.SCRIPT_CLOSE_TAG);

This will add the CDATA 'magic' to the generated javascript, which
preserves valid javascript and html.