Am I wrong to say you should never use onclick in an element as this would be contrary to the purpose of using jQuery which means onclick would totally bind mark-up to javascript? So it would not be unobtrusive in that case. -- View this message in context: http://www.nabble.com/Don%27t-use-onclick-tp25865558s27240p25865558.html Sent from the jQuery General Discussion mailing list archive at Nabble.com.
I don't think it's too hyped. Having calls to javascript in your elements defeats the purpose of unobtrusively maintaining and using libraries like jQuery. How can you stay that Rob??
>>>I think you have your design priorites backward. Firstly determine the functionality required, then how to best implement it. If that means using a library obviously we're past that point. We've decided this was a good use for jQuery. So how can you say priorities are tangled here when you assume we're overthinking this because we're using a library. It sounds as though you're a bit anti-new, stay hard core javascript type of dude. If you're using javascript to make an entire application fine, but I'm in with the new and new to me makes sense. Unobtrusive is not overrated, it's good practice and it's a pattern as far as I'm concerned.
The simple fact that you don't have javascript floating all over your doc inside elements is alone a reason that unobtrusive rocks. Let alone many other reasons.
Rob, keeping all JS outside of the HTML is a good practice, and keeps everything nice and easy to maintain. Jonathan Vanherpe (T & T NV) wrote: > > RobG wrote: > >> On Oct 13, 1:34 pm, expresso<dschin...@gmail.com>
Leave a comment on radioactivity's reply
Change topic type
Link this topic
Provide the permalink of a topic that is related to this topic