On 28/03/07, Jörn Zaefferer [EMAIL PROTECTED] wrote:
Michel Brouckaert schrieb:
If you have more time and the project would be a really big one, i
would advice you to rather use Prototype. Class based designs mostly
only pay off in huge projects because of reusability. So at the end of
I've started serious javascript programming using prototype
(including ajax).
I found javascript programming with prototype fun and easy.
Then I discovered jQuery.
And then I found javascript programming with prototype long and boring.
I think the jQuery way is far more efficient and clean.
thanks!
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
can you help me?
what benefits of JQuery vs prototype?(http://www.prototypejs.org/)
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
Hi Denis,
Best thing you can do is experiment with both and even throw in some
of the others (YUI, Dojo, Mochi, mootools) and see which style fits
you best. The benefits of using one over the other are going to vary
differently for different people and different projects.
Once you play around
I was a long time prototype user and have been taking jQuery for a spin
recently. I wrote a little about what I think at
http://musetracks.instantspot.com/blog/index.cfm/2007/3/22/jQuery-isSmooth.
On 3/27/07, Brandon Aaron [EMAIL PROTECTED] wrote:
Hi Denis,
Best thing you can do is
what benefits of JQuery vs prototype?(http://www.prototypejs.org/)
In reality, most js frameworks offer similar core functionality. What you're
usually comparing is syntax and general coding approach, which vary quite a bit
based on personal preferences. All frameworks are going to let you add a
Matt Kruse schrieb:
3) Prototype is tied closely to the Ruby on Rails community. If you use Ruby
on
Rails, definitely choose Prototype.
We're currently using Rails together with jQuery and I can't second
that. Although you loose some of the super-easy to implement helpers
(which produce
On Mar 27, 2007, at 10:47 AM, Matt Kruse wrote:
3) Prototype is tied closely to the Ruby on Rails community. If you
use Ruby on
Rails, definitely choose Prototype. Outside of that community I see
no reason
to choose Prototype over other frameworks like jQuery or even Moo.
If you must
have
Denis schrieb:
can you help me?
what benefits of JQuery vs prototype?(http://www.prototypejs.org/)
You may find jQuery's community very, very active, friendly and helpful.
Something I haven't seen or experienced in this form in any other open
source project.
Something that may weigh much
well,
I am on an internship, and i had a couple of weeks to learn how ajax worked,
implement it in code and then take it to a production level. I first tried a
couple of prototype based libary's and I have to say that if you need to be
programming quiet fast and have properly written code. you
Michel Brouckaert schrieb:
If you have more time and the project would be a really big one, i
would advice you to rather use Prototype. Class based designs mostly
only pay off in huge projects because of reusability. So at the end of
the line I think it depends...
I think reusing jQuery
Oh yeah, and also because of the Devo hat logo. It just does it for me. Hey
John, if you ever get tired of the New Wave Javascript tagline, how about
Whip Your Scripts Into Shape?
Haha! I like that a lot :-) Maybe that'll be the tag line for the
re-launched site. Or maybe something like
Hello,
I'm
new to this mailing list and have recently begun the process of evaluating
jQuery. After looking at a wide variety of _javascript_/Ajax libraries, I've
narrowed my choices down to jQuery and Prototype. Though I understand there's
nothing stopping me from using both, there's
You'd be surprised at how much functionality jQuery packs into such a
small package. I used to use prototype, but I've switched to jQuery
completely.
Maybe the largest piece of functionality you'll give up is access to
some of the other stuff that leverages prototype (e.g.
scriptaculous).
I would agree with Corey. We've been using jquery in a large scale application. We evaluated jquery and prototype a while back but were forced to start prototyping ui's quickly and so we picked jquery and figured we'd re-evaluate when implementation began.
We've never re-evaluated since there has
Im with Jonathan on this one. jQuery is the only library ive ever used, and its done everything ive ever needed.On 8/16/06, Jonathan Sharp
[EMAIL PROTECTED] wrote:I would agree with Corey. We've been using jquery in a large scale application. We evaluated jquery and prototype a while back but
http://jdsharp.us/code/jd_Menu/jd_Menu.html)Doesn't work in Safari 2.0.1___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
18 matches
Mail list logo
