That's right, I just checked the sources... Anyways, although migration the
project
now does not make sense, it is a good idea for the next project...
Thanks everybody,
J.
On 20.02.2012 08:31, Wilhelmsen Tor Iver wrote:
Thanks a lot. One last stupid question: is this supposed to work for Wick
Thanks for the post.
I wish this could be integrated into the core.
Josh.
On Mon, Feb 20, 2012 at 5:32 AM, robmcguinness <
robert.mcguinness@gmail.com> wrote:
> very nice thanks!
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Shrinking-the-session-size-s
> Thanks a lot. One last stupid question: is this supposed to work for Wicket
> 1.4?
Doubful, the event system was added in 1.5
- Tor Iver
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e
very nice thanks!
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Shrinking-the-session-size-simply-by-zipping-it-Saved-my-day-tp4402980p4403065.html
Sent from the Users forum mailing list archive at Nabble.com.
On 02/19/2012 10:56 PM, Jorge Rodrigez wrote:
You just need to add/remove an item to your data source.
Next time you rerender the grid it will show/hide the added/removed
Any custom datasource examples out there? Essentially I'd like to bind
the grid to a POJO collection member.
Manos
-
Hi all,
thought I'd share a really simple hack that we're using to reduce the Wicket
session size (on Wicket 1.4).
Background: We deploy to Google App Engine, and there's a strict 1MB limit.
We've been using LDMs and all sorts of optimisations, but we were still
reaching the limits when a user v
You just need to add/remove an item to your data source.
Next time you rerender the grid it will show/hide the added/removed
item/row.
On Sun, Feb 19, 2012 at 6:46 PM, Emmanouil Batsis (Manos) wrote:
> Subject says it all... currently using inmethod from wicketstuff but there
> is no add/remove r
Check out Flexigrid for Wicket: http://code.google.com/p/flexigrid-for-wicket/
Verma Shalini (HCTM/ETA us.bosch.com> writes:
>
> Hi,
>
> I was trying to search if anybody has integrated the Jquery Felxigrid plugin
with Wicket.As the tool is very powerful.
>
> Thanks
> Shalini
>
>
-
Subject says it all... currently using inmethod from wicketstuff but
there is no add/remove row in the 1.4.x versions.
Manos
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-
Hi,
Can any person help my this issue ?
Actually i am facing two issue in my all wicket application version
1.5.3.
First is, I have a dropdown choice. When the page is render first time,
in dropdownchoice , choose one shown. But when select any item from drop
down and click on save but
Thanks a lot. One last stupid question: is this supposed to work for Wicket 1.4?
J.
On 19.02.2012 15:28, Christoph Leiter wrote:
$(document).ready(function() {
Wicket.Event.subscribe('/dom/node/added', function(element) {
$(element).css('border', '1px solid red');
});
});
Ok, now i researched some some more:
What i wan't to do: Have an autocompletetextbox with custom layout in the
dropdown.
The default autocomplete fills the first criteria, but then i would like to
modify the html-output
thats created in the dropdown. The default output is final though and
outputs
Sure:
$(document).ready(function() {
Wicket.Event.subscribe('/dom/node/added', function(element) {
$(element).css('border', '1px solid red');
});
});
On 19.02.2012 13:39, Jürgen Lind wrote:
I'm not sure if I get you right on this one: the first argument of which
event
handler is
Hi,
at first glance I can't say what's wrong with your code, but you
should try debugging wicketAjaxGet function with FireBug or some other
dev tool. In this way you should find why there's no AJAX call.
I have an Ajax link in a drop down menu, created like this:
final MenuC
I'm not sure if I get you right on this one: the first argument of which event
handler is the added element? Could you probably add some code to illustrate
this?
J.
On 19.02.2012 13:28, Christoph Leiter wrote:
Hi Juergen,
there's actually no need to scan the full DOM with this method. :) The
Hi Juergen,
there's actually no need to scan the full DOM with this method. :) The
first argument of the event handler is the added element. You can simply
use it as is or pass it to $() to do jQuery magic just for the relevant
part.
Christoph
On 19.02.2012 13:18, Jürgen Lind wrote:
Chri
Christoph,
I have use yout approach (jQuery + css-class) for some time now as well.
However, I
have found that if the DOM tree grows rather large, a full scan puts
significant load
on the browser. That's why I want to be more specific and limit the scanning +
updating
to the relevant parts of
On 18.02.2012 17:46, Jürgen Lind wrote:
thank you for your reply, I did not know that such a method exists (does
it for 1.4
or is this already Wicket 1.5). An secondly: are these handlers fired on
a ajax
update of an existing DOM Element or only when it is added?
This is also available in 1.4.
Well, I haven't used 1.4.x for almost two years now ...
It seems you need to add "implements IHeaderContributor" to your component.
From: Jürgen Lind
To: "users@wicket.apache.org" ; Martin Grigorov
Sent: Sunday, 19 February 2012, 12:37
Subject: Re: Component
Strange, I am using 1.4.12 and neither is present there. The javadoc at
http://wicket.apache.org/apidocs/1.4/org/apache/wicket/Component.html also does
not show the method with this signature...
J.
On 19.02.2012 12:23, Martin Grigorov wrote:
Hi Juergen,
Both Component#renderHead(IHeaderRespo
Hi Juergen,
Both Component#renderHead(IHeaderResponse)
IHeaderResponse#renderOnDomReadyJavascript() methods are available in 1.4.x.
What exactly you think is not available there ?
From: Jürgen Lind
To: "users@wicket.apache.org"
Sent: Sunday, 19 February 2012
Hi Jorge,
thanks for the hint, unfortunately, this method is only available in Wicket 1.5
-
in this projekt, I am still using Wicket 1.4. Maybe I should stop looking for
a general solution for this project and in the future use the solution you
suggested...
J.
On 19.02.2012 10:30, Jorge Rodr
Hi,
I think you just need:
class MyComponent extends SomeWicketComponent {
@Override public void renderHead(IHeaderResponse response) {
response.renderOnDomReadyJavascript("someJSToExecute()");
}
}
someJSToExecute() will be executed every time an instance of MyComponent is
rendered. Bot
23 matches
Mail list logo
