Re: adding a listener to the AjaxRequestTarget

2007-01-24 Thread Igor Vaynberg
On 1/24/07, Vincent Demay [EMAIL PROTECTED] wrote: if you _do_ need it to be called _during_ the rendering then we will have to extract an interface from the target that only has prependjavascript() and you will only get that in the listener instead of the target itself. you means

Re: adding a listener to the AjaxRequestTarget

2007-01-24 Thread Vincent Demay
Igor Vaynberg a écrit : On 1/24/07, Vincent Demay [EMAIL PROTECTED] wrote: if you _do_ need it to be called _during_ the rendering then we will have to extract an interface from the target that only has prependjavascript() and you will only get that in the listener instead of the target

Re: adding a listener to the AjaxRequestTarget

2007-01-24 Thread Igor Vaynberg
wonderful :) -igor On 1/24/07, Vincent Demay [EMAIL PROTECTED] wrote: Igor Vaynberg a écrit : On 1/24/07, Vincent Demay [EMAIL PROTECTED] wrote: if you _do_ need it to be called _during_ the rendering then we will have to extract an interface from the target that only has

Re: adding a listener to the AjaxRequestTarget

2007-01-24 Thread Vincent Demay
Ok it is done you could find a patch on jira : http://issues.apache.org/jira/browse/WICKET-234 Thanks for your help Igor Igor Vaynberg a écrit : wonderful :) -igor On 1/24/07, Vincent Demay [EMAIL PROTECTED] wrote: Igor Vaynberg a écrit : On 1/24/07, Vincent Demay [EMAIL PROTECTED]

Re: [jira] Commented: (WICKET-235) clean up info on site

2007-01-24 Thread Martijn Dashorst
-100 We already have the site up on apache: http://cwiki.apache.org/WICKETxSITE Martijn On 1/24/07, Eelco Hillenius (JIRA) [EMAIL PROTECTED] wrote: [ https://issues.apache.org/jira/browse/WICKET-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467112 ]

Re: [jira] Commented: (WICKET-235) clean up info on site

2007-01-24 Thread Eelco Hillenius
You might want to subtract 2 more if you want to win this :) Eelco On 1/24/07, Martijn Dashorst [EMAIL PROTECTED] wrote: -100 We already have the site up on apache: http://cwiki.apache.org/WICKETxSITE Martijn On 1/24/07, Eelco Hillenius (JIRA) [EMAIL PROTECTED] wrote: [

Re: [jira] Commented: (WICKET-235) clean up info on site

2007-01-24 Thread Igor Vaynberg
if we already have the site there, then why are we still hosting it on sf.net? -igor On 1/24/07, Martijn Dashorst [EMAIL PROTECTED] wrote: -100 We already have the site up on apache: http://cwiki.apache.org/WICKETxSITE Martijn On 1/24/07, Eelco Hillenius (JIRA) [EMAIL PROTECTED] wrote:

Re: [jira] Commented: (WICKET-235) clean up info on site

2007-01-24 Thread Martijn Dashorst
Because we are still not officially landed on apache. Same argument for the user list. Martijn On 1/24/07, Igor Vaynberg [EMAIL PROTECTED] wrote: if we already have the site there, then why are we still hosting it on sf.net? -igor On 1/24/07, Martijn Dashorst [EMAIL PROTECTED] wrote: -100

Re: [jira] Commented: (WICKET-235) clean up info on site

2007-01-24 Thread Upayavira
Igor Vaynberg wrote: umm, but we have a wiki, we dont need to redirect to wicket.apache.org but to apache.org/confluence/whateverstaticexportwhatchamaggicit During incubation, our Apache site is incubator.apache.org/wicket. We can sync Confluence into that. Regards, Upayavira On 1/24/07,

Re: [jira] Commented: (WICKET-235) clean up info on site

2007-01-24 Thread Igor Vaynberg
so lets, who do we bug to do that? -igor On 1/24/07, Upayavira [EMAIL PROTECTED] wrote: Igor Vaynberg wrote: umm, but we have a wiki, we dont need to redirect to wicket.apache.orgbut to apache.org/confluence/whateverstaticexportwhatchamaggicit During incubation, our Apache site is

Re: [jira] Commented: (WICKET-235) clean up info on site

2007-01-24 Thread Upayavira
Igor Vaynberg wrote: so lets, who do we bug to do that? I don't really know how to do it at this point, but I guess you could bug me. Upayavira

Re: Packaging our releases

2007-01-24 Thread Jean-Baptiste Quenot
* Ingo Adler: I'm not using Maven. I use Ant and Ivy. Me too. And I'd love to see Wicket using the successful combo, but this is not (yet) the case of others[1]. I like the wicket-all idea. One version - one distribution - one download. First step: I create (or copy) an IntelliJ