[Wicket-user] Problem with javascript initialization order and header contributions

2007-02-05 Thread Erik van Oosten
Hi, I have some javascript with initialization code that needs functions from wicket-ajax.js. However, my javascript is loaded (and run) before wicket-ajax.js. The javascript is added in a component as follows: add(HeaderContributor.forJavaScript(this.getClass(), AutoLogout.js)); Is

Re: [Wicket-user] Problem with javascript initialization order and header contributions

2007-02-05 Thread Erik van Oosten
Oh, and euh, I am using a Wicket pre-1.2.5 snapshot from 2007-01-23. Erik van Oosten wrote: Hi, I have some javascript with initialization code that needs functions from wicket-ajax.js. However, my javascript is loaded (and run) before wicket-ajax.js. The javascript is added in a

Re: [Wicket-user] Problem with javascript initialization order and header contributions

2007-02-05 Thread Al Maw
Erik van Oosten wrote: Is there a way to force header contributions to load in a certain order? Sort of. HeaderContributors are designed so that if you add them twice, they only render once (so you can have multiple components on the page share the same contributor). Unfortunately,

Re: [Wicket-user] Problem with javascript initialization order and header contributions

2007-02-05 Thread Erik van Oosten
Al Maw wrote: Unfortunately, wicket-ajax.js is rendered as a kind-of composite HeaderContributor, so you can't just go like this: add(HeaderContributor.forJavaScript(AbstractDefaultAjaxBehavior.JAVASCRIPT); ...as you'll get two of them. :-( Yes, I noticed and saw the code. Are functions

Re: [Wicket-user] Problem with javascript initialization order and header contributions

2007-02-05 Thread Igor Vaynberg
On 2/5/07, Erik van Oosten [EMAIL PROTECTED] wrote: Yes, I noticed and saw the code. Are functions in wicket-ajax.js not intended for public use? if you asked me i would say no. these are our internal javascript functions. what out of there were you using exactly? -igor