Re: 1.3.0 beta4 release tomorrow (2007-10-07)

2007-10-06 Thread Nino Saturnino Martinez Vazquez Wael
But still one step closer to release:) Frank Bille wrote: And to spell it out: I'm not "releasing" tomorrow, only branching. So when that is done and I have build the artifacts I will create a vote for the actual release. :) Frank On 10/6/07, Frank Bille <[EMAIL PROTECTED]> wrote: Hey all

Re: 1.3.0 beta4 release tomorrow (2007-10-07)

2007-10-06 Thread Eelco Hillenius
On 10/6/07, Frank Bille <[EMAIL PROTECTED]> wrote: > And to spell it out: I'm not "releasing" tomorrow, only branching. So when > that is done and I have build the artifacts I will create a vote for the > actual release. :) Sounds good. Eelco

Re: 1.3.0 beta4 release tomorrow (2007-10-07)

2007-10-06 Thread Frank Bille
And to spell it out: I'm not "releasing" tomorrow, only branching. So when that is done and I have build the artifacts I will create a vote for the actual release. :) Frank On 10/6/07, Frank Bille <[EMAIL PROTECTED]> wrote: > > Hey all. > > Tomorrow around 08.00 GMT (AM), I will branch trunk int

1.3.0 beta4 release tomorrow (2007-10-07)

2007-10-06 Thread Frank Bille
Hey all. Tomorrow around 08.00 GMT (AM), I will branch trunk into our beta4 release. So if you want something fixes in beta4, please commit before that or submit patches (and notify me by replying here). Regards Frank

Re: wicket-contrib-input-events

2007-10-06 Thread Nino Saturnino Martinez Vazquez Wael
I was wondering about the mouse event part, arent there something of this in dojo, prototype.. So that part may be duplicate?? Nino Saturnino Martinez Vazquez Wael wrote: Hi As youve might have seen on the user list the input events contrib are ready for key binding (binding a components act

wicket-contrib-input-events

2007-10-06 Thread Nino Saturnino Martinez Vazquez Wael
Hi As youve might have seen on the user list the input events contrib are ready for key binding (binding a components action/event to forexample ctrl+s).. If you want you could check it out, and tell if anything could be done better, currently its the inputbehavior class that would be worth