Comments
-
says:
prototype?
Sun, June 03 at 22:08 PM
-
says:
They all know how to choose a JavaScript library for the job?
Mon, June 04 at 06:07 AM
-
says:
I was surprised about the diversity and quantity of websites and companies using Prototype. There’s a bit of everything in there: cutting edge webapps, corporate websites, social networks, games(!), blogging tools, etc.
If I missed an exciting one – please let me know, I’ll add it to the Prototype website.
Mon, June 04 at 11:05 AM
-
says:
they dont know jQuery yet.
Mon, June 04 at 15:06 PM
-
says:
I’m quite proud of a product I developed for work which uses alot of prototype – libretto
It uses prototype along with Flash and externalInterface really heavily. And although it still has some cross browser issues I think it is coming along quite well :)
You can see an example of it in action by viewing the most recent issue of the Reverb Mag
Mon, June 04 at 20:22 PM
-
says:
Their layouts get hosed when they make an element invisible? Showing and hiding elements (or testing for visibility) is a nightmare for them?
Prototype has a lot of good things in it. Unfortunately, they are all balled into one huge file. And the failure to understand the difference between visibility and display doesn’t exactly inspire confidence in the rest of it.
BTW, that thread about the display property “bug” and the subsequent rant that the display property sucks was enough to induce vomiting. In that regard, it is Prototype’s design that sucks, not the w3c.
Sun, June 10 at 19:28 PM
-
says:
David, please stop reading my blog if it makes you sick ;)
Wed, June 13 at 07:58 AM
-
says:
Hey—thanks for adding the Globe and Mail! ;)
Greg
Mon, June 25 at 19:39 PM
-
says:
My pleasure!
Tue, June 26 at 21:30 PM
