Re: adding a listener to the AjaxRequestTarget
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 appendJavascript ?
yes, my bad :)
If we make a listener such as
IAjaxResponseListener {
[..]
sounds fine, do you need this in 2.0 only or 1.3 as well?
-igor
Re: adding a listener to the AjaxRequestTarget
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 itself.
you means appendJavascript ?
yes, my bad :)
If we make a listener such as
IAjaxResponseListener {
[..]
sounds fine, do you need this in 2.0 only or 1.3 as well?
-igor
I need that in 2.0 and in 1.3 as weel, I'm currently writing this
I give you a patch as soon as I finish
Thanks
--
Vincent
Re: adding a listener to the AjaxRequestTarget
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
prependjavascript()
and
you will only get that in the listener instead of the target itself.
you means appendJavascript ?
yes, my bad :)
If we make a listener such as
IAjaxResponseListener {
[..]
sounds fine, do you need this in 2.0 only or 1.3 as well?
-igor
I need that in 2.0 and in 1.3 as weel, I'm currently writing this
I give you a patch as soon as I finish
Thanks
--
Vincent
Re: adding a listener to the AjaxRequestTarget
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] 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 appendJavascript ?
yes, my bad :)
If we make a listener such as
IAjaxResponseListener {
[..]
sounds fine, do you need this in 2.0 only or 1.3 as well?
-igor
I need that in 2.0 and in 1.3 as weel, I'm currently writing this
I give you a patch as soon as I finish
Thanks
--
Vincent
Re: [jira] Commented: (WICKET-235) clean up info on site
-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 ] Eelco Hillenius commented on WICKET-235: +100 clean up info on site - Key: WICKET-235 URL: https://issues.apache.org/jira/browse/WICKET-235 Project: Wicket Issue Type: Bug Components: site Reporter: Eelco Hillenius Assigned To: Martijn Dashorst There is some horribly outdated stuff on the site, e.g. on the FAQ: http://wicket.sourceforge.net/faqs.html, 'How can I hide markup and/or components?' which uses a pre 1.0 way of using wicket ids. Any such information should be removed from the site, so that we end up just having some plain info that won't be outdated soon. For anything we have the WIKI and mailing list archives and examples etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. -- Vote for Wicket at the http://www.thebeststuffintheworld.com/vote_for/wicket Wicket 1.2.4 is as easy as 1-2-4. Download Wicket now! http://wicketframework.org
Re: [jira] Commented: (WICKET-235) clean up info on site
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: [ https://issues.apache.org/jira/browse/WICKET-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467112 ] Eelco Hillenius commented on WICKET-235: +100 clean up info on site - Key: WICKET-235 URL: https://issues.apache.org/jira/browse/WICKET-235 Project: Wicket Issue Type: Bug Components: site Reporter: Eelco Hillenius Assigned To: Martijn Dashorst There is some horribly outdated stuff on the site, e.g. on the FAQ: http://wicket.sourceforge.net/faqs.html, 'How can I hide markup and/or components?' which uses a pre 1.0 way of using wicket ids. Any such information should be removed from the site, so that we end up just having some plain info that won't be outdated soon. For anything we have the WIKI and mailing list archives and examples etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. -- Vote for Wicket at the http://www.thebeststuffintheworld.com/vote_for/wicket Wicket 1.2.4 is as easy as 1-2-4. Download Wicket now! http://wicketframework.org
Re: [jira] Commented: (WICKET-235) clean up info on site
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: [ https://issues.apache.org/jira/browse/WICKET-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467112] Eelco Hillenius commented on WICKET-235: +100 clean up info on site - Key: WICKET-235 URL: https://issues.apache.org/jira/browse/WICKET-235 Project: Wicket Issue Type: Bug Components: site Reporter: Eelco Hillenius Assigned To: Martijn Dashorst There is some horribly outdated stuff on the site, e.g. on the FAQ: http://wicket.sourceforge.net/faqs.html, 'How can I hide markup and/or components?' which uses a pre 1.0 way of using wicket ids. Any such information should be removed from the site, so that we end up just having some plain info that won't be outdated soon. For anything we have the WIKI and mailing list archives and examples etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. -- Vote for Wicket at the http://www.thebeststuffintheworld.com/vote_for/wicket Wicket 1.2.4 is as easy as 1-2-4. Download Wicket now! http://wicketframework.org
Re: [jira] Commented: (WICKET-235) clean up info on site
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 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] Eelco Hillenius commented on WICKET-235: +100 clean up info on site - Key: WICKET-235 URL: https://issues.apache.org/jira/browse/WICKET-235 Project: Wicket Issue Type: Bug Components: site Reporter: Eelco Hillenius Assigned To: Martijn Dashorst There is some horribly outdated stuff on the site, e.g. on the FAQ: http://wicket.sourceforge.net/faqs.html, 'How can I hide markup and/or components?' which uses a pre 1.0 way of using wicket ids. Any such information should be removed from the site, so that we end up just having some plain info that won't be outdated soon. For anything we have the WIKI and mailing list archives and examples etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. -- Vote for Wicket at the http://www.thebeststuffintheworld.com/vote_for/wicket Wicket 1.2.4 is as easy as 1-2-4. Download Wicket now! http://wicketframework.org -- Vote for Wicket at the http://www.thebeststuffintheworld.com/vote_for/wicket Wicket 1.2.4 is as easy as 1-2-4. Download Wicket now! http://wicketframework.org
Re: [jira] Commented: (WICKET-235) clean up info on site
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, Martijn Dashorst [EMAIL PROTECTED] wrote: 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 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 ] Eelco Hillenius commented on WICKET-235: +100 clean up info on site - Key: WICKET-235 URL: https://issues.apache.org/jira/browse/WICKET-235 Project: Wicket Issue Type: Bug Components: site Reporter: Eelco Hillenius Assigned To: Martijn Dashorst There is some horribly outdated stuff on the site, e.g. on the FAQ: http://wicket.sourceforge.net/faqs.html, 'How can I hide markup and/or components?' which uses a pre 1.0 way of using wicket ids. Any such information should be removed from the site, so that we end up just having some plain info that won't be outdated soon. For anything we have the WIKI and mailing list archives and examples etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. -- Vote for Wicket at the http://www.thebeststuffintheworld.com/vote_for/wicket Wicket 1.2.4 is as easy as 1-2-4. Download Wicket now! http://wicketframework.org -- Vote for Wicket at the http://www.thebeststuffintheworld.com/vote_for/wicket Wicket 1.2.4 is as easy as 1-2-4. Download Wicket now! http://wicketframework.org
Re: [jira] Commented: (WICKET-235) clean up info on site
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 incubator.apache.org/wicket. We can sync Confluence into that. Regards, Upayavira On 1/24/07, Martijn Dashorst [EMAIL PROTECTED] wrote: 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 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 ] Eelco Hillenius commented on WICKET-235: +100 clean up info on site - Key: WICKET-235 URL: https://issues.apache.org/jira/browse/WICKET-235 Project: Wicket Issue Type: Bug Components: site Reporter: Eelco Hillenius Assigned To: Martijn Dashorst There is some horribly outdated stuff on the site, e.g. on the FAQ: http://wicket.sourceforge.net/faqs.html, 'How can I hide markup and/or components?' which uses a pre 1.0 way of using wicket ids. Any such information should be removed from the site, so that we end up just having some plain info that won't be outdated soon. For anything we have the WIKI and mailing list archives and examples etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. -- Vote for Wicket at the http://www.thebeststuffintheworld.com/vote_for/wicket Wicket 1.2.4 is as easy as 1-2-4. Download Wicket now! http://wicketframework.org -- Vote for Wicket at the http://www.thebeststuffintheworld.com/vote_for/wicket Wicket 1.2.4 is as easy as 1-2-4. Download Wicket now! http://wicketframework.org
Re: [jira] Commented: (WICKET-235) clean up info on site
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
* 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 project with modules over the extracted distribution. So I can navigate through the source, the samples and the rest. The web site and the docs are not important. But I don't mind. If the projects are nicely structured I can even compile and start the sample applications without any hassle. I use this project to lookup how samples work, for api documentation and to look how the internals are implemented. Second step: I copy all the jar files I need to my repository to update my projects. The wicket-all distribution is a nice addition to people who want to get an overview over the current release quickly without getting into the details of the project's structures (subprojects and source/jar and distribution jars) in the maven repositories. +1. We need to have both the artifacts deployed to a central repository (for the Maven or Ivy users that already know Wicket), and the all-in-one package for the beginner to become acquainted with Wicket. Cheers, -- Jean-Baptiste Quenot aka John Banana Qwerty http://caraldi.com/jbq/ [1] http://www.nabble.com/Ant-%2B-Ivy-tf2667504.html#a7438702
