wicket-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Grigorov <mgrigo...@apache.org>
Subject Re: Wicket 6 - JavaScriptHeaderItem renders too early
Date Thu, 23 Jan 2014 14:28:00 GMT
Hi,

Read http://wicketinaction.com/2012/07/wicket-6-resource-management/

Martin Grigorov
Wicket Training and Consulting


On Thu, Jan 23, 2014 at 4:24 PM, Entropy <blmulholland@gmail.com> wrote:

> Hello, I am just converted to Wicket 6, and I have a line like this in one
> component:
>
> response.render(JavaScriptHeaderItem.forScript(writeGridJS(), getId() +
> "_js"));
>
> That writes some custom javascript which in turn run when Ext.onReady() is
> ready.  However, this script generated so early that not only is the DOM
> not
> ready, Ext itself hasn't even been defined.  My header item is the second
> item in the <HEAD>, and the Ext include is 3rd from last.  Even moving the
> ext include to the top of the .html, it is still well below the code and
> does not run in time.
>
> How can I make my header item render at the BOTTOM of the <head> instead of
> at the top?
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Wicket-6-JavaScriptHeaderItem-renders-too-early-tp4663910.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message