There is an interesting article about converting JavaScript code from Prototype to jQuery. Here's small excerpt from this article:

Let me start off by saying I absolutely love Prototype. When a friend showed me how much it helped with writing cross-browser compatible code, I was an instant fan.

Over the years of being a Prototype user I paid close attention to the many posts about why X is a better framework than Y. I had always planned on at least TRYING another framework at some point to see what all the fuss was about.

Source: Perplexed Labs.

The new version of  Prototype library was released . Here's short excerpt from official announce:

Yesterday we released Prototype 1.6.0.3, the result of some much-needed bug fixes, and a stopgap release on the road to 1.6.1. It’s a backwards-compatible, drop-in replacement recommended for all users of Prototype 1.6. We’ve fixed 30 bugs and made 25 other improvements to our already-rock-solid library

Source: Prototype.

First release candidate of qooxdoo 0.8 is out. Here's small excerpt from official announce:

We are getting closer to qooxdoo 0.8 final: a first release candidate is available.

The first beta of qooxdoo 0.8 release with lots of changes and improvments. Read the full release info and download the new beta version from official qooxdoo site.

Michael Minella post a tutorial about unobtrusive event handling with Prototype JavaScript library. He writes:

«JavaScript is commonly used to add functionality to HTML documents.  There are two ways to do this, with level one event handlers or using unobtrusive JavaScript.  One allows you only to assign one event handler to an event at a time and is deeply coupled to your HTML markup.  The other allows you to assign as many event handlers to an event as you wish and completely removes JavaScript from your markup.  Do you know which is which?  This tutorial will cover what the difference is, why using unobtrusive JavaScript is a better approach and how to implement unobtrusive event handlers using the Prototype JavaScript library. »

Source:MichaelMinella.com.

Michael Galpin post an intresting tutorial about using Prototype and script.aculo.us libraries together. Here's the short list of topics discussed in this article:

• Introduction to Prototype

• Using Prototype's Ajax library

• Working with HTML

• Working with data

• Summary

Source: IBM developerWork.

Sebastian Brink has developed a nice looking gallery application called qGallery

It is really simple to use you just have to upload your images in full resolution together with a simple xml file and include the script and a simple div into the webpage. Everything else is done automatically. The gallery is creating every used image on the fly with the help of some php scripts in the background.

Source: http://ajaxian.com

A new version of Prototype Cheat sheet - a full reference for Prototype 1.6.0.2 released. Here's some notes about notations:

«Modules are sorted in a somewhat logical order - those commonly used are mostly in the left/center area, while deprecated/utility methods are all the way to the right

• Method can be recognized by parentheses following it (anything that doesn’t have ones is a property)

• Deprecated items are marked red and have NO parentheses/arguments specified

• Prototype extends quite few native objects’ prototypes with a set of convenient methods. In such cases there’s an explicit note about it next to a module name - i.g. stripScripts() method from “String (String.prototype)” can be called as 'foo'.stripScripts()

• When a module is also a class, there’s a “(constructor)” note next to it - i.g. “Hash (constructor)” means that it should be called as new Hash()

• There are few bonus items (such as those from Prototype.Browser) which are not yet included in documentation.»

Prototype 1.6.0.2 was released . This release fix o address several compatibility and performance issues and helps to protect against a potential security issue for developers using Prototype outside of a web browser environment. Was fixed 28 bugs and made over a dozen improvements to the code base, including performance improvements for CSS selectors in Safari 3 and for the Element#up/#down/#next/#previous and Event#findElement methods in all browsers.

The final versions of Prototype 1.6.0, script.aculo.us 1.8.0, and the Prototype & script.aculo.us book are now available. Prototype 1.6.0 is the most significant update to the framework since its inception over two years ago. We’re very excited about the changes in this release, and what better way to celebrate than with an update to script.aculo.us and a book covering all the new goodness?

Changes to the Class API

For example, in 1.6.0_rc0, where you’d write:

var Foo = Class.create(); Class.extend(Foo, { /* instance methods */ });

We’ve changed this so you now write:

var Foo = Class.create();
Foo.addMethods({ /* instance methods */ });

As in 1.6.0_rc0, you can still add instance methods directly from Class.create:

It has lots of new features such as:

• Event API Enhancements
• Function API Enhancements
• Function API Enhancements
• Class API Enhancements
• Ajax API Enhancements
• DOM API Enhancements
• Template API Enhancements
• Improved support for JavaScript 1.6 and WHATWG 1.0 standards

final version of 1.5.1 is here. The core team and dozens of contributors have fixed 30 bugs and introduced a slew of features and performance optimizations since 1.5.0. Here’s a look at the highlights of our best release yet.

One of most comon web developer's tasks is making HTML element s do some useful things when events are fired by browser, for example, when user's mouse cursor is hovered over the element.
Classic solution for this is attaching event handlers right in HTML code, i.e. <div onclick=...
A great approach for programmer when you have full access to source code, have enough skills to modify it etc. But sometimes you cannot control element's event handlers (imagine you write an article on some website, or you need some event handlers to a particular mod_mainmenu links in Joomla)
While surfing the Web, I've found a library that solves this problem  - Cruiser Behaviors library.
I'll show you how you can separate the content and it's behavior using this library. Let's make a HTML that displays Google PR retreived live from Google server without writing event handlers as HTML element properties. PR will be displayed as a tooltip for element, updated once per page display and displayed when user's mouse cursor hovers over the link