Well, personally I would, but its not always possible its still
beta(some customer wont run beta software). A lot of fixes has been made
since 1.2.6. Upgrading our application took 3 man days, not so much the
application code but rather the tests we wrote, we ran into the
redirector bug, which
with 1.3 now
?
Cheers,
Daniel
--
View this message in context:
http://www.nabble.com/wicket-contrib-input-events-add-to-bamboo-or-maybe-migrate-to-wicket-stuff-minis--tf4589761.html#a13161141
Sent from the Wicket - Dev mailing list archive at Nabble.com.
of javascript reference)?
regards Nino
dtoffe wrote:
Hi !!
Well, I'm trying to make it work with Wicket 1.2.6, I started a test
project and copied the sources of wicket-contrib-input-events within my test
project. It complains in InputBehaviour:
public void rende
Hi !!
Well, I'm trying to make it work with Wicket 1.2.6, I started a test
project and copied the sources of wicket-contrib-input-events within my test
project. It complains in InputBehaviour:
public void renderHead(IHeaderResponse response) {
where IHeaderResponse is not
Guess wicket's perfect:)
Nino Saturnino Martinez Vazquez Wael wrote:
So what other cool features should be able for wicket, that might be
doable for a guy like me?
Hi
I'd like the input-event project to be available via the maven repo on
wicket stuff.
Hower this project did not become that complex, actually it just ended
up being a pretty simple behavior, so I thought that it might go into
the minis project or?
Btw javascript library used are BSD lic
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
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
