Hi,
On Thu, May 2, 2013 at 4:30 PM, Martin Dietze <d...@fh-wedel.de> wrote: > Since Wicket 6 introduced jQuery as backend for Ajax, there are > now rather many jquery-libraries included and there are rather > Many JQuery libraries included ? What do you mean with this ? Wicket contirbutes jquery.js, wicket-ajax-jquery.js and wicket-event-jquery.js. In Wicket 1.5 they were the latter two. > long blocks of Javascript code executed at "domready". > This depends on how many Ajax components/behaviors you have in your page and how many OnDomReadyHeaderItems are contributed. If you use JavaScript event delegation with Wicket Ajax Behavior that broadcasts events then you can decrease this dramatically. > > One of our HTML designers now expressed his concern that on > rather complex pages like ours this approach may slow down > rendering pages on slow machines (our project is used by people > from their workplaces where they - by company policy - have to > use old IE browsers on often not exactly fast machines). > > Since I am not at all an expert in this field, I'm passing on > this concern here, maybe any of the gurus around here can > comment on this? One of the possible measures our HTMLer > mentioned was bundling multiple Javascript-includes to a single > one, is this something that can be done for the Javascript > library includes added by Wicket? > Check http://wicketinaction.com/2012/07/wicket-6-resource-management/ - bundles. > > Cheers, > > M'bert > > -- > ----------- / http://herbert.the-little-red-haired-girl.org / > ------------- > =+= > It was hard to code, so it should be hard to understand! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Martin Grigorov Wicket Training & Consulting http://jWeekend.com <http://jweekend.com/>