Hi,
I think you need a push approach. I suggest you to use the Atmosphere
framework that enable a push channel between the client and the server with
WebSocket (of HTML5). If Websocket doesn't work, Atmosphere uses the Comet
approach.
See:
That seems very cool !!
Many thanks for your great job
Julien Roche
On Fri, Apr 1, 2011 at 9:02 AM, nino martinez wael
nino.martinez.w...@gmail.com wrote:
very nice with the scaffold component!!
Any examples of it?
2011/3/31 James Carman ja...@carmanconsulting.com:
Wicketopia is a
Hi,
This is typically a jquery ui problem. Indeed, it creates a div element
after the input field So, each time you refresh the input, a new div will be
inserted. The best workaround is to wrap the input into a div / span
element which will be used to refresh the input. With this approach, we
Hi,
Be carefull with autocomplete, that seems to be an new HTML5 input
attributes (see http://www.w3schools.com/html5/att_input_autocomplete.asp).
That will works for new browser, but not for the old.
Regards
Julien Roche
On Mon, Mar 14, 2011 at 5:14 PM, Bas Gooren b...@iswd.nl wrote:
Hi,
The jQuery UI Dialog (and the others dialogs too) has this comportement
(adding elements at the end of the body) to position the dialogs and for the
modal approach. So, when you refresh the dialog, you recreate the instance
and so regenerate the HTML. You have to destroy properly your dialog
Hi Anna,
I think you have to set the right converter on your wicket textfield (with
the override of the method getConverter and with the class
PatternDateConvert). The dateFormat option works only on the client side
with jQuery.
Regards
Julien Roche
On Tue, Dec 7, 2010 at 7:56 PM, Anna
Hi,
Just a little annoucement for an intermediate release of wiQuery: the 1.1.2.
What kind of changes ?
* Use of jQuery 1.4.4 jQuery UI 1.8.6
* IModel enhancement for the options
* Javascript and Stylesheet enhancement
* Animate for the jQuery effect
* IWiQueryInitializer
Hi all,
Can you try tabs with the last release of wiquery ? (the 1.1.1). A lot of
changes and refactoring were don into the core. Maybe that will solved your
problems.
Can you give me your feedbacks please .
Thank you
Regards
Julien Roche
On Mon, Nov 29, 2010 at 9:33 PM, Brad Grier
Hi Armandoxxx,
If you want, you have too an implementation for your case with wiQuery (see:
http://wiquery-examples-1-1-x.appspot.com/?wicket:bookmarkablePage=:org.odlabs.wiquery.examples.droppable.DroppablePage).
But your approach is very ligthweight !!
Regards
Julien
On Tue, Nov 9, 2010 at
Hi,
wiQuery is now available as 1.0.3 (bugfixes from the 1.0.2) and as a major
version: the 1.1.
The 1.1 binds jQuery 1.4.3, jQuery UI 1.8.5 and Wicket 1.4.12. So, you can
found two now components: AutoComplete and Button (see the jQuery UI
examples: http://jqueryui.com/demos/autocomplete/ and
Hi Peter,
The right way for your case will be:
add(new WiqueryAbstractBehavior() {
public JsStatement statement() {
return new JsStatement ().$(null, .check-login).chain(attr,
'href', '#');
}
});
In the standard process, we will never have an empty component when the
renderHead
Or
return new JsQuery().$(.check-login).chain(attr, 'href', '#');
Julien Roche
On Mon, Oct 18, 2010 at 5:53 PM, julien roche AKA indiana_jules
roche@gmail.com wrote:
Hi Peter,
The right way for your case will be:
add(new WiqueryAbstractBehavior() {
public JsStatement statement
Hi Reinout,
Can you post your HTML code please ? Because I think the better way with an
ajaxLazyLoadPanel will be like this:
div wicket:id=accordion
h3a href=#First header/a/h3
divdiv wicket:id=lazy/div/div
h3a href=#Second header/a/h3
divSecond content/div
/div
Where lazy is a
Hi,
For wiQuery, you can find the sources on the following link:
http://code.google.com/p/wiquery/source/browse/#svn/examples/wiquery-examples
To see dialogs examples:
http://code.google.com/p/wiquery/source/browse/#svn/examples/wiquery-examples/src/main/java/org/odlabs/wiquery/examples/dialog
Hi,
All our jQuery UI components and behaviors were made as wiQuery plugins. You
can take a look on the code in the svn. You have got too an example for the
qTip plugin:
http://groups.google.com/group/wiquery/browse_thread/thread/119255ce1db56101/7b36b3cc2ed957a0?lnk=gstq=tooltip#7b36b3cc2ed957a0
Hi,
Have you enable wiquery in your Wicket application ? This link is an
implementation of the WebApplication with the linked with Wiquery:
http://code.google.com/p/wiquery/source/browse/branches/1.0.1/src/main/java/org/odlabs/wiquery/utils/WiQueryWebApplication.java
Hope that helped you
Julien
?
2. Why the example requires double-click?
Regards.
-David
--- On Tue, 3/30/10, julien roche AKA indiana_jules roche@gmail.com
wrote:
From: julien roche AKA indiana_jules roche@gmail.com
Subject: Re: My first WiQuery app does not work
To: users
quick questions:
1. My environment is JDK 1.6 and Wicket 1.4.7. WiQuery
1.0 should have no problem with it. Correct?
2. Why the example requires double-click?
Regards.
-David
--- On Tue, 3/30/10, julien roche AKA indiana_jules
roche
Julien Roche Aka Indiana_Jules
On Tue, Dec 8, 2009 at 8:30 PM, TahitianGabriel glan...@piti.pf wrote:
Try to add URIEncoding=UTF-8 in the Connector meta in the server.xml file
of Tomcat:
Connector URIEncoding=UTF-8 ...
Should solve your problem...
Regards,
Gabriel.
--
View this message
', wicketSerialize(this)); return true;};
It works, I retrieve the correct text.
Can it be possible to change this part of code to avoid changing the Tomcat
server configuration ?
Thanks
Julien Roche Aka Indiana_Jules
Email: roche@gmail.com
Portable: 06 63 91 94 63
Skype: indiana_jules
20 matches
Mail list logo