The jQuery pitfall is to ... just start hacking. The moment you are juggling jQuery stuff to patch sloppy HTML created at runtime by last month's jQuery stuff, then you are back to square one.
If you are being "forced" :-) to move processing to the browser, the book I recommend is "Single Page Web Applications", ed. Manning. It provides a useable solution in pure Javascript, based on the module pattern (see "JS: The Good Parts", already endorsed elsewhere). It still uses jQuery for event mgmt and -simple- DOM selectors, but here jQuery is meant as a tool not as the driver, which it never should be. [If you asked me, I'd say JS development is definitely NOT a shame. JS is a great language. But this is OT.] :-) On Thursday, January 17, 2013 12:33:54 PM UTC+1, Jan Goyvaerts wrote: > > And it has come to that - forced into JS development ! Shame ! :-p > > But I've got to admit jquery allows you to pull off tricks that would be > very difficult server side. so there's no escaping it any more. ;-) > > Can somebody recommend lecture for both the subjects ? > > Thanks, > > Jan > > > > > -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/BObVyGGCwfUJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
