Re: wicket8 : wickets js/ jquery integration

On Oct 7, 2017 23:23, "Sven Meier" wrote: Hi Korbinian, using the "defer" attribute on script tags in the head section seems to be best practice now: The problem is that the ondomready scripts depend on jquery and wicket-xyz ones and there is no way to defer them.

Re: wicket8 : wickets js/ jquery integration

Hi Korbinian, using the "defer" attribute on script tags in the head section seems to be best practice now: https://www.shivering-isles.com/the-science-of-loading-javascript/ Wicket supports the attribute since https://issues.apache.org/jira/browse/WICKET-5715 Have fun Sven Am

wicket8 : wickets js/ jquery integration

Hi, currently wicket renders all its jQuery and Ajax stuff right into the head, and I wonder why. Current best practice seems to defer all javascript till the end of the page just right before the closing tag to let the browser meanwhile get the DOM and do some work and not get blocked by

Re: WICKET-6105 and WicketStuff

That's a plan! Sven Am 07.10.2017 um 18:16 schrieb Andrea Del Bene: Sure we should! But I'd like not to break the build when we will merge (hopefully soon) WICKET-6105. After we have merged it we will have all the time to migrate the code to the new extensions module. On Oct 7, 2017 5:32 PM,

Re: WICKET-6105 and WicketStuff

Sure we should! But I'd like not to break the build when we will merge (hopefully soon) WICKET-6105. After we have merged it we will have all the time to migrate the code to the new extensions module. On Oct 7, 2017 5:32 PM, "Maxim Solodovnik" wrote: > This make sense :) >

Re: WICKET-6105 and WicketStuff

This make sense :) I'll try to find some time and check some of these modules On Sat, Oct 7, 2017 at 10:10 PM, Sven Meier wrote: > Hi, > > IMHO we should set a good example by migrating these modules to use the new > classes in wicket-extensions. > We don't want to provide

Re: WICKET-6105 and WicketStuff

+1 Thanks for checking! On Sat, Oct 7, 2017 at 9:02 PM, Andrea Del Bene wrote: > Hi, > > WicketStuff is currently depending on Wicket 'wicket-datetime' for three > subprojects: > > - wicket-scala > > - inmethod-grid > > - wicketstuff-portlet-examples > > I think we should

WICKET-6105 and WicketStuff

Hi, WicketStuff is currently depending on Wicket 'wicket-datetime' for three subprojects: - wicket-scala - inmethod-grid - wicketstuff-portlet-examples I think we should replace it with the corresponding module we have migrated to WicketStuff. What do you think?

[ANNOUNCE] WicketStuff 6.28.0 Released

Joachim Rohde (1): Merge pull request #571 from jheek/feature/remove-double-markers Jonathan Heek (2): don't add js code twice fix indentation Konstantinos Karavitis (1): Merge pull request #591 from kkaravitis/wicket-6.x Martin Tzvetanov Grigorov (4): Build

Re: RedirectToUrlException seems to be broken in FF

Here is the quick start: https://github.com/solomax/ajax-download On Sat, Oct 7, 2017 at 12:40 PM, Maxim Solodovnik wrote: > Thanks for the clarifications Martin, > > According to [1] 'Ajax-Location' is being set instead of 'Location' > (due to redirect happens on ajax