approach, but I just wanted to know if there are any plans to rework
this in Wicket, or if the current approach is just as good?
-- Edvin
--
View this message in context:
http://www.nabble.com/Wicket-and-inline-JavaScript-tp17402101p17404025.html
Sent from the Wicket - User mailing list archive
I am currently in a project where we do everything with jQuery in the
frontend, simulating Wicket's AJAX input and using its AJAX output.
However, I would not advice in doing this until you have a strong grasp
of Wicket's form and AJAX handling. Having a good jquery programmer
helps too.
html/javascript to decide what's the better
approach, but I just wanted to know if there are any plans to rework
this in Wicket, or if the current approach is just as good?
-- Edvin
--
View this message in context:
http://www.nabble.com/Wicket-and-inline-JavaScript-tp17402101p17404025.html
Hi,
I have a webdesigner who keeps harassing me with the way Wicket does
JavaScript, attaching behaviour to onclick events etc. instead of doing
it the jquery way of picking up the components and attaching the
events afterwards, thus keeping all the nasty bits away from the actual
markup.
://www.nabble.com/Wicket-and-inline-JavaScript-tp17402101p17404025.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi Ned,
thanks for your reply. I agree with your point of view. Today, however,
we got bitten because the designer wanted to change all buttons by
hiding them with jquery, and adding an anchor right after it in the
dom-tree, so he could style them the way he wanted it (not possible with
JavaScript, so I thought I'd be nice to hear some opinions :))
-- Edvin
--
View this message in context:
http://www.nabble.com/Wicket-and-inline-JavaScript-tp17402101p17417072.html
Sent from the Wicket - User mailing list archive at Nabble.com
