This! I second this!
I can imagine a stripped down version of Prototype that
has none of the DOM manipulation so it can coexist with all other
libraries and avoid dulicated features, and instead provide more of
those essentials like Enumerable and Class.
I've always seen Prototype JS as the
Prototype is still heavily used at The New York Times. And even though
we've begun incorporating jQuery into more of our projects I don't see
Prototype going away any time soon.
On Jul 13, 10:36 am, Cantrelle Vincent vcantre...@gmail.com wrote:
Dear all,
This is just a simple question related
I agree with T.J. We shouldn't be simply teaching just how to use a
certain tool but when to use them. And then learning JavaScript as a
language rather than merely being exposed to it via libraries is
beneficial because then your students will understand what the
libraries are doing. I think this
When using $.noConflict(); you need to load Prototype before loading
jQuery. The script tag for Prototype literally needs to be above the
script tag for jQuery.
When using noConflict I find the most useful way of separating the two
libraries logically is to assign jQuery a new name.
For
On Mar 19, 3:53 pm, T.J. Crowder t...@crowdersoftware.com wrote:
No, you don't. The order doesn't matter, as long as if you load jQuery
first, you make the `noConflict` before you load Prototype, e.g.:
script src='jquery.js'/script
scriptjQuery.noConflict();/script
script
Independent Software Consultant
tj / crowder software / comwww.crowdersoftware.com
On Jul 4, 6:24 pm, P.J. pjfontil...@gmail.com wrote:
Hi guys,
First off, here's a reference I'd like you to read so you'll
understand where I'm coming from.http://jqueryvsmootools.com/
It's written by Aaron
Hi guys,
First off, here's a reference I'd like you to read so you'll
understand where I'm coming from. http://jqueryvsmootools.com/
It's written by Aaron Newton and it's about jQuery and MooTools. Short
and sweet, jQuery focuses on the DOM, and does a pretty good job with
it; and MooTools
