News from jsdevtools.com

Yahoo! User Interface Blog: YUI: Open Hours Friday Sept 3rd

Thu, 02 Sep 2010 21:53:37 -0000

For those of you that don’t subscribe to the YUI calendar or YUILibrary.com forum, the next installment of YUI: Open Hours will be this Friday the 3rd. The topic of this week’s call will be performance. How and what to measure in your module code, and techniques and tools for measuring various aspects of site [...]

Yahoo! User Interface Blog: Ask Satyam: Writing Clean, Debuggable Code

Thu, 02 Sep 2010 15:13:25 -0000

Satyam (a.k.a Daniel Barreiro) is a long-time YUI contributor and one of the most prolific, generous experts in the YUI forums. He is also the author of a new book on YUI 2.8.0, YUI 2.8.0: Learning the Library. This article in the “Ask Satyam” series was suggested by JoeDev. While its focus (like [...]

Sencha Blog: Implementation Spotlight: Kohive

Wed, 01 Sep 2010 22:47:56 -0000

Kohive is an online collaboration tool for teams to work together. They can create separate virtual desktop workspaces called hives where they can share and interact with each other in real time. Kohive used Ext JS for implementation of advanced data as well as a comprehensive and beautiful user interface.

Yahoo! User Interface Blog: YUI Theater — Douglas Crockford: “Crockford on JavaScript — Scene 6: Loopage” (52 min.)

Mon, 30 Aug 2010 23:47:40 -0000

Douglas Crockford’s latest installment in the “Crockford on JavaScript” series, a talk in which he covers the role of event loops and the importance of server-side JavaScript, is now available on video. Flash video is embedded below, or you can download the HD video (480p ~370MB). Video from the first five lectures is [...]

qooxdoo News: The week in qooxdoo (2010-08-27)

Fri, 27 Aug 2010 16:45:58 -0000

Another week in retrospect: Deprecated code With revision r23139, we removed the deprecated code introduced with version 1.2 of qooxdoo. So now trunk is completely free of deprecations again. For more details, take a look at the corresponding bug report. Using a deputy We had a request to add the possibility to specify a deputy as a model in [...]

Sencha Blog: Tips and Tricks for Ext JS Component Developers

Fri, 27 Aug 2010 16:40:19 -0000

Ext JS ships with all the components that you need to build even very sophisticated applications. But, there are occasional cases where you might need to write a custom component. Luckily, the Sencha Community has a rich ecosystem full of quality components for developers to use. Here, we'll cover a few tips and tricks that component authors can use to enhance their user extensions.

Official jQuery Blog: The Official jQuery Podcast – Episode 32 – Dave Ward

Fri, 27 Aug 2010 15:08:28 -0000

Our guest this week is Dave Ward (http://encosia.com), who is the co-host of the Tekpub video series on jQuery, Mastering jQuery. We talk about the Tekpub series as well as caching lengths with the Google CDN and Microsoft CDN amoungst other CDN features. We also learn when you shouldn’t wait for the document to ready to [...]

Yahoo! User Interface Blog: Introducing Yeti: The YUI Easy Testing Interface

Wed, 25 Aug 2010 23:16:54 -0000

Testing JavaScript is an important but often overlooked part of web development. One reason is because developing for the web means targeting more than one browser. YUI currently classifies 11 different environments that enjoy our highest support level. In addition, we also test YUI on emerging X-grade environments like mobile devices. When you have so [...]

UIZE JavaScript Framework | Latest News: 2010-08-25 - NEW MODULE: Uize.Array

Wed, 25 Aug 2010 07:00:00 -0000

The new Uize.Array module defines a namespace for various modules that provide array specific functionality or utilities. To kick things off, the new Uize.Array.Order module under the Uize.Array namespace provides functionality for changing the order of elements in an array, with support for reversing, jumbling, specialized sorting, and more.

UIZE JavaScript Framework | Latest News: 2010-08-25 - NEW MODULE: Uize.Array.Order

Wed, 25 Aug 2010 07:00:00 -0000

The new Uize.Array.Order module provides functionality for changing the order of elements in an array, with support for reversing, jumbling, inside to out, etc. Unlike sorting an array based upon the values of its elements, the methods of the Uize.Array.Order module allow you to reorder the elements according to different patterns - without respect to the element values. For example, the Uize.Array.Order.reverse method reverses the order of the elements in an array. The Uize.Array.Order.jumble method jumbles (randomly shuffles) the elements in an array. The Uize.Array.Order.insideOut method reorders the elements from inside to out by starting with the inner elements and moving outwards in both directions to reach the start and the end of the array, while the Uize.Array.Order.outsideIn method reorders the elements from outside to in by starting with the outer elements and moving inwards in both directions to reach the inner elements.

jQuery UI Blog: Extensible Autocomplete

Wed, 25 Aug 2010 00:44:36 -0000

The release of the Autocomplete widget in jQuery UI 1.8 was a pretty important milestone for the jQuery UI team. If you’ve looked at the widget, you may have noticed that there are only four options, far fewer than our other plugins. Unlike progressbar, our plugin with the fewest options, Autocomplete’s small API isn’t a [...]

Official jQuery Blog: jQuery Conference 2010: Boston Announcement

Tue, 24 Aug 2010 21:28:14 -0000

The jQuery Project is very excited to announce the jQuery Conference 2010: Boston on October 16-17, 2010. The conference will be held at the Hilton Boston Logan in Boston, Massachusetts. The best part of this announcement is that Tickets are on sale now! This venue is the largest that the project has worked with to date [...]

Yahoo! User Interface Blog: Developing an Accessible Star Ratings Widget

Tue, 24 Aug 2010 17:00:41 -0000

/* * for the forms in this article */ .tjk-form {margin-bottom:3em;} /* **************************** Image Replacement Techniques **************************** * * A la Yahoo! Music * the original sprite is vertical and the styling is slightly different */ #noticias .tjk-spans span, .tjk-spans span { background:transparent url(http://yuiblog.com/assets/starTutorial/sprite.png) no-repeat scroll 0; font-size:0; height: 19px; overflow:hidden; vertical-align:middle; width: 96px; display: block; } .tjk-spans em { display:block; } .tjk-spans .r15 { background-position:-385px 0; } .tjk-spans [...]

Sencha Blog: Resolution Independent Mobile UI

Mon, 23 Aug 2010 20:02:12 -0000

As device displays become denser and denser, finding the right method for creating resolution independent UI elements will become more and more important. This article shows you how to make your own scalable UI elements for WebKit.

qooxdoo News: The week in qooxdoo (2010-08-20)

Fri, 20 Aug 2010 19:05:19 -0000

Welcome back to another regular round-up of the week. Overflow handling As promised last week when we announced the new overflow feature, we updated our applications to benefit from the toolbar overflow handling. We added specific code to the feed reader, api viewer and playground. To see it in action, resize your browser window and notice the toolbar [...]

Official jQuery Blog: The Official jQuery Podcast – Episode 31 – Filament Group

Fri, 20 Aug 2010 01:09:37 -0000

In our 31st episode, we talk with the team at Filament Group, Todd Parker, Patty Toland and Scott Jehl. Filament Group is a design firm in Boston, MA and both Todd and Scott are members of the jQuery team. We discuss ThemeRoller, which Filament Group created as well as Progressive Enhancement and their [...]

Yahoo! User Interface Blog: Announcing YUI 3.1.2: Critical Security Update for All YUI 3.1.x/3.2.0pr1 Users

Thu, 19 Aug 2010 20:35:17 -0000

The YUI team released YUI 3.1.2 today. This is an important security update for all users of YUI 3.1.x and 3.2.0pr1. If you are hosting YUI 3.1.x or 3.2.0pr1 on your site, or if you use YUI 3.1.x/3.2.0pr1 IO’s cross-domain functionality, you are affected. XDR in YUI’s IO utility implements a Flash transport as [...]

Yahoo! User Interface Blog: Quick Edit mode for YUI 2 DataTable

Thu, 19 Aug 2010 16:42:03 -0000

YUI 2 DataTable provides slick inline editing. When disableBtns is turned on in the column configuration, editing simple values like strings or numbers feels just like Excel. However, the experience cannot be as responsive as a desktop application because each change typically requires an XHR call to the server to store (or reject!) [...]

Yahoo! User Interface Blog: Using YUI 2 on the DuckDuckGo Search Engine

Thu, 19 Aug 2010 13:41:07 -0000

DuckDuckGo is a search engine that uses YUI extensively. Here’s what it uses in particular: ImageLoader. Matt Mlinac’s YUI 2 ImageLoader was the first thing I implemented and what originally hooked me on YUI for this project. DuckDuckGo has favicons next to results and often has “Zero-click Info” above results that usually includes an image. I [...]

Sencha Blog: BlackBerry Torch: The HTML5 Developer Scorecard

Wed, 18 Aug 2010 20:00:31 -0000

RIM's latest smart phone, the BlackBerry Torch 9800, just came to market with a first class Webkit browser. We were anxious to run some tests and see how it stacks up.

Yahoo! User Interface Blog: Implementing YUI on the Assembla.com Agile Planner

Wed, 18 Aug 2010 14:35:45 -0000

Fast and fun – that was the user requirement for the new Assembla.com Agile Planner – an AJAX interface for adding development tasks, building story/feature outlines, and scheduling them into releases. We were lucky to have YUI 3 to make it fast and fun to implement as well. I had used YUI 2 for a [...]

Twitter / jquerytools: jquerytools: jQuery Tools 1.2.4. Sound and solid. Release notes: http://bit.ly/dzPXAp

Wed, 18 Aug 2010 09:38:54 -0000

jquerytools: jQuery Tools 1.2.4. Sound and solid. Release notes: http://bit.ly/dzPXAp

Yahoo! User Interface Blog: Ask Satyam: Row Expansion and Nested DataTables

Tue, 17 Aug 2010 19:06:04 -0000

Sencha Blog: Using the Data Package in Sencha Touch

Tue, 17 Aug 2010 18:22:37 -0000

This tutorial shows how to quickly put together simple components backed by the data package. See how the Model/Store/Proxy ecosystem fits together and how to use Stores with data-aware components, just like in our Sencha Touch Twitter example.

UIZE JavaScript Framework | Latest News: 2010-08-17 - IMPROVED MODULE: Uize.Widget.Collection.Dynamic

Tue, 17 Aug 2010 07:00:00 -0000

The Uize.Widget.Collection.Dynamic module has been improved with the addition of support for the touch interface of Apple's iPad. With the updated version of this module, it is now possible to reorganize the items in a collection using the Apple iPad's touch interface. This is demonstrated in the Dynamic Collection example, which has been updated with selection checkboxes for the collection item widgets to allow non-contiguous selection of multiple items.

jQuery UI Blog: The jQuery Project is Proud to Announce the jQuery Mobile Project

Fri, 13 Aug 2010 20:23:28 -0000

Mobile web development is an emerging hot topic in the web development community. As such, the jQuery Team has been hard at work on determining the strategy and direction that the jQuery Project will take. Today, we are proud to announce the jQuery Mobile Project. We’ve launched a new site at jquerymobile.com that [...]

Official jQuery Blog: The jQuery Project is Proud to Announce the jQuery Mobile Project

Fri, 13 Aug 2010 20:17:43 -0000

qooxdoo News: The week in qooxdoo (2010-08-13)

Fri, 13 Aug 2010 17:25:02 -0000

Hi all! The weekly wrap-up of happenings in and around qooxdoo is here. Team A new member has joined the core team here at 1&1. It's Tino Butz, and Tino is no stranger to us. We have been working together for quite some time, since Tino was formerly on the Gmx.com mail client team. As a consequence, [...]

Official jQuery Blog: jQuery London 2010 Postponed

Fri, 13 Aug 2010 16:06:40 -0000

After much deliberation, The jQuery Project Operations Team has decided to postpone our planned London event this year. Unfortunately, we were unable to secure a suitable venue that would allow us to provide the type of professional-quality event the community has come to expect within a budget sustainable by the project. We regret any inconvenience [...]

Sencha Blog: Ext JS 3.3 Beta 2 Released

Thu, 12 Aug 2010 23:11:20 -0000

We are pleased to announce the immediate availability of Ext JS 3.3 beta 2. This release addresses a few issues that appeared in the first beta, as well as adding enhancements for the PivotGrid and Calendar components.

Sencha Blog: Infinite Ajax Carousel

Tue, 10 Aug 2010 19:16:10 -0000

In a forthcoming demo app of a shopping browser, we'll be showcasing an "infinite carousel", a new feature of our carousel component that we'll be releasing as part of Sencha Touch. The major feature of the infinite carousel is active DOM management that keeps the web app within the iPad's memory limits.

jQuery UI Blog: jQuery UI 1.8.4

Tue, 10 Aug 2010 12:52:47 -0000

The fourth maintenance release for jQuery UI 1.8 is out. This update brings bug fixes for the Droppable, Resizable, Selectable and Sortable interactions as well as the Accordion, Autocomplete, Button, Datepicker Dialog, Progressbar, Slider and Tabs widgets. jQuery UI 1.8.3 was released a few days prior to 1.8.4, but there was a problem with the [...]

qooxdoo News: Download qxoo now!

Tue, 10 Aug 2010 12:50:05 -0000

The last couple of days we had some time to use our new qxoo package, which you might already have read about, and did some experiments with it. All of us here in the core team like it so much we thought we had to write another blog post to show some details on how to [...]

qooxdoo News: The week in qooxdoo (2010-08-06)

Fri, 06 Aug 2010 13:20:43 -0000

Hi all! After an exciting week, here comes the usual round-up. qooxdoo Releases This week saw the joint release of qooxdoo 1.2 and 1.1.1. Hope everybody is enjoying it . qxoo We have managed to build a single JavaScript file including the whole qooxdoo OO layer which can be used in non-browser environments. See more details in [...]

UIZE JavaScript Framework | Latest News: 2010-08-06 - NEW MODULE: Uize.Node.Util

Fri, 06 Aug 2010 07:00:00 -0000

The new Uize.Node.Util module provides a home for miscellaneous node related methods that are too esoteric to belong in the base Uize.Node module. Along with creating a home for esoteric node related methods to be developed in the future, a handful of static methods already in the Uize.Node module that were judged to be too esoteric to be in that module were migrated out into the new Uize.Node.Util module, thereby reducing the size of the Uize.Node module that is relied upon heavily by other code. The migrated methods include: Uize.Node.getEffectiveBgColor, Uize.Node.getOpacityProperties, Uize.Node.getOpacityStr, Uize.Node.showInLayoutFlow, and Uize.Node.stylePropertiesAsStr. This change is not backwards compatible. If you had code that was relying on the static methods that have been migrated into the new Uize.Node.Util module, then you will have to modify that code to require the Uize.Node.Util module and to call the methods in that module.

qooxdoo News: Expanding qooxdoo to …

Thu, 05 Aug 2010 12:31:13 -0000

It has been a topic a couple of times on our mailing list, to bring the OO layer of qooxdoo to non-browser environments. I took some time after the last release to check what's necessary and build a proof of concept. That went so well that I included it into the framework to make it [...]

qooxdoo News: qooxdoo 1.2 and 1.1.1 released

Wed, 04 Aug 2010 17:38:22 -0000

We are happy to announce another joint release of the qooxdoo framework. You can download versions 1.2 and 1.1.1, the corresponding release notes and manuals are online as well. The qooxdoo 1.2 release comes with substantial improvements in almost the entire range of the framework. Here is a brief overview: The entire manual is now in SVN, [...]

qooxdoo News: Contribution Demobrowser

Wed, 04 Aug 2010 16:59:58 -0000

As you surely all know, qooxdoo-contrib is the project's place for hosting various contributions and therefore a vital part of the qooxdoo ecosystem. We always try to improve things there, so here's a preview of a feature we've been working on for quite a while now. There's a lot of great projects in qooxdoo-contrib, but the [...]

UIZE JavaScript Framework | Latest News: 2010-08-03 - NEW MODULE: Uize.Node.Classes

Tue, 03 Aug 2010 07:00:00 -0000

The new Uize.Node.Classes module is a package module with static methods to facilitate manipulation of the value of the className property of DOM nodes, with support for adding classes, removing classes, toggling classes, and lots more. The methdos of the Uize.Node.Classes module make it much easier to manipulate classes than it would be to use regular expressions, and one's code becomes easier to read and more elegant. In addition to ease of use, the Uize.Node.Classes module introduces a powerful, higher level construct called a state. The State Related Methods that support the state paradigm make it much easier to manage the classes in the className property of a node to reflect application state.

qooxdoo News: The week in qooxdoo (2010-07-30)

Sun, 01 Aug 2010 20:18:32 -0000

Another weekly status report right before the releases planned for next week. Upcoming Releases This week we continued and intensified our efforts towards the upcoming releases. According to our release scheme, it is again a joint release of a minor release (qooxdoo 1.2) and a patch release (qooxdoo 1.1.1). The ramp-down plan has already be announced on [...]

Official jQuery Blog: The Official jQuery Podcast – Episode 30 – Chris Coyier

Fri, 30 Jul 2010 15:54:16 -0000

In our 30th episode, we talk with Chris Coyier of CSS-Tricks. Chris also works for Wufoo, an online form builder service. Chris talks about his inspiration for writing for CSS-Tricks and we look at his jQuery snippets, freebies and screen casts. We learn what Wufoo is and talk about the new API [...]

Sencha Blog: Announcing Ext JS 3.3 Beta – PivotGrids, Calendars and More

Wed, 28 Jul 2010 20:21:02 -0000

We are pleased to announce the availability of Ext JS 3.3 beta 1 for immediate download. This release introduces great new Calendar and PivotGrid components, plus over 160 enhancements and bug fixes.

qooxdoo News: EuroPython2010

Mon, 26 Jul 2010 09:38:09 -0000

I've just returned from Birmingham where EuroPython, the European Python conference, has been held for the second time in successive years. The organizers have done a tremendous job to make it a friendly and productive conference. I attended the preceding tutorial days, taking a full-day tutorial on py.test by Holger Krekel, a half-day introduction to [...]

UIZE JavaScript Framework | Latest News: 2010-07-24 - NEW EXAMPLE: 3D Rotation Viewer

Sat, 24 Jul 2010 07:00:00 -0000

The new 3D Rotation Viewer example demonstrates how to easily create a slick 3D rotation viewer in UIZE that lets users rotate the view of an object a full 360 degrees using a mouse, or finger on the Apple iPad. The example is inspired by a showcase example by Apple of HTML5 technologies. The UIZE implementation works in pretty much all browsers, with no need for HTML5 or CSS3 features. This was an exercise in seeing how easy it would be to create an equivalent experience in UIZE. It was easy, taking less than a day. The code is all original, with absolutely no referencing of Apple's code (but thanks to Apple for their delicious iPod Touch products, and for their fabulous photos of said products). In the example, an instance of the Uize.Widget.Drag class is being used to create a simple 3D rotation viewer. Using a mouse, you can click and drag to rotate the 3D image. On an Apple iPad, you can use your finger. The viewer implements a deceleration behavior - the speed at the time of release determines how long it will take to spin down to a stop. When the page loads initially, the image is animated 360 degrees clockwise. Buttons beneath the viewer let you trigger other kinds of spins.

UIZE JavaScript Framework | Latest News: 2010-07-22 - Improved Unit Tests

Thu, 22 Jul 2010 07:00:00 -0000

The unit tests suite for the UIZE JavaScript Framework, implemented in the Uize.Test.UnitTests module, has been improved with the addition of basic loadability tests for all modules for which dedicated test modules have not yet been written. All modules for which dedicated tests have not yet been written are now automatically tested at least for loadability. Also, all modules of the UIZE JavaScript Framework are now designed to be safe to load in a non-browser context, such as Microsoft's Windows Script Host. There were some modules that would fail to load because certain aspects of the initialization of the modules relied on specific features exposed by a Web browser, such as the window, document, and navigator objects. These modules have been updated to deal gracefully with the non-existence of those objects in non-browser contexts. This allows an automated unit test system to at least verify that these modules can be loaded and that their code does not contain fatal syntax errors or other crippling errors of initialization / module setup - without having to involve a Web browser. Features of the modules may still not be usable in a non-browser context, but at least the modules can be sanity checked for basic well-formedness of the JavaScript. This is particularly helpful for the automatic testing of the loadability of the scrunched versions of modules.

jQuery UI Blog: productivity.appendTo( jQuery.ui )

Wed, 21 Jul 2010 19:59:02 -0000

Like most open source projects, jQuery UI is maintained by a team of developers volunteering their spare time to the project. While we’ve been very productive at times, occasionally the team gets busy and productivity slows, sometimes almost to a halt. With new plugins to design and build, old plugins to maintain, and a growing [...]

Sencha Blog: Ext GWT 2.2 Beta Released

Wed, 21 Jul 2010 17:08:03 -0000

The Ext GWT team is happy to announce the availability of Ext GWT 2.2.0 beta. This release brings several improvements and new features. A full change log and online documentation can be found on the download page.

Sencha Blog: HTML5 Family: CSS3 Ads Versus Flash Ads

Tue, 20 Jul 2010 21:07:18 -0000

We thought we'd see if you can really duplicate popular Flash ads in HTML5 and CSS3. Take a look at these popular Flash ads and compare them to our CSS3 recreations. It's a little uncanny.

Official jQuery Blog: jQuery Conferences 2010: Call for speakers

Tue, 20 Jul 2010 15:14:11 -0000

We’d like to open up submissions for talks for our conferences in London and Boston. The dates are currently being firmed up, but currently we’re eyeing these days: London: Sept 13-14 Sept 8-9th or the 22-23rd; Boston: Oct 16-17. Please fill out the form if you’re interested in speaking at either of these events. We will [...]

UIZE JavaScript Framework | Latest News: 2010-07-15 - NEW EXAMPLE: UIZE Unit Tests

Thu, 15 Jul 2010 07:00:00 -0000

The new UIZE Unit Tests example lets you select and run any of the test modules of the UIZE JavaScript Framework. In the example, a test module selector lets you choose your test module. On selecting a test module, the test module is loaded dynamically. After it has loaded, you can use the "START TESTS" button to start running the tests contained inside the selected test module. While the tests are being performed, a progress bar is updated to show how far you are through the tests. Also, a log is written to with details of the tests being performed. You can stop the tests at any time using the "STOP TESTS" button. If one of the tests fails (none should, of course), test execution is aborted and a synopsis of the failure is displayed in a dialog. To run the entire test suite for the UIZE JavaScript Framework, you can select the Uize.Test.UnitTests test module.

UIZE JavaScript Framework | Latest News: 2010-07-11 - NEW EXAMPLE: Digital Clock

Sun, 11 Jul 2010 07:00:00 -0000

The new Digital Clock example shows how the Uize.Widget.SegmentDisplay.Seven widget class can be used to easily create a digital clock that shows hours, minutes, and seconds. In the example, six seven segment display widgets are used - two for the hours display, two for the minutes display, and two for the seconds display. After the page loads and is initialized, a timer/interval is started that updates the clock's display every second. For every update, the current time is queried using JavaScript's Date object and formatted to an HHMMSS string using the Uize.Date.Formatter.format method of the Uize.Date.Formatter module, specifying the string value '{hh}{mm}{ss}' for the date format. From the formatted string, the first character is used to set the value of the hours display's tens widget, and the second character is used to set the value of the hours display's ones widget. In a similar manner, the third and fourth characters of the formatted date string are used for the minutes display's two seven segment display widgets, and the last two characters of the formatted date string are used for the seconds display's two widgets.

Official jQuery Blog: The Official jQuery Podcast – Episodes 28 & 29

Fri, 09 Jul 2010 20:00:07 -0000

Episode 28 – Remy Sharp Part 3 – jQuery for Designers In our final part with Remy Sharp we talk about his jQuery for Designers site. jQuery for Designers is a tutorial and screencast site which caters to designers and how to use jQuery to add interactive elements to your site. We discuss the [...]

UIZE JavaScript Framework | Latest News: 2010-07-07 - NEW MODULE: Uize.Widget.Log

Wed, 07 Jul 2010 07:00:00 -0000

The new Uize.Widget.Log module implements a very basic logging widget, to serve as a base class for more specialized logging widget subclasses. The Uize.Widget.Log class provides very basic support for displaying messages in a logging pane, with a clear button that lets the user clear logged messages. The Uize.Widget.Log widget class serves as the base class for the more specific Uize.Widget.Log.InstanceEvents widget class. Examples of the logging widget in action can be seen in the Button and Virtual DOM Events examples.

UIZE JavaScript Framework | Latest News: 2010-07-07 - NEW EXAMPLE: Button

Wed, 07 Jul 2010 07:00:00 -0000

The new Button example provides a demonstration of the features of the Uize.Widget.Button widget class. In the example, an instance of the Uize.Widget.Button widget class is instantiated and wired up. A log widget is used to log the instance events that occur for the button widget. Interacting with the widget will cause events to be fired, and those events will appear in the log. The log displays both the custom instance events that are fired using the button widget's fire method, as well as all Changed.* property change events that result from values of the button's various set-get properties being changed (so, the log can be used to watch for changes in the state of the button widget). Below the instance event log for the button is a set of links for testing aspects of the programmatic interface of the button widget. A "TOGGLE ENABLED" link toggles the value of the button's enabled set-get property. A "TOGGLE BUSY" link toggles the value of its busy set-get property. A "TOGGLE SELECTED" link toggles the value of its selected set-get property. Finally, a "CHANGE BUTTON TEXT" link changes the value of its text set-get property.

UIZE JavaScript Framework | Latest News: 2010-07-07 - NEW MODULE: Uize.Widget.Log.InstanceEvents

Wed, 07 Jul 2010 07:00:00 -0000

The new Uize.Widget.Log.InstanceEvents module implements a log interface for logging the instance events of an instance of a Uize subclass. The Uize.Widget.Log.InstanceEvents module provides a convenient way to easily present a log of all the instance events that occur for an instance of a Uize subclass, including custom instance events that are fired using the instance's fire method, as well as all Changed.* property change events that result from values of the instance's various set-get properties being changed. This means that you can use a Uize.Widget.Log.InstanceEvents instance to watch for changes in the state of some other instance. The instance for which instance events are logged can be an instance of any Uize subclass - not just widget classes.

script.aculo.us web 2.0 javascript: Online JavaScript Master Classes in July 2010, US-friendly time zones!

Wed, 30 Jun 2010 20:26:00 -0000

Dear script.aculo.us user!

We're announcing not one but two new JavaScript Master Classes, Virtual Edition on July 13/14 and July 29/30!

Here's what attendees of our first Virtual Edition JavaScript Master Class said:

“JavaScript Master Class worth every cent. Tons of docs, answers, insights, fun & encouragement. Highly recommended, super friendly.”
“Enjoyed it, learnt a lot and the online format worked very well.”
“Help & clarifications on the side [in the chat] = AWESOME team”
“Completely Impressed”

This time around, we're splitting each class in two half days, for your learning pleasure. The half-days are designed to take up 9am-1pm ET for our first class, and 9am-1pm PT for the second class, ideal if you are in the US, Canada, or South America.

See http://javascriptmasterclass.com/ for details &emdash; but don't book until you've read the bit about your discount!

Save $100 if you book now!

Since we don't have to travel, pay for a class venue, rent a projector, etc., we can pass the savings on to you! The normal ticket price is $429, and the Early Bird price is just $349.
Because you're an awesome script.aculo.us fan, you get $20 off the Early Bird price, saving $100 over the final ticket price.

Here's how to get your ticket for just $329. Go to: http://javascriptmasterclass.com/

Click the bigass pink button to book your ticket. Then enter the fancy code:
SCRIPTY2

But hurry, as the early bird pricing expires soon, on July 4 for the Class on July 13/14, and on July 19, for the Class that's on on July 29/30.

See you at the class!

UIZE JavaScript Framework | Latest News: 2010-06-29 - UIZE Adds Support For Touch

Tue, 29 Jun 2010 07:00:00 -0000

The UIZE JavaScript Framework has added support for the touch interface of Apple's iPad. There's no denying the excitement surrounding Apple's new iPad device, and there is now likely to be a veritable flood of touch interface devices entering the market in response to their success. Apple has already sold over three millions iPads in less than three months. Several other vendors have announced intentions to enter the market with their own competing tablet / slate devices. The touch interface is a trend that is solidly establishing itself. The UIZE JavaScript Framework is addressing this hot new trend by providing the abstractions necessary to make life easier for application developers. To kick off this effort, the Uize.Widget.Drag module has been enhanced to now support touch interface events. Because many other widgets are already written to use the Uize.Widget.Drag widget class, the improvements in this class automatically confer touch support to the widgets that use this class in their implementation. Examples of this are the Uize.Widget.Resizer, Uize.Widget.Resizer.Marquee, Uize.Widget.Bar.Slider, Uize.Widget.ColorCube.Draggable, Uize.Widget.Dialog, Uize.Widget.Drag.Move, and Uize.Widget.ImagePort.Draggable classes. What this all means is that, with the new and improved Uize.Widget.Drag class, selection marquees, sliders, dialogs, image ports, etc. are all now draggable on the Apple iPad - and they still behave as before with mouse / trackpad control. So, if you have an iPad, swing by the uize.com Web site and take a tour of the iPad examples (you'll find them under the examples menu).

UIZE JavaScript Framework | Latest News: 2010-06-28 - UIZE Web Site Revamp

Mon, 28 Jun 2010 07:00:00 -0000

The uize.com Web site has been updated with a bright new look and usability improvements for the Apple iPad. While there are those among us who are attracted to the dark side... where color themes are concerned, there is no denying that the overwhelming preference is for light themed Web sites. Dark text over a light background is the age old convention when it comes to the printed word. People are used to it, comfortable with it, and a light background improves readability in high ambient light conditions where a dark background would have a hard time competing with the ambient light. Add to that the fact that fingerprints on touch devices like the Apple iPad really show up something awful against a dark background, and that one can see one's own reflection too easily against a glossy display when its background is dark, and you have a whole bunch of compelling reasons to have a light background. Hence, the new look for the uize.com Web site. In addition to the color theme changes, many features have been tweaked slightly to improve usability on touch devices like the Apple iPad. Some user interface controls have been made larger, font size for some links has been increased, and some iPad specific issues have been addressed. Hope you like the new look. Bright and fresh.

jQuery UI Blog: jQuery UI 1.9 Milestone 2 – Menu

Thu, 24 Jun 2010 12:39:14 -0000

The second milestone release for jQuery UI 1.9 is out, featuring the new Menu widget, in active development. It also includes updates to the Tooltip widget that we did since our first milestone release. What’s a Milestone Release? A milestone release makes it easier to try out the latest development code of jQuery UI without necessarily having [...]

Official jQuery Blog: The Official jQuery Podcast – Episode 27 – Remy Sharp, Part 2

Fri, 18 Jun 2010 15:47:41 -0000

We again sit down with Remy Sharp in this second of a three part interview. This week we talk with Remy about HTML5 and the future of the spec and how to work with HTML5 today with JavaScript shims. You can subscribe to the show in iTunes or via the raw RSS feed or you [...]

UIZE JavaScript Framework | Latest News: 2010-06-15 - Deprecated Event Management Methods Killed

Tue, 15 Jun 2010 07:00:00 -0000

A number of instance and static event management methods of the Uize base class that were deprecated back in early June of 2009 have finally been killed. In keeping with the policy of one year backwards compatibility transition periods, the deprecated forms of these methods were kept in place for a year and are now ready to expire. Specifically, the addEventHandler, addEventHandlers, fireEvent, removeEventHandler, and removeEventHandlers instance methods have been killed, and the Uize.addEventHandler, Uize.addEventHandlers, Uize.wire, Uize.fireEvent, Uize.removeEventHandler, and Uize.removeEventHandlers static methods have been killed.

Official jQuery Blog: Seattle jQuery Open Space and Hack Attack with John Resig – July 5th

Mon, 14 Jun 2010 19:14:15 -0000

On Monday, July 5th, John Resig will be at the Seattle jQuery/JavaScript community meetup at Amazon’s brand new Van Vorst Meeting Center in South Lake Union for an afternoon of learning, openspace, hacking and, of course, pizza! The fun begins at 1pm with a quick keynote and explanation of open space technology then the group will [...]

Twitter / jquerytools: jquerytools: jQuery Tools 1.2.3 for Plone (open source content management): http://bit.ly/9HlPKN

Sun, 13 Jun 2010 04:52:35 -0000

jquerytools: jQuery Tools 1.2.3 for Plone (open source content management): http://bit.ly/9HlPKN

Twitter / jquerytools: jquerytools: jQuery Tools 1.2.3. 10 bugs fixed. Enjoy! http://bit.ly/dzPXAp

Sat, 12 Jun 2010 11:34:37 -0000

jquerytools: jQuery Tools 1.2.3. 10 bugs fixed. Enjoy! http://bit.ly/dzPXAp

MooTools: Setting Up Elements

Fri, 11 Jun 2010 04:16:36 -0000

Once you know how much easier it is to get elements all around, you should take the time to learn how MooTools has provided a simple access API around the browser quirks for Elements. And on top of it, we’ve extended this API to things that you don’t normally find on Elements. And as cool [...]

jQuery UI Blog: jQuery UI 1.8.2

Mon, 07 Jun 2010 12:29:14 -0000

The second maintenance release for jQuery UI 1.8 is out. This update brings bug fixes for the Selectable and Sortable interactions as well as the Accordion, Autocomplete, Button, Datepicker and Slider widgets. For the full list of changes, see the changelog. You can download it here: Download File Downloads Development Bundle: http://jquery-ui.googlecode.com/files/jquery-ui-1.8.2.zip Themes Package: http://jquery-ui.googlecode.com/files/jquery-ui-themes-1.8.2.zip Svn (contains final files as [...]

UIZE JavaScript Framework | Latest News: 2010-06-07 - MIGRATED METHODS: Uize.Date.format, Uize.Date.toPretty

Mon, 07 Jun 2010 07:00:00 -0000

The Uize.Date.format and Uize.Date.toPretty static methods of the Uize.Date module have been migrated into the new Uize.Date.Formatter module. Because these methods have only been deprecated and have not yet been eliminated from the Uize.Date module, code currently using them should continue to work. However, code that was previously using these methods should be updated to use the new Uize.Date.Formatter.format and Uize.Date.Formatter.toPretty methods of the Uize.Date.Formatter module.

UIZE JavaScript Framework | Latest News: 2010-06-07 - NEW MODULE: Uize.Date.Formatter

Mon, 07 Jun 2010 07:00:00 -0000

The new Uize.Date.Formatter module provides methods for formatting and parsing date strings, supporting a wide variety of different formatting options. The Uize.Date.Formatter.format static method of the new Uize.Date.Formatter module allows date objects to be formatted in many different ways, by specifying date formats using the many available date component tokens, such as {YYYY}, {YY}, {MM}, {monthNo}, {monthName}, {shortMonthName}, {DD}, {dayNo}, {dayNoSuffix}, {dayName}, {shortDayName}, {hh}, {h12}, {hh12}, {mm}, {minutes}, {ss}, {seconds}, and {ampm}. Additionally, date strings can be parsed according to any specified date format.

UIZE JavaScript Framework | Latest News: 2010-06-07 - Improved Date Picker Widget

Mon, 07 Jun 2010 07:00:00 -0000

The date picker widget, implemented in the Uize.Widget.Picker.Date module, has been improved to correctly support date entry in a wide variety of different formats. Previously, dates selected by the user in the date picker dialog could be formatted in the date picker widget's text input field using a configurable date format, as specified in the Uize.Widget.Picker.Date class' displayFormat set-get property. However, the date picker dialog could only parse dates specified in a format that could be recognized by the Uize.Date.resolve method. The new implementation uses the Uize.Date.Formatter.parse method of the new Uize.Date.Formatter module to parse dates in any format specified by the displayFormat property. This change also involves improvements to the Uize.Widget.Calendar, Uize.Widget.Dialog.Picker, Uize.Widget.Dialog.Picker.Date, and Uize.Widget.Picker modules.

MooTools: MooTools Core 1.3 beta 2

Fri, 04 Jun 2010 03:46:19 -0000

Over the past couple of weeks we have got a lot of great responses over the initial beta of MooTools Core 1.3. We have since improved both the code and the documentation in order to release a second beta. Most notably we have removed the dependency on Hash. If you build 1.3 without compatibility you won’t get the [...]

script.aculo.us web 2.0 javascript: Online JavaScript Master Class on June 24, 2010

Wed, 26 May 2010 17:08:00 -0000

Dear script.aculo.us user!

Announcing the JavaScript Master Class: Virtual Edition, June 24!

We've been doing the legwork. We've learned what it takes to put on a kick-ass live, online class. (Don't call it a "webinar" -- or I'll be forced to show you the error of your ways!) The maiden voyage of the JavaScript Master Class: Virtual Edition will take place on June 24 2010, from 10am to 5pm London (GMT) time.

All you need is a reasonably snappy computer, good solid broadband, the latest version of Flash (sorry!), and your fine self. Our class schedule will include snack/pee breaks, and a lunch break. Our voices and screen presentations will come at you live! We'll take questions and solve problems. You will have a few exercises to work on, and we'll help you debug them if the need arises! And, because the online dynamic's a bit different, we'll be sending you the class materials in advance so you can peruse & prepare.

Previous attendees have described our workshops as "worth every penny" and "extremely good" and "I learned a lot and slowly started to feel my brain dribble out of my ears... in a good way." You will learn absolute gobs of stuff about JavaScript: The Language that will help you every day, no matter whether you use Prototype, jQuery, Node.js, or any other library -- or none at all.

See http://javascriptmasterclass.com/ for details &emdash; but don't book until you've read the bit about your discount!

Save 80 Euros if you book now!

Since we don't have to travel, pay for a class venue, rent a projector, etc., we can pass the savings on to you! The normal ticket price is 330€ + VAT. The Early Bird price is just 275€ + VAT.
Because you're an awesome script.aculo.us fan, you get 10% off (that's 30€ off!) the total Early Bird price including VAT.

Here's how to get your ticket for just 300€, incl. VAT. Go to: http://javascriptmasterclass.com/

Click the bigass pink button to book your ticket. Then enter the fancy code:
YAYSCRIPTY2

If you have a non-Austrian VAT ID, or you simply aren't from the EU, you will get the VAT right back from us. We will refund it by PayPal.
Include your VAT ID in the Billing Info field!

Future online classes in your time zone?
We're starting off close to home, time zone-wise, but we'd love to venture further afield.
Let us know at jsrocks@slash7.com.

Twitter / jquerytools: jquerytools: jQuery Tools 1.2.2: http://bit.ly/dzPXAp

Wed, 19 May 2010 07:58:25 -0000

jquerytools: jQuery Tools 1.2.2: http://bit.ly/dzPXAp

MooTools: A Magical Journey into the Base Fx Class

Tue, 18 May 2010 16:46:10 -0000

Fx is not just for animating elements In a recent project I worked on with Thomas Aylott the page did some calculations and displayed the result after the user pulled some sliders around. Rather than just change the text from one number to another, the element would increment the number before the user’s very eyes. [...]

UIZE JavaScript Framework | Latest News: 2010-05-18 - NEW EXAMPLE: Animate Size in JavaScript

Tue, 18 May 2010 07:00:00 -0000

The new Animate Size in JavaScript example shows how to animate the size of an HTML element and how to apply amazingly realistic motion effects like easing, elasticity, bounce, and many more. In the example, the Uize.Fx.fadeStyle method of the Uize.Fx module is animating the size of an object. You can move the mouse around inside the brushed metal square to see a faint preview for a new size for the object, and then click to animate the object to that new size. How the object transitions is decided by the curve(s) used. The curve(s) can be changed by clicking on one of the links in the "PRESETS" tab. Upon choosing a preset, a random new size is chosen and the object is animated to the size using the new curve(s). The object's size can be animated again by clicking a preset link repeatedly, by clicking the "PREVIEW ANIMATION" button repeatedly, or by clicking anywhere on the metal square. The settings for a preset can be edited in the "PARAMS" tab, and the edited settings can be previewed by clicking on the "PREVIEW ANIMATION" button.

UIZE JavaScript Framework | Latest News: 2010-05-16 - NEW METHOD: Uize.escapeRegExpLiteral

Sun, 16 May 2010 07:00:00 -0000

The new Uize.escapeRegExpLiteral static method of the Uize base class provides a convenient way to escape regular expression special characters inside a string that is to be used as a literal match in a regular expression. Using this method, any string can be escaped so that it can be used in creating a regular expression where that string can be matched as a literal match. Strings may sometimes contain special regular expression characters, such as the ( (open parenthesis), ) (close parenthesis), . (period), ? (question mark), and other characters that have special meaning in the context of regular expression strings. If you wanted to use a regular expression to match a string that contained any of these special characters, then the special characters would have to be escaped. The Uize.escapeRegExpLiteral method takes care of this for you.

UIZE JavaScript Framework | Latest News: 2010-05-16 - Deprecated Methods Killed

Sun, 16 May 2010 07:00:00 -0000

A number of methods of the Uize.Color and Uize.Node modules that were deprecated back in the first half of 2009 have finally been killed. Deprecated features of the Uize.Color module that have now been killed include the mix, setColor, setHex, and toHex instance methods, the Uize.Color.blendHex, Uize.Color.hexStrToRgb, Uize.Color.mixColors, Uize.Color.rgbFromStyleStr, Uize.Color.rgbToHexStr, and Uize.Color.rgbToStyleStr static methods, and the Uize.Color.RgbColor object. Additionally, the deprecated Uize.Node.getStyleAttribute static method of the Uize.Node module has been killed. For backwards compatibility and to provide time for transition, these methods were supported for just over a year after being deprecated. Finally removing them helps to clean up the code and reduce code size by a little bit.

Prototype JavaScript framework - blog: Prototype 1.7 RC2

Thu, 13 May 2010 00:19:00 -0000

We’ve just tagged Release Candidate 2 of Prototype 1.7, with the intent of putting out a final 1.7 release very soon.

In addition to the usual bug fixes, RC2 includes a late addition: the Element#purge method, used to dispose of an element (remove its event handlers and storage keys) before removing it from the page.

In addition, Element#update now performs a similar cleanup process on content that will be replaced via innerHTML. Both these additions should help keep memory usage down, especially for apps that create and destroy lots of DOM nodes.

Consult the CHANGELOG for further details.

Download, report bugs, and get help

Download Prototype 1.7 RC2
View the API documentation
Check out the Prototype source code on GitHub
Submit bug reports to Lighthouse
Get prototype help on the mailing list or #prototype IRC channel
Talk to the core team on the prototype-core mailing list

Thanks to the many contributors who made this release possible!

Twitter / jquerytools: jquerytools: jQuery Tools 1.2.1. Now works in Chrome 5 beta, iPhone and iPad. http://bit.ly/aE5X3j

Tue, 11 May 2010 10:59:18 -0000

jquerytools: jQuery Tools 1.2.1. Now works in Chrome 5 beta, iPhone and iPad. http://bit.ly/aE5X3j

jQuery UI Blog: jQuery UI 1.9 Milestone 1 – Tooltip

Mon, 10 May 2010 14:55:49 -0000

The first milestone release for jQuery UI 1.9 is out, featuring the new Tooltip widget, in active development. What’s a Milestone Release? A milestone release makes it easier to try out the latest development code of jQuery UI without necessarily having to check out code from GitHub. With a milestone release you can try out new widgets that [...]

MooTools: Announcing: MooTools in Real Life

Wed, 05 May 2010 17:52:49 -0000

If you’ve been paying attention for the past few years, you’ve probably noticed the growth of MooTools, both as a project and as a thriving community. Unfortunately, it has come to light that many so called “members” of the JavaScript community may, in fact, be automata. To protect ourselves and the MooTools community, we’ve started [...]

jQuery UI Blog: How to submit a fix to jQuery UI – The Easy Way

Wed, 05 May 2010 14:40:48 -0000

Now that jQuery UI is hosted on GitHub, it’s even easier to start contributing fixes to the project. Let’s walk through the easy way, where you don’t need to learn how to really use git. In another post, we’ll cover some best practices for contributing with git. Let’s say you want to submit a patch to the [...]

Twitter / jquerytools: jquerytools: Dropping a Bomb! jQuery Tools 1.2.0 is out. http://flowplayer.org/tools/

Tue, 04 May 2010 14:52:54 -0000

jquerytools: Dropping a Bomb! jQuery Tools 1.2.0 is out. http://flowplayer.org/tools/

Twitter / jquerytools: jquerytools: Flowplayer Setup - a jQuery Tools 1.2.0 showcase: http://flowplayer.org/setup/

Tue, 04 May 2010 14:52:04 -0000

jquerytools: Flowplayer Setup - a jQuery Tools 1.2.0 showcase: http://flowplayer.org/setup/

jQuery UI Blog: jQuery UI 1.8.1

Tue, 04 May 2010 12:29:43 -0000

The first maintenance release for jQuery UI 1.8 is out. This update brings a bunch of fixes to Autocomplete and a few fixes to other plugins. For the full list of changes, see the changelog. You can download it here: Download File Downloads Development Bundle: http://jquery-ui.googlecode.com/files/jquery-ui-1.8.1.zip Themes Package: http://jquery-ui.googlecode.com/files/jquery-ui-themes-1.8.1.zip Svn (contains final files as they are in the zip, with [...]

jQuery UI Blog: jQuery UI 1.7.3

Tue, 04 May 2010 12:15:32 -0000

The third maintenance release for jQuery UI 1.7 is out. This is an update to the legacy 1.7 to make it compatible with the latest jQuery 1.4, in case you aren’t yet able to upgrade to the latest jQuery UI 1.8. You can download it here: Download File Downloads Development Bundle: http://jquery-ui.googlecode.com/files/jquery-ui-1.7.3.zip Themes Package: http://jquery-ui.googlecode.com/files/jquery-ui-themes-1.7.3.zip Svn Tag: http://jquery-ui.googlecode.com/svn/tags/1.7.3/ Themes: http://jquery-ui.googlecode.com/svn/tags/1.7.3/themes/ Google Ajax [...]

MooTools: More than Meets the Eye: Form Validator

Fri, 30 Apr 2010 20:09:03 -0000

Continuing with my “More than Meets the Eye” series, today I want to talk to you about the MooTools More Form.Validator. There was a comment left on my last post in this series (about Form.Request) specifically requesting that I cover this relatively complex plugin that’s useful for telling users about the validity of data they [...]

UIZE JavaScript Framework | Latest News: 2010-04-30 - NEW EXAMPLE: Animate Position in JavaScript

Fri, 30 Apr 2010 07:00:00 -0000

The new Animate Position in JavaScript example shows how to animate the position of an HTML element and how to apply amazingly realistic motion effects like easing, elasticity, bounce, and many more. In the example, the Uize.Fx.fadeStyle method of the Uize.Fx module is animating the position of a silver sphere. You can click anywhere on a brushed metal square and the sphere will move to that position. How the sphere moves is decided by the curve(s) used by the Uize.Fx.fadeStyle method. You can change the curve(s) by selecting one of the many presets from the "PRESETS" tab. Upon choosing a preset, a random target position is chosen for the sphere, and the sphere is then animated to that position using the newly selected curve(s). The animation can be repeated by clicking a preset link repeatedly, or by clicking the "PREVIEW ANIMATION" button repeatedly, or by clicking anywhere on the metal square. The settings for a preset can be edited in the "PARAMS" tab, and the edited settings can be previewed by clicking on the "PREVIEW ANIMATION" button.

Twitter / jquerytools: jquerytools: Throwing out jQuery Tools 1.2.0 preview: http://dev.flowplayer.org/tools/

Wed, 28 Apr 2010 17:15:58 -0000

jquerytools: Throwing out jQuery Tools 1.2.0 preview: http://dev.flowplayer.org/tools/

MooTools: MooTools 1.3 ßeta 1

Tue, 27 Apr 2010 23:25:06 -0000

MooTools 1.3 beta 1 launches today. Lots of bug fixes and improvements, and all that jazz. Before presenting you with a random rundown of features, let me be clear about something: MooTools 1.3 is (or will be) 100% compatible with every public documented API of MooTools 1.2. So chill already. Anyways, here’s what’s new: Globals MooTools 1.3 moves [...]

MooTools: Object Oriented jQuery with MooTools @ jQuery Conference

Tue, 27 Apr 2010 13:12:36 -0000

Hey there MooToolers. I just returned from speaking at jQuery Conference 2010 in San Francisco on “Object Oriented jQuery with MooTools” and thought I’d share some notes on the experience. My Talk If you ask me how I did I’d say I missed a few connecting ideas but got the concept out there and got some [...]

UIZE JavaScript Framework | Latest News: 2010-04-25 - IMPROVED METHOD: Uize.substituteInto

Sun, 25 Apr 2010 07:00:00 -0000

The Uize.substituteInto static method, implemented in the Uize base class has been improved to be more robust. Because of the way it was previously implemented, the Uize.substituteInto method would perform further substitutions into values previously substituted into the source string. This could result in some odd and unexpected behaviors in the unlikely event that the value for one substitution contained the token name for another substitution. In addition to this improvement, the Uize.substituteInto method is also now fully unit tested, and its documentation has been updated to be more comprehensive and accurate.

UIZE JavaScript Framework | Latest News: 2010-04-18 - NEW EXAMPLE: Animated Buttons with Box Shadow

Sun, 18 Apr 2010 07:00:00 -0000

The new Animated Buttons with Box Shadow example demonstrates the UIZE JavaScript Framework's ability to animate values for the box-shadow CSS3 style property. In this example, an instance of the Uize.Widget.HoverFader widget class is being used to add a JavaScript animation effect to a set of navigation buttons. With help from the Uize.Fx.xShadows extension module, the instance manages fading of values for the box-shadow, margin-left, margin-top, color, and border-color CSS style properties for the buttons. For browsers that support the CSS3 box-shadow style property, the buttons appear to "leap" out of the page when they are moused over. To add more realism, the Uize.Curve.Rubber module is used to add a bounce quality to the fade back from a button's hover state to its resting state, which makes the buttons bounce as they sink back in and "hit the page surface".

UIZE JavaScript Framework | Latest News: 2010-04-18 - DEPRECATED MODULE: Uize.Fx.xTextShadow

Sun, 18 Apr 2010 07:00:00 -0000

he Uize.Fx.xTextShadow extension module has been deprecated in favor of the new and more powerful Uize.Fx.xShadows module. As its name implies, the Uize.Fx.xTextShadow module provided support specifically for fading / animating values of the text-shadow CSS3 style property. The new Uize.Fx.xShadows module provides support for animating both the text-shadow and box-shadow style properties. Because the Uize.Fx.xTextShadow module has only been deprecated and has not yet been eliminated, code currently using it should continue to work. However, relying on the backwards compatibility provision will not be as efficient as directly using the new Uize.Fx.xShadows module. Therefore, code that was previously using the Uize.Fx.xTextShadow module should be updated to use the new Uize.Fx.xShadows module.

UIZE JavaScript Framework | Latest News: 2010-04-18 - NEW MODULE: Uize.Fx.xShadows

Sun, 18 Apr 2010 07:00:00 -0000

The new Uize.Fx.xShadows extension module implements support for fading / animating the values of both the text-shadow and box-shadow CSS3 style properties. This new module takes over from the now deprecated Uize.Fx.xTextShadow module. When the Uize.Fx.xShadows module is loaded, the Uize.Fx.fadeStyle method can be used to animate text shadow and box shadow along with all other supported CSS style properties.

UIZE JavaScript Framework | Latest News: 2010-04-15 - IMPROVED MODULE: Uize.Template

Thu, 15 Apr 2010 07:00:00 -0000

The Uize.Template module has been improved in a number of ways: 1) The new Uize.Template.encodings static property, which is an object, allows custom encodings to be registered by assigning encoding profile objects as properties on it. 2) The new Uize.Template.defineStandardEncoding static method provides a convenient way to define new standard encodings. 3) Three new encodings have been added: iso8601, tagAttributes, and tagAttributeValue. 4) When building up the canonical list of modules required by a template being compiled, the @required directive now makes sure to ignore any duplicate instances of required modules. 5) The Uize.Template.encode and Uize.Template.decode static methods have been improved to now both support encoding chains, in the same format as can be used in assignment expressions in template code (eg. 'json -> urlPiece'). 6) The reference documentation for the Uize.Template module has been improved in a number of ways. 7) With the introduction of the new Uize.Template.encodings static property, the Uize.Template.encoders and Uize.Template.decoders static properties have been deprecated. 8) With the introduction of the new Uize.Template.encodings static property, the way that encodings imply dependencies upon code execution has changed.

UIZE JavaScript Framework | Latest News: 2010-04-12 - IMPROVED MODULE: Uize.Date

Mon, 12 Apr 2010 07:00:00 -0000

The Uize.Date module has been improved, with fixes for a number of issues, improvements to a number of static methods, and the addition of a thorough set of unit tests in the new Uize.Test.Uize.Date unit tests module. FIXES: 1) The Uize.Date.inRange static method has been fixed to correctly support date range objects where the value of the minValue property is undefined, null, or not specified. 2) A rounding bug in the Uize.Date.isRecent static method, that would cause this method to produce the incorrect result under certain conditions, has been fixed. 3) A bug with the Uize.Date.toIso8601 static method, where the month would always be off by one, has been fixed. IMPROVEMENTS: 1) The Uize.Date.format static method has been improved with the addition of support for invalid dates for all substitution tokens (eg. Uize.Date.format (new Date (NaN),'{YYYY}-{MM}-{DD}') now produces the result '????-??-??'). 2) The Uize.Date.resolve static method has been improved with the addition of support for dates specified as a milliseconds integer number. UNIT TESTS: The Uize.Date module is now thoroughly unit tested by the newly created Uize.Test.Uize.Date unit tests module.

Prototype JavaScript framework - blog: Prototype 1.7 RC1: Sizzle, layout/dimensions API, event delegation, and more

Mon, 05 Apr 2010 16:42:00 -0000

We've just tagged the first release candidate of Prototype 1.7: a major new version with some major new features.

Sizzle as the selector engine (or mix in your own)

With Prototype 1.7, we've finally realized our long-held goal of moving to Sizzle, the middleware selector engine used by jQuery and others. I wrote our previous selector engine, used since 1.5.1, but nevertheless I'm excited to switch to a more robust engine that's shared between frameworks.

So Sizzle is the new default. But there's more to it than that. In moving to Sizzle, we've modularized the selector engine entirely. If you want to use Diego Perini's NWMatcher library in place of Sizzle, you can. Just check out the source code and build like so:

rake dist SELECTOR_ENGINE=nwmatcher

If you're a sentimentalist, you can use the legacy Prototype selector engine by specifying SELECTOR_ENGINE=legacy_selector. Or add your own selector engine by creating a subdirectory in vendor/ and following some simple conventions.

Element#on

Element#on is a new way to access the Prototype event API. It provides first-class support for event delegation and simplifies event handler removal.

In its simplest form, Element#on works just like Element#observe:

$("messages").on("click", function(event) {
  // ...
});

An optional second argument lets you specify a CSS selector for event delegation. This encapsulates the pattern of using Event#findElement to retrieve the first ancestor element matching a specific selector. So this Prototype 1.6 code...

$("messages").observe("click", function(event) {
  var element = event.findElement("a.comment_link");
  if (element) {
    // ...
  }
});

...can be written more concisely with Element#on as:

$("messages").on("click", "a.comment_link", function(event, element) {
  // ...
});

Element#on differs from Element#observe in one other important way: its return value is an object with a #stop method. Calling this method will remove the event handler. (Technically, this is an instance of a new class called Event.Handler.) With this pattern, there's no need to retain a reference to the handler function just so you can pass it to Element#stopObserving later.

For example, in Prototype 1.6, where you'd need to write something like...

start: function() {
  this.clickHandler = function(event) {
    // ...
  };

  $("messages").observe("click", this.clickHandler);
},

stop: function() {
  $("messages").stopObserving("click", this.clickHandler);
}

...you can now write:

start: function() {
  this.clickHandler = $("messages").on("click", function(event) {
    // ...
  });
},

stop: function() {
  this.clickHandler.stop();
}

Also note that the Event.Handler class has a corresponding #start method that lets you re-attach an observer you've removed with #stop.

So, to review, Element#on is both a new approach to event observation and an implementation of event delegation. Feel free to eschew Element#observe and use Element#on exclusively; or use Element#on just for event delegation; or keep using Element#observe the way you always have.

Element.Layout: Your digital tape measure

The second major feature in 1.7 is Element.Layout, a class for pixel-perfect measurement of element dimensions and offsets.

Now you don't have to decide between properties like offsetWidth (which return numbers, but not the numbers you want) or retrieving computed styles (which have their own set of quirks and require a call to parseInt).

The simple case

If you want a one-off measurement of an element, use the new Element#measure:

$('troz').measure('width'); //-> 150
$('troz').measure('border-top'); //-> 5

// Offsets, too:
$('troz').measure('top'); //-> 226

The argument passed to measure is one of a handful of intuitive names, most of which are derived from their CSS equivalents. So width means the width of the content box, just like in CSS — but we throw in extra properties (e.g., padding-box-width, margin-box-height) for some common measurements. This approach gives you far more granularity than common DHTML properties like offsetWidth and clientHeight.

These measurements are guaranteed to be in pixels. Even in IE. (In fact, Prototype works around a handful of IE quirks that would ordinarily result in inaccurate measurments.) It can even measure elements that are hidden, as long as their parents are visible. (Like when you want to animate an element from a hidden state and need to know how tall it will be.)

The complex case

If you need to measure several things at once, though, Element#measure is not the most efficient way to do it. Often an element will need a bit of manipulation before it reports its dimensions accurately, which means measurements can be costly.

The Element.Layout class tries to minimize that cost. It's a read-only subclass of Hash that remembers values in order to avoid re-computing.

First, use Element#getLayout to obtain an instance of Element.Layout:

var layout = $('troz').getLayout();

Now use Element.Layout#get to retrieve values, using the same property names you used for Element#measure:

layout.get('width');  //-> 150
layout.get('height'); //-> 500

layout.get('padding-left');  //-> 10
layout.get('margin-left');   //-> 25
layout.get('border-top');    //-> 5
layout.get('border-bottom'); //-> 5

layout.get('padding-box-width'); //-> 170
layout.get('border-box-height'); //-> 510

layout.get('width');  //-> 150

Here's where the remembered values (or memoization, if you prefer) come in. When I ask for width, Prototype measures the element – which, as we discussed, is a costly operation — and returns a value. A few lines later, I ask for width again, and I get the same value. But this time it didn't do any measuring. It remembered the value from last time.

There's more. When I ask for border-box-height, Prototype knows that's just height plus border-top plus border-bottom. All three of those properties are already memoized, since I asked for them earlier, so it skips the measurement phase and just gives me the sum.

How does it know when an element's dimensions change? It doesn't. Don't hang onto an instance of Element.Layout for too long; it's meant for short-term efficiency, not long-term caching. You can grab a new instance by calling Element#getLayout again.

Believe it or not, this is the short version. Read the documentation to learn more.

JSON fixes, ES5 compliance

The JSON interface slated for ECMAScript 5 is already being implemented in major browsers. It uses many of the same method names as Prototype's existing JSON implementation, but with different behavior, so we rewrote ours to be ES5-compliant and to fall back to the native JSON support where possible. A few other methods, like Object.keys, received similar treatment.

And, of course, bug fixes

Consult the CHANGELOG for further details.

Download, report bugs, and get help

Download Prototype 1.7 RC1
View the API documentation
Check out the Prototype source code on GitHub
Submit bug reports to Lighthouse
Get prototype help on the mailing list or #prototype IRC channel
Talk to the core team on the prototype-core mailing list

As always: thanks to the many contributors who made this release possible!

MooTools: Dojo and MooTools

Thu, 01 Apr 2010 16:02:54 -0000

Over the past several months we here at MooTools have been contemplating how much of what we do is duplicated effort. When we started this whole project years ago it was because we wanted to do things our own way, but as MooTools and JavaScript in general have progressed, we find ourselves facing the tedium [...]

UIZE JavaScript Framework | Latest News: 2010-03-24 - New Web Site Using UIZE: wardtog.com

Wed, 24 Mar 2010 07:00:00 -0000

The recently released wardtog.com Web site is an excellent showcase of the UIZE JavaScript Framework. Wardtog.com really is the long tail of location based products, offering products that represent hundreds upon hundreds of cities across the entire globe. Let's say, hypothetically, that you were born and raised in the city of Cape Town, South Africa. Then, let's say further that you were at some point transplanted to San Francisco, California. Now, as an expatriate of Cape Town, South Africa, you might be moved to buy a shirt declaring your undying love for your city of birth. At Wardtog.com, this hypothetical expatriate can do just that by going to the Cape Town Designs page. With wardtog.com, transplants from all around the globe can step up and represent. Each city has numerous products with numerous design themes. The wardtog.com Web site is an impressive showcase of what can be accomplished using the UIZE JavaScript Framework. The designs for the many cities represented on the site are generated dynamically in Adobe Photoshop, with some help from the host-neutral modules of UIZE. Then, build scripts running in Windows Script Host are responsible for building the thousands of HTML pages, utilizing UIZE and its JavaScript templates functionality, thereby reducing server load by not requiring large amounts of dynamic processing and database access when pages of the site are viewed. Then, the entire site, consisting of thousands of static pages, is packaged and deployed to the server, once again utilizing scripts running in Windows Script Host and employing the host-neutral features of UIZE. Finally, the UIZE JavaScript Framework is used on the client-side to provide zoom previews in product grids, and for other client-side interactivity. All in all, wardtog.com really flexes the muscles of the UIZE JavaScript Framework and puts its robust features to good use.

MooTools: Get friendly with the Natives

Wed, 24 Mar 2010 02:48:56 -0000

Have you extended a Native lately? It’s an incredibly helpful thing. Often people write ugly functions that take a string or whatever as an argument and return some manipulation of the string. Extending natives is a great way to do the same thing, but it is much prettier (aka: explicit, readable, easier-to-debug.) The Difference: I’ve seen stuff [...]

MooTools: A Better Way to use Elements

Fri, 19 Mar 2010 22:41:41 -0000

Javascript development in the browser is all about the Elements. Manipulating the DOM happens every few lines of code. It’s important enough that some libraries provide little more than DOM enhancements. Not to worry though, MooTools provides greatly in this area as well. $ and $$ Most of you probably know the two document methods getElementById and [...]

UIZE JavaScript Framework | Latest News: 2010-03-18 - NEW EXPLAINER: Creating A New Uize Module

Thu, 18 Mar 2010 07:00:00 -0000

The new Creating A New Uize Module explainer provides guidelines and advice for the development of new UIZE modules, to be followed by developers of the UIZE JavaScript Framework. Among other things, this document discusses: 1) choosing an appropriate namespace and name for your new module, 2) requirements for the module info, scruncher settings, and module meta data comment blocks of your new module, 3) guidelines on implementing the functionality for your new module, 4) implementing a companion unit test module for your new module, 5) documenting your new module, and 6) creating one or more examples for your new module.

MooTools: MooTools Roundup February 2010

Fri, 12 Mar 2010 02:11:30 -0000

The foundation of every great open source project is its community. The MooTools Team creates the base framework code but it’s all of you that take the framework and build outstanding plugins. These are just some of the new developments floating around the MooTools community. 12 Steps to MooTools Mastery Jacob Thornton’s NetTuts article, 12 Steps to [...]

UIZE JavaScript Framework | Latest News: 2010-03-11 - IMPROVED MODULE: Uize

Thu, 11 Mar 2010 08:00:00 -0000

The built-in module loader in the Uize base class has been improved to make updating the version of the UIZE JavaScript Framework used on a particular Web site easier. It has been updated so that it now retains the query parameters from the URL that is used when sourcing in the Uize. These query parameters make their way into the default value that is set for the Uize.moduleUrlTemplate static property when loading in the Uize base class in a Web page. As such, they are then used when forming the URLs for requesting subsequent modules that need to be dynamically loaded in. This means that if you're adding a build number query parameter onto the URL when loading in the Uize base class in a script tag, then that same build number will appear in URLs for dynamically loaded modules. By using a build version query param when loading the Uize base class, one can ensure that the browser's cache will be defeated for all dynamically loaded modules, which guarantees that the browser won't continue using an old cached copy for one module while potentially using a new fresh copy of some other module (which could produce errors if the different modules from different versions of the framework are not compatible with one another). The Uize.getPathToLibrary static method has been improved to now support an optional moduleTokenSTR parameter. When the optional moduleTokenSTR parameter is specified, then the value returned by this method will be the value of the src property for the script tag that sources in the module specified by the moduleFilenameSTR parameter, but with the module filename replaced by the substitution token specified by the moduleTokenSTR parameter.

UIZE JavaScript Framework | Latest News: 2010-03-08 - NEW EXAMPLE: Get Tree from Page

Mon, 08 Mar 2010 08:00:00 -0000

The new Get Tree from Page example demonstrates how the Uize.Node.Tree.getTreeFromPage static method of the Uize.Node.Tree module can be used to build a tree data object respresenting the structure of the document, by analyzing the occurrence of different CSS classes for section headings at different depths of the document (in this case, the CSS classes level1Header, level2Header, and level3Header). A tree data object like this can be supplied to a tree menu widget, or can otherwise be used to build UI for navigating to different sections of the document (a contents tree, for example).

MooTools: More Than Meets the Eye: Form.Request

Thu, 04 Mar 2010 22:06:11 -0000

MooTools More features a diverse, powerful collection of Classes (60 plugins!!) and some are my favorite tools that I use over and over again. I thought I’d take some time to dig into some of the plugins in MooTools More that I think are interesting and really useful that maybe you haven’t had time to [...]

Twitter / jquerytools: jquerytools: Windows Phone 7 Series using jQuery Tools: http://www.windowsphone7series.com

Tue, 16 Feb 2010 20:51:23 -0000

jquerytools: Windows Phone 7 Series using jQuery Tools: http://www.windowsphone7series.com

MooTools: MooTools at FOSDEM: Video

Mon, 15 Feb 2010 15:59:28 -0000

Hello everyone, I’m really excited and pleased to announce that my presentation “MooTools as a General Purpose Application Framework” which I delivered at the FOSDEM is now available on YouTube. If you are not able to watch the HD-Version you can download the slides here. Thanks again to the FOSDEM team for inviting me and for giving us [...]

MooTools: MooTools Roundup January 2010

Mon, 15 Feb 2010 15:56:14 -0000

The foundation of every great open source project is its community. The MooTools Team creates the base framework code but it’s all of you that take the framework and build outstanding plugins. Here are some great plugins and tutorials that have been released recently. MooTools Driver for Rails 3 Helpers Rails 3 has been recently been released [...]

MooTools: MooTools More 1.2.4.3, 1.2.4.4

Wed, 10 Feb 2010 02:10:29 -0000

UPDATE: 1.2.4.4 is also released; there was a new bug in Tips introduced in 1.2.4.3 that was immediately patched. This is mostly a bug fix release. Nearly 50 bug fixes (see the milestone for 1.2.4.3 in Lighthouse). Keyboard: Added some support for just pressing ‘shift’, ‘control’, or ‘alt’ Added a bunch of keycodes for Mac compatibility Keyboard.Extras: Support for “shortcuts” which are [...]

Twitter / jquerytools: jquerytools: Free theme using jQuery Tools by @zbra: http://zbra.co.za

Fri, 08 Jan 2010 10:42:46 -0000

jquerytools: Free theme using jQuery Tools by @zbra: http://zbra.co.za

Twitter / jquerytools: jquerytools: Working on jQuery Tools 1.2.0. Will turn your site into pure amazing. Need help. Please, join the team. Send me a message.

Mon, 07 Dec 2009 08:47:46 -0000

jquerytools: Working on jQuery Tools 1.2.0. Will turn your site into pure amazing. Need help. Please, join the team. Send me a message.

Twitter / jquerytools: jquerytools: jQuery Tools article on Tripwire Magazine: http://bit.ly/7DxHos

Fri, 04 Dec 2009 12:40:49 -0000

jquerytools: jQuery Tools article on Tripwire Magazine: http://bit.ly/7DxHos

Twitter / jquerytools: jquerytools: Server-side Javascript: http://nodejs.org/ Finally. Simply Amazing.

Fri, 20 Nov 2009 20:13:49 -0000

jquerytools: Server-side Javascript: http://nodejs.org/ Finally. Simply Amazing.

Twitter / jquerytools: jquerytools: I was hoping for something like this to appear http://persvr.org Unfortunately does not look mature yet.

Mon, 16 Nov 2009 17:35:49 -0000

jquerytools: I was hoping for something like this to appear http://persvr.org Unfortunately does not look mature yet.

Twitter / jquerytools: jquerytools: Meeting businessmen in New York. Relax: jQuery Tools will always be Open Source. Spotted seagram building yesterday: http://bit.ly/3LDFpx

Mon, 26 Oct 2009 10:50:24 -0000

jquerytools: Meeting businessmen in New York. Relax: jQuery Tools will always be Open Source. Spotted seagram building yesterday: http://bit.ly/3LDFpx

script.aculo.us web 2.0 javascript: scriptaculous V1.8.3: Prototype 1.6.1, service release/bug fixes

Thu, 08 Oct 2009 10:32:00 -0000

This is a bugfix release that bumps script.aculo.us to version 1.8.3.

Most importantly, the included Prototype 1.6.1 provides performance and compatibility improvements with the latest browsers.

Other fixes:

Effect.toggle to return effect (to be able to do Effect.toggle(element, 'appear', {sync: true});) [RStankov]
Use element.identify() for fetching element.id in Sortable.create [RStankov]
Fix deprecated usage of Position.cumulativeOffset. [#182 state:resolved] [James Wheare]
Make loader work for application/xhtml+xml served documents. Closes #95. [Pavel Sedek]
Check for Windows Media plugin and RealPlayer plugin in Firefox on Windows to allow sound playback. Closes #36, #86. [Alexander Gavazov et al.]
Remove dead code in effects.js. Closes #125. [Confusioner]

Download at http://script.aculo.us/, or grab/fork the source at http://github.com/madrobby/scriptaculous.

Twitter / jquerytools: jquerytools: jQuery Tools 1.1.2. is out: Website redesign!, (even) richer events + 18 small issues: http://bit.ly/7jPDs

Wed, 07 Oct 2009 10:06:53 -0000

jquerytools: jQuery Tools 1.1.2. is out: Website redesign!, (even) richer events + 18 small issues: http://bit.ly/7jPDs

Twitter / jquerytools: jquerytools: @rtomayko read several articles from your site http://tomayko.com/ Always nice to spot developers with sense.

Sat, 03 Oct 2009 19:41:03 -0000

jquerytools: @rtomayko read several articles from your site http://tomayko.com/ Always nice to spot developers with sense.

Twitter / jquerytools: jquerytools: Wondering what they say about jQuery Tools in Saudi Arabia: http://bit.ly/3K7N5L

Sat, 03 Oct 2009 15:31:39 -0000

jquerytools: Wondering what they say about jQuery Tools in Saudi Arabia: http://bit.ly/3K7N5L

Twitter / jquerytools: jquerytools: jQuery Tools article at noupe.com : http://bit.ly/T6zrv

Tue, 29 Sep 2009 04:03:18 -0000

jquerytools: jQuery Tools article at noupe.com : http://bit.ly/T6zrv

script.aculo.us web 2.0 javascript: script.aculo.us 2.0 alpha preview

Fri, 25 Sep 2009 16:30:00 -0000

scripty2 is now out in a preview alpha release, with cool demos and some of the nicest documentation any open source project has (we do know that's a bold statement!).

In this release, the focus has been on the effects engine, with the UI parts still pending a rewrite (there will be a lot of really cool stuff coming for the UI part, but more about that later).

As a bonus, the minified and gzipped version of scripty2 is a mere 5k in size. That’s a lot of animation features in a very, very small package.

Hop over to http://scripty2.com to see the demos and documentation, and learn more about the background story on Thomas' blog post.

Twitter / jquerytools: jquerytools: jQuery Tools 1.1.1 is out. Smaller footprint, W3C event model & 15 bugfixes. Hug me! http://bit.ly/VhElc

Fri, 18 Sep 2009 19:56:02 -0000

jquerytools: jQuery Tools 1.1.1 is out. Smaller footprint, W3C event model & 15 bugfixes. Hug me! http://bit.ly/VhElc

Prototype JavaScript framework - blog: Documentation: not just new, but also improved

Thu, 10 Sep 2009 05:20:00 -0000

When we officially released 1.6.1 last week, we also published new documentation, the first official docs generated with PDoc.

Tobie, ear to the ground, brought to my attention what many of you were saying (on the blog and on Twitter): the new docs were harder to navigate and, therefore, harder to browse. Though I had eventual plans to re-do the navigation, the instant feedback showed it was a more critical issue than I’d guessed. So I spent the last week making some changes to the template we use to generate the docs.

You can see the results at api.prototypejs.org. The biggest change is obvious: a fixed, always-visible sidebar that makes it easier to move from section to section. Typing in the search box replaces the hierarchical navigation with a list of matching results. Clearing the search box (use the ESC key as a shortcut) switches back to the ordinary navigation. The sidebar will preserve state from page to page — it’ll remember your search term and the scrollbar position.

The docs aren’t perfect yet, but they’re good enough to use. I’ve tested them on Firefox 3.5, Safari 4.0, and IE 7–8. If there are glitches in these browsers or others, please open issues on the GitHub project. (If you, as a JavaScript developer, are still using IE 6; I’d like to take you out for a beer and ask you why.)

We intend for this to be default template included with PDoc, albeit without the Prototype branding. And now that we’ve accomplished the most pressing goal — getting PDoc to generate comprehensive and canonical docs for Prototype — we can focus on the big ideas we’ve got for the next version of our inline documentation tool.

Prototype JavaScript framework - blog: Core Team update: Andrew & Tobie take the reins

Tue, 01 Sep 2009 14:20:00 -0000

In addition to releasing Prototype 1.6.1, I’m pleased to announce that Andrew Dupont and Tobie Langel now officially head up the Prototype Core Team. They’ll be in charge of maintaining Prototype, deciding what makes the cut for new releases, and handling day-to-day operations.

This change in responsibility will let me focus on some infrastructural projects we need for the next-generation version of Prototype. It’ll also help us fix bugs faster and release new versions more frequently. And I’ll remain on the Core Team, contributing code and offering input on API design.

Andrew and Tobie have proved themselves to be worthy keepers of the code, so I’m certain Prototype is in good hands. Congratulations, guys, and thanks for all your hard work!

Prototype JavaScript framework - blog: Prototype 1.6.1 released

Tue, 01 Sep 2009 14:15:00 -0000

We’re pleased to announce the release of Prototype 1.6.1 today. This version features improved performance, an element metadata storage system, new mouse events, and compatibility with the latest browsers. It’s also the first release of Prototype built with Sprockets, our JavaScript packaging tool, and PDoc, our inline documentation tool.

Highlights

Full compatibility with new browsers. This version of Prototype fully supports versions 1.0 and higher of Google Chrome, and Internet Explorer 8 in both compatibility mode and super-standards mode.
Element metadata storage. Easily associate JavaScript key/value pairs with a DOM element. See the blog post that started it off.
New mouse events. Internet Explorer’s proprietary “mouseenter” and “mouseleave” events are now available in all browsers.
Improved performance and housekeeping. The frequently used Function#bind, String#escapeHTML, and Element#down methods are faster, and Prototype is better at cleaning up after itself.
Built with Sprockets. You can now include the Prototype source code repository in your application and use Sprockets for dependency management and distribution.
Inline documentation with PDoc. Our API documentation is now stored in the source code with PDoc so it’s easy to send patches or view documentation for a specific version.

See the RC2 blog post, RC3 blog post, and CHANGELOG for more details.

Download, report bugs, and get help

Download Prototype 1.6.1
View the API documentation
Check out the Prototype source code on GitHub
Submit bug reports to Lighthouse
Get Prototype help on the mailing list or #prototype IRC channel
Interact with the Core Team on the protoype-core mailing list

We hope you enjoy the new version!

UPDATE

We’re aware of the usability issues with the current PDoc-generated API documentation. We’re working hard to fix those.

In the meantime, we’ve reverted our changes and you can again access the old Prototype documentation. For those of you courageous enough, the new documentation is still available.

Sorry for the inconvenience.

Prototype JavaScript framework - blog: Prototype 1.6.1 RC3: Chrome support and PDoc

Tue, 16 Jun 2009 22:21:00 -0000

Today we’re announcing Release Candidate 3 of Prototype 1.6.1. Among the highlights of this release are official Chrome support, improved IE8 compatibility, faster generation of API documentation with PDoc, and lots of bug fixes.

Chrome support

Since Google Chrome is a close sibling of Safari, Prototype has had excellent Chrome compatibility ever since the browser was first released. Now we’re making it official: Prototype supports Chrome 1.0 and greater.

If you have Chrome installed on your system (Windows only for now, even though early alphas exist for Mac), invoking rake test will run the unit tests in all locally-installed browsers, including Chrome. To run the unit tests in Chrome alone, try rake test BROWSERS=chrome.

Generate your own docs with PDoc

It’s been a long, strange trip for PDoc, the inline-doc tool that will soon be for Prototype and script.aculo.us what RDoc is for Rails. It started as Tobie’s brainchild over a year ago, but key contributions from James Coglan and Samuel Lebeau have helped to carry it across the finish line.

PDoc was a part of RC2, but has since been updated to make doc generation much, much faster. On my machine, a process that used to take 20 minutes now takes only 60 seconds. Furthermore, we’ve solved a couple of minor issues that made it hard to build the docs on Windows.

Ever since Prototype 1.5, we’ve kept our documentation in Mephisto, the same engine that powers the rest of the site (and this blog). It’s served us well, but it meant that updating the docs became a chore that could only be started once we’d released a particular version. PDoc will make it far easier to maintain our documentation — and far easier to keep archival copies of the docs for older versions of Prototype.

Upon final release of 1.6.1, we’ll put the generated docs on this site, just like Rails hosts its most recent stable documentation. Until then, you can generate your own local docs by checking out the full source and running rake doc from the command line.

Other improvements

There have also been a number of bugs fixed since RC2 — including a heinous bug relating to Event#observe — and a number of key optimizations. We’ve further improved IE8 compatibility, solving some edge-case issues that popped up since RC2. Credit goes to Juriy (kangax), our newest team member, for working tirelessly these last few months to make 1.6.1 faster and less reliant on browser sniffs.

Download, report bugs, and get help

Download Prototype 1.6.1 RC3
Submit bug reports to Lighthouse
Get Prototype help on the mailing list or #prototype IRC channel
Interact with the Core Team on the protoype-core mailing list

Thanks to the many contributors who made this release possible!

Prototype JavaScript framework - blog: Prototype 1.6.1 RC2: IE8 compatibility, Element storage, and bug fixes

Fri, 27 Mar 2009 23:33:00 -0000

Today we tagged the first public release candidate of Prototype 1.6.1. (What happened to RC1? Long story.) While there are more minor fixes we’d like to get into this release, we decided an interim release was necessary because of the final release of Internet Explorer 8 last week.

This is the first public release of Prototype that is fully compatible — and fully optimized for — Internet Explorer 8’s “super-standards” mode. In particular, Prototype now takes advantage of IE8’s support of the Selectors API and its ability to extend the prototypes of DOM elements.

What’s new?

Full compatibility with Internet Explorer 8. Juriy has spearheaded the effort to replace most of our IE “sniffs” into outright capability checks — making it far easier to support IE8 in both “super-standards” mode and compatibility mode.
Element storage, a feature announced previously. Safely associate complex metadata with individual elements.
mouseenter and mouseleave events — simulating the IE-proprietary events that tend to be far more useful than mouseover and mouseout.
An Element#clone method for cloning DOM nodes in a way that lets you perform “cleanup” on the new copies.

What’s been improved?

Better housekeeping on event handlers in order to prevent memory leaks.
Better performance in Function#bind, Element#down, and a number of other often-used methods.
A number of bug fixes.

Consult the CHANGELOG for more details.

In addition to the code itself, the 1.6.1 release features Prototype’s embrace of two other excellent projects we’ve been working on: Sprockets (JavaScript concatenation) and PDoc (inline documentation). Sprockets is now used to “build” Prototype into a single file for distribution. PDoc will be the way we document the framework from now on. The official API docs aren’t quite ready yet, but they’ll be ready for the final release of 1.6.1.

Download, Report Bugs, and Get Help

Download Prototype 1.6.1_rc2
Submit bug reports to Lighthouse
Get Prototype help on the rails-spinoffs mailing list or #prototype IRC channel
Interact with the Core Team on the prototype-core mailing list

Thanks to the many contributors who made this release possible!

Prototype JavaScript framework - blog: Sprockets: Beautiful and angular

Fri, 20 Feb 2009 01:59:00 -0000

Over at SvN, Sam announced the 1.0 release of Sprockets, the new dependency management and concatenation tool that makes it easy to modularize your JavaScript. Sprockets is Prototype’s new build system, but it’s also been extracted into a Ruby library so you can use it anywhere you write JavaScript.

There are many great ways to use Sprockets in your own projects. You can use it the way Prototype does — split up your JavaScript into small, maintainable files, then create “meta-files” that include the smaller files in a logical order. Prototype had previously been doing this with plain ERB; now we integrate Sprockets as a Git submodule and use it to build our distributable file.

Sprockets can also be used to write JavaScript “plugins”: bundles of files that can easily be integrated into existing code. With Sprockets, you can formally declare that foo.js depends on thud.js; when your files are concatenated into one output file, thud.js will be included first.

In addition, Sprockets lets JavaScript files provide other assets — HTML, CSS, images, and the like. At build time, those assets will be copied into the document root of your server (in a way that preserves the sub-structure of directories within). This allows the plugin to refer to those assets via absolute URLs, instead of having to ask you where they’re located.

A few facts are worth special mention.

Sprockets does not require Prototype. Sprockets directives can be inserted into any arbitrary JavaScript file. You can use Sprockets in your build system no matter which JavaScript framework you prefer.
Sprockets does not require Rails. Sam has also written an excellent sprockets-rails plugin, one which deftly applies the conventions of Rails plugins to JavaScript. But he has also written a generic CGI wrapper around Sprockets that is framework-agnostic. Or, instead, you can integrate Sprockets into your build cycle without bothering your server stack with the details. If you use Rake, you can do this with Ruby, as Prototype does; otherwise you can use the sprocketize binary from the command line.
Sprockets-enabled JavaScript files can work just fine without Sprockets. If your plugin has its own “build stage,” then the distributable JavaScript will include no Sprockets directives. On the other hand, if your plugin is small enough not to require this overhead, your distributable can be a short JS file that declares its external dependencies at the top. Because require directives are an extension of comment syntax, they won’t confuse a JS interpreter.

In short, we’re excited about what Sprockets means for the Prototype ecosystem. If you maintain a Prototype add-on library, the prototype-core mailing list would love to help you make it Sprockets-aware.

Now is the time on Sprockets when we dance.

Prototype JavaScript framework - blog: Pimp My Code #1: Element.Storage

Mon, 16 Feb 2009 08:41:00 -0000

Man, it's quiet around here. Interested in doing some pimpin'?

WAIT! COME BACK.

Code pimping. You know? The thing I'd discussed before? Forgive my earlier informality. I see now how my words could have been confusing.

The very first edition of Pimp My Code is special because the code we’ll be looking at will be included in Prototype 1.6.1. (It's a bit like if we were to Pimp [someone's] Ride™, then decide to keep the car for ourselves.) So this is more than just an academic exercise for us — the “pimped” result is now part of the Prototype source code.

The Original

The code in question, from Sébastien Grosjean (a.k.a. ZenCocoon), implements element “storage” — attaching of arbitrary data to DOM nodes in a safe and leak-free manner. Other frameworks have had this for a while; jQuery’s $.fn.data, for instance, is used heavily by jQuery plugin authors to great effect. But Seb’s is based on the similar Mootools API, which I’ve admired since it debuted in Mootools 1.2.

Here’s Seb’s code. It’s a long code block, since he’s been thoughtful enough to comment the hell out of it:

The idea is this: instead of storing arbitrary objects as properties on DOM nodes, create one custom property on the DOM node: an index to a global hashtable. The value of that key in the table will itself be a collection of custom key/value pairs. On top of avoiding nasty IE memory leaks (circular references between DOM objects and JS objects), this has the benefit of encapsulating all of an element’s custom metadata into one place.

Let’s make a first pass at this, line-by-line.

The Critique

Object.extend(Prototype, {UID: 1});

Already we’ve gotten to something I’d change. Seb is using the Prototype namespace correctly here, in that he’s storing something that’s of concern only to the framework and should feel “private.” But my own preference is to move this property into the Element.Storage namespace. I am fickle and my mind is hard to read.

Element.Storage = {
  get: function(uid) {
    return (this[uid] || (this[uid] = {}));
  },

  init: function(item) {
    return (item.uid || (item.uid = Prototype.UID++));
  }
}

OK, another change jumps out at me. The Element.Storage.init method gets called in both Element#store and Element#retrieve; it handles the case where an element doesn’t have any existing metadata. It creates our custom property on the node and increments the counter.

In other words, store and retrieve are the only two places where this method is needed, so I balk at making it public. My first instinct was to make it a private method inside a closure:

(function() {
  function _init(item) {
    return (item.uid || (item.uid = Prototype.UID++));
  }

  // ... rest of storage code
})();

I started down this path but quickly stopped. Instead, we’re going to refactor this part so that the init case is handled without the need for a separate method. Let’s move on for now.

Element.Methods.retrieve = function(element, property, dflt) {
  if (!(element = $(element))) return;
  if (element.uid == undefined) Element.Storage.init(element);
  var storage = Element.Storage.get(element.uid);
  var prop = storage[property];
  if (dflt != undefined && prop == undefined)
    prop = storage[property] = dflt;
  return prop;
};

A few things to mention here.

Variable naming is important. The ideal name for the third parameter of this function would be default, but that’s off-limits; default is a reserved word in JavaScript. Seb’s opted for dflt here, which is clear enough. I’d change it to defaultValue because I like vowels.

As an aside: my first instinct was to remove the defaultValue thing altogether, because I was surprised by the way it behaved. I didn’t find it very intuitive to give Element#retrieve the capability to store properties as well. So I took it out.

I changed my mind several minutes later, when I wrote some code that leveraged element metadata. I had assumed I wouldn’t need the “store a default value” feature often enough to warrant the surprising behavior, but I was spectacularly wrong. I put it back in. Consider that a lesson on how your API design needs to be grounded in use cases.
The idiom in the first line is used throughout Prototype and script.aculo.us (and, in fact, should be used more consistently). It runs the argument through $, but also checks the return value to ensure we got back a DOM node and not null (as would happen if you passed a non-existent ID). An empty return is equivalent to return undefined, which (IMO) is an acceptable failure case. Bonus points, Seb!
The custom property Seb’s been using is called uid. I’m going to change this to something that’s both (a) clearly private; (b) less likely to cause a naming collision. In keeping with existing Prototype convention, we’re going to call it _prototypeUID.
Here’s a nitpick: if (element.uid == undefined). The comparison operator (==) isn’t very precise, so if you’re testing for undefined, you should use the identity operator (===). You could also use Prototype’s Object.isUndefined. In fact, I will.

I have a prejudice against the == operator. Most of the time the semantics of === are closer to what you mean. But this has special significance with undefined, which one encounters often in JavaScript. As an example: when you’re trying to figure out if an optional parameter was passed into a function, you’re looking for undefined. Any other value, no matter how “falsy” it is, means the parameter was given; undefined means it was not.

(Oh, by the way: I am aware of the code screenshot on our homepage that violates the advice I just gave.)
There are other checks against undefined in this function. For consistency I’m going to change these to use Object.isUndefined as well. Also, the check for dflt != undefined is unnecessary: if that compound conditional passes, it means retrieve is going to return undefined anyway, so it doesn’t matter which of the two undefined values we return.

Man, I’m a bastard, aren’t I? Luckily, Element#store is similar enough that there’s no new feedback to be given here, so I’m done kvetching.

Before we rewrite this code to reflect the changes I’ve suggested, we’re going to make a couple design decisions.

Feature Design

While I was deciding how to replace Element.Storage.init, I had an idea: rather than use ordinary Objects to store the data, we should be using Prototype’s Hash. In other words, we’ll create a global table of Hash objects, each one representing the custom key-value pairs for a specific element.

This isn’t just a plumbing change; it’s quite useful to be able to deal with the custom properties in a group rather than just one-by-one. And since Hash mixes in Enumerable, interesting use cases emerge: e.g., looping through all properties and acting on those that begin with a certain “namespace.”

So let’s envision a new method: Element#getStorage. Given an element, it will return the Hash object associated with that element. If there isn’t one, it can “initialize” the storage on that element, thus making Element.Storage.init unnecessary.

This new method also establishes some elegant parallels: the store and retrieve methods are really just aliases for set and get on the hash itself. Actually, retrieve will be a bit more complicated because of the “default value” feature, but we’ll be able to condense store down to two lines.

The Rewrite

Enough blathering. Here’s the rewrite:

Element.Storage = {
  UID: 1
};

As promised, I’ve moved the UID counter. The Element.Storage object also acts as our global hashtable, but all its keys will be numeric, so the UID property won’t get in anyone’s way.

Element#getStorage assumes the duties of Element.Storage.get and Element.Storage.init, thereby making them obsolete. We’ve removed them.

Element.addMethods({
  getStorage: function(element) {
    if (!(element = $(element))) return;

    if (Object.isUndefined(element._prototypeUID))
      element._prototypeUID = Element.Storage.UID++;

    var uid = element._prototypeUID;

    if (!Element.Storage[uid])
      Element.Storage[uid] = $H();

    return Element.Storage[uid];
  },

The new getStorage method checks for the presence of _prototypeUID. If it’s not there, it gets defined on the node.

It then looks for the corresponding Hash object in Element.Storage, creating an empty Hash if there’s nothing there.

As I said before, Element#store is much simpler now:

  store: function(element, key, value) {
    if (!(element = $(element))) return;
    element.getStorage().set(key, value);
    return element;
  },

I thought about returning the stored value, to make it behave exactly like Hash#set, but some feedback from others suggested it was better to return the element itself for chaining purposes (as we do with many methods on Element).

And Element#retrieve is nearly as simple:

  retrieve: function(element, key, defaultValue) {
    if (!(element = $(element))) return;

    var hash = element.getStorage(), value = hash.get(key);

    if (Object.isUndefined(value)) {
      hash.set(key, defaultValue);
      value = defaultValue;
    }

    return value;
  }
});

And we’re done.

Further refinements

In fact, we’re not done. This is roughly what the code looked like when I first checked in this feature, but some further improvements have been made.

Since we’d been using a system similar to this to associate event handlers with nodes, we had to rewrite that code to use the new storage API. In doing so, we found that we needed to include window in our storage system, since it has events of its own. Rather than define a _prototypeUID property on the global object, we give window a UID of 0 and check for it specifically in Element#getStorage.

Also, based on an excellent suggestion, we changed Element#store so that it could accept an object full of key/value pairs, much like Hash#update.

In Summation

I was happy to come across Sébastien's submission. It was the perfect length for a drive-by refactoring; it made sense as a standalone piece of code, without need for an accompanying screenshot or block of HTML; and it implemented a feature we'd already had on the 1.6.1 roadmap.

You can get the bleeding-edge Prototype if you want to try out the code we wrote. Or you can grab this gist if you want to drop the new functionality in alongside 1.6.0.3.

We're further grateful to Mootools for the API we're stealing. And to Wil Shipley for the recurring blog article series we're stealing.

script.aculo.us web 2.0 javascript: JavaScript performance ebook: special discount for script.aculo.us users

Sun, 25 Jan 2009 02:30:00 -0000

Dear script.aculo.us user!

Amy Hoy and Thomas Fuchs have been busy on writing the JavaScript Rocks! Performance ebook, which is now available in beta!

The package consists of a 100+ pages ebook PDF, the DOM Monster, a tool that analyzes your websites and gives tips and hints, and free updates (including the final version, once the book is out of beta).

Topics covered in the book (applicable to all frameworks, not just Prototype and script.aculo.us):

how to know if you’ve got a problem
how to track down bottlenecks
how to create custom profiling tools
how to minimize your load & render time
how to optimize your hosting environment
how not to optimize your JavaScript files
how to write faster DOM code
how to write faster pure JavaScript
how to improve perceived performance
key performance differences between browsers
tips & tricks for JavaScripty iPhone apps

With the following discount code, you get $5 off the listed price.

Discount code: goscripty2. Either go to the JavaScript Rocks! Performance ebook page, and locate the 'have a discount code? click here' link under the big 'Buy Now!' button at the end of the page, or follow this link to enter the code directly.

Thanks for supporting our free materials and open source work on scriptaculous 2.0!

Grab your JavaScript Rocks! Performance ebook!

P.S. Once we're out of beta, this discount code will no longer work, so be sure to grab yours soon!

amok project updates - Google Code: GettingStarted (A getting started guide for new amok users.) Wiki page edited by chrisincambo

Tue, 06 Jan 2009 10:29:18 -0000

amok project updates - Google Code: GettingStarted (A getting started guide for new amok users.) Wiki page edited by chrisincambo

Mon, 08 Dec 2008 08:03:32 -0000

amok project updates - Google Code: amok-0.3.tar.gz (Added support for mocking all instances of a class) file uploaded by chrisincambo

Tue, 02 Dec 2008 08:06:46 -0000

amok project updates - Google Code: GettingStarted (A getting started guide for new amok users.) Wiki page edited by chrisincambo

Tue, 02 Dec 2008 08:04:27 -0000

amok project updates - Google Code: r27 (added mock_all_with method to allow all class instances to b...) committed by chrisincambo

Tue, 02 Dec 2008 07:57:15 -0000

added mock_all_with method to allow all class instances to be a mock

script.aculo.us web 2.0 javascript: V1.8.2: Prototype 1.6.0.3, service release/bug fixes

Tue, 18 Nov 2008 17:42:00 -0000

This is a bugfix release that bumps script.aculo.us to version 1.8.1.

This version is recommended for all users.

Update to Prototype 1.6.0.3
Make sure InPlaceEditor converts HTML entities to text. [Sean Kirby]
Fix that Builder.node did not return extended elements on IE. Closes #71 and #77.
Fix a bug in Sortable.destroy to make sure it's called on the referenced Sortable only, which allows for the correct intialization of nested Sortables. Closes Trac #8615. [Leon Chevalier]
Change Effect.Base#render not to use eval(), so certain JavaScript runtime environments (like Adobe AIR) that do not support eval() work. [King Maxemilian, John-David Dalton]
Fixed a calculation error in Effect.Transitions.pulse that could lead to flickering, add easing and change it to be a normal 0 to 1 transition that can be used with any effects; Effect.Pulsate now uses its own implementation. [Thomas Fuchs]
Fixed Effect.ScrollTo. Changeset 8686 had a typo, document.viewport.getScrollOffsets[0] is always undefined. Removed the max check as it is not a cross-browser way to get scroll height and breaks the effect. Depending on scrollTo to do the right thing. Closes #11306. [Nick Stakenburg]
Update version check so all Prototype versions can be required, not just x.x.x. Closes #10966. [Nick Stakenburg]
Using $$ in the loader instead of getElementsByTagName to prevent limitations. Closes #9032. [Nick Stakenburg]
Fix some missing semicolons. [jdalton]
Fix an issue with Effect.ScrollTo that caused Firefox to scroll to the wrong offset in some situations. Closes #10245. [nik.wakelin]
Fixes an issue with IE ghosting on non-absolute elements. Closes #10423. [Tanrikut, tdd]

Prototype JavaScript framework - blog: Prototype Linkedin Group

Fri, 17 Oct 2008 07:32:00 -0000

When we first launched the Linkedin Prototype Group, we weren’t necessarily expecting it to be such a success–it’s over 800 members strong and counting.

Also, at the time, there wasn’t much you could do after having joined the group. This has changed with the recent introduction of discussions.

One of the first posts spurred some thoughts about the usefulness and goals of this Linkedin group especially given the high quality of our new mailing list. (And let me take the opportunity to sincerely thank T.J. Crowder for all the effort he’s put into it.)

My initial reaction, based on an early August thread was to suggest keeping the development-orientated discussions in the mailing list, while expecting more career-orientated ones to take place in the Linkedin group.

Of course, there’s no way we can nor should be controlling this, and in the end, you will be deciding what will happen where. So I suppose the only real raison d’être of this post is to advise you of this new feature and open up the debate.

Thoughts ?

Prototype JavaScript framework - blog: Want your code "pimped"?

Tue, 07 Oct 2008 21:23:00 -0000

We decided it’s finally time to implement an idea we had long ago.

I’m an avid reader of the blog of Wil Shipley, a man in the business of writing great apps for OS X. His running code improvment series, Pimp My Code, takes submissions from readers who think their code needs refactoring. Then Shipley refactors them, explaining the whys and hows along the way. The submissions are small (never more than 75-100 lines), but in rewriting them Shipley always happens upon specific, useful programming tips. I don’t know the first thing about Objective-C, but I find the series fascinating and instructive.

So we’re going to do something similar on this blog. Do you have a piece of JavaScript you want refactored? Does it use Prototype? Do this:

Sign up for a GitHub account if you don’t have one. It’s free and quick.
Go to Gist, GitHub’s pastebin app, and paste the code you want us to refactor. Mark it as “private” if you like.
Message me on GitHub with the URL to your code snippet. If necessary, explain a bit about what the code does (or should do), but don’t write an epistle or anything.

I’ll share the submissions with the rest of the team and we’ll pick a few that we like. Then we’ll dedicate a post to each one, refactoring out loud along the way. We won’t be mean or snarky; this is not a DailyWTF-style exercise.

To pre-empt the obvious rebuttal: we do not consider this to be an act of charity, or code manna from computer heaven, or a gift from the light-bearers to the huddled masses. Whether we actually “improve” your code is not for us to say. It will, however, illustrate our coding style.

If that sounds useful to you, then step up! Give us code and ask that it be pimped!

Prototype JavaScript framework - blog: Growing the community

Tue, 07 Oct 2008 17:39:00 -0000

Now that 1.6.0.3 is out, let’s talk about the Prototype community.

A lot of people have been commenting on how quiet it’s been around here over the last few months. There are several reasons:

We were quite busy with behind-the-scenes stuff. Moving to GitHub and Lighthouse was quite the task. As part of that migration we went through all the bugs on the old Rails Trac and were therefore left with a large backlog of bugs that we’d waited too long to address.
We were quite busy with our day jobs. Only a couple of us are freelancers; the rest work full-time for software companies. And usually there are several people working on Prototype at any one time, but over the summer it’s rarely been more than one or two.
In an effort to “catch up” with the accumulated tickets, we tried to stuff too much into a single bugfix release. We need to keep releases small and focused; trying to change too much at once tends to disorient us and our users. Once we realized we needed to scale back this release, it took a while to figure out which changes needed to stay and which needed to be reverted.

These aren’t excuses; they’re just explanations. As a team, we agree that we’ve got to prevent such a long release gap from happening again, and to keep an eye out for warning signs like the ones listed above.

This means, among other things, that we’re planning to move away from a “when it’s ready” release schedule. Instead, we’ll move toward one in which there are several releases per year; whatever is ready in time for a given release will go in, and whatever is not will have to wait. That applies to bug fixes and features alike. Eight months between releases just won’t work.

What you can do

Community outreach was one of the major goals of Prototype Developer Day. Many people are frustrated with the state of the Prototype community and would like to see some changes made. We’re in complete agreement.

Ideally, as an open-source community grows, those who want to help out gravitate toward specific roles. Those who can grok the source code write patches; those who are good at diagnosing problems file bug reports; those who can write clearly contribute documentation; and so on. We’d love to grow that “halo” around Prototype Core so that things can get done more quickly.

To be more specific, we would love help in any of these areas:

Give support on the Prototype & scrip.aculous mailing list.
File bugs in Lighthouse when you encounter errors or surprising behavior in Prototype.
Write test cases or patches for existing bugs in Lighthouse.
Discuss the direction of the library and its future on the Prototype Core mailing list.
Propose new features and implement them.
Write documentation wherever you feel we need more; submit it to Lighthouse as an enhancement.
Suggest blog posts. (Or even write them!) Post to the Prototype Core list if you’re interested in doing this.

There are, of course, many other things one can do to help us out. But if you’re looking for a way to contribute and don’t have something specific in mind, we’d suggest doing one of these seven things.

What we can do

We know we need more help, but we also know we need to be better community curators. So here are some things we pledge to do better:

We’ll beef up the Prototype web site so that it’s easier to get started with the framework, easier to find great resources like Scripteka and Prototype UI, and easier to find answers to common questions.
We’ll give special attention to documentation tickets on Lighthouse so that our API docs don’t stay stale and thin.
We’ll release on a more consistent schedule, as explained above.
We’ll resume work on PDoc (inline documentation) and Sprockets (JS dependency management), spin-off projects that make Prototype more of a “platform.” They’ll be a boon to the Prototype ecosystem when they’re completed.

Finally: if you consider yourself to be good at planning and organizing an open-source project, then we’d love your input on how to grow our community. Our highest priority, however, is not to launch a new initiative or process; it’s to get more people doing the seven things listed above.

Prototype JavaScript framework - blog: Prototype 1.6.0.3: A long-awaited bugfix release

Tue, 30 Sep 2008 17:48:00 -0000

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.

Developers who follow along in Git might’ve noticed that the repository has seen a lot of disruptive activity in the last few days as we reassessed many of the commits that had gone into the library since April. Rather than try to fit too many fixes into one release, we decided to scale back and release 1.6.0.3 with the set of improvements we were in complete agreement on.

Because of the way we handled this overhaul, those who try to update their Git working copies to the latest trunk will encounter conflicts, even if they hadn’t made local changes.

Here’s how we recommend bringing your working copy up to date:

First, if you’ve made any local changes, please create a new branch so that those changes aren’t lost.
On your local master branch, run:
```
git fetch origin master
git reset --hard 34ee207
```
The first line fetches the new commits without trying to apply them to your local copy. The second line resets your master branch to be in sync with the latest revision.
From there, you can cherry-pick from your branch any local commits you made (though you may have to do some manual merging).

Download, report bugs, and get help

Download Prototype 1.6.0.3
Submit bug reports to Lighthouse
Get Prototype help on the Prototype & script.aculo.us mailing list or #prototype IRC channel
Interact with the Core Team on the prototype-core mailing list

As always, thanks to the core team and the many users who contributed bug reports and well-tested patches for this release.

amok project updates - Google Code: r26 (Added ability to pass message to callback in and_callback) committed by chrisincambo

Thu, 18 Sep 2008 08:06:34 -0000

Added ability to pass message to callback in and_callback

amok project updates - Google Code: r25 (Added latest version of amok which supports mocking callback...) committed by chrisincambo

Thu, 18 Sep 2008 07:40:15 -0000

Added latest version of amok which supports mocking callbacks

amok project updates - Google Code: r24 (Added and_callback to the amok.DSL) committed by chrisincambo

Thu, 18 Sep 2008 07:38:52 -0000

Added and_callback to the amok.DSL

amok project updates - Google Code: r23 (Added and_callback method) committed by chrisincambo

Thu, 18 Sep 2008 07:28:31 -0000

Added and_callback method

Prototype JavaScript framework - blog: Practical Prototype and script.aculo.us

Mon, 11 Aug 2008 13:48:00 -0000

We’re very happy to announce a new addition to the Prototype bookshelf: core committer Andrew Dupont’s Practical Prototype and script.aculo.us published by Apress.

Obviously, Practical Prototype and script.aculo.us covers all you need to know about the latest versions of Prototype and script.aculo.us. But it goes well beyond that. Andrew does an awesome job at setting the context and giving appropriate background information, so much so that you’ll end up knowing not only the how but also the why. In the ruthless world of client-side development, that’s a serious asset!

Practical Prototype and script.aculo.us is a pleasure to read – the style is both straightforward and witty – and should appeal to beginners and seasoned developers alike.

If you want to try before you buy, you can always download a sample chapter or the table of contents from the Apress website. Or you can grab a hard copy and/or a pdf from the Apress website or from Amazon.

As always, happy Prototyping!

amok project updates - Google Code: r22 (First commit) committed by chrisincambo

Sun, 27 Jul 2008 08:39:50 -0000

First commit

amok project updates - Google Code: r21 (First commit) committed by chrisincambo

Sun, 27 Jul 2008 08:39:17 -0000

First commit

amok project updates - Google Code: r20 (Added license block) committed by chrisincambo

Sun, 27 Jul 2008 08:30:19 -0000

Added license block

amok project updates - Google Code: r19 (Changed comment) committed by chrisincambo

Sun, 27 Jul 2008 08:07:09 -0000

Changed comment

amok project updates - Google Code: Default_DSL_documentation (Documentation for the default domain specific language (DSL)) Wiki page edited by chrisincambo

Sun, 27 Jul 2008 08:03:56 -0000

amok project updates - Google Code: Default_DSL_documentation Wiki page edited by chrisincambo

Sun, 27 Jul 2008 08:02:00 -0000

amok project updates - Google Code: Default_DSL_documentation Wiki page added by chrisincambo

Sun, 27 Jul 2008 08:00:23 -0000

amok project updates - Google Code: GettingStarted (A getting started guide for new amok users.) Wiki page edited by chrisincambo

Sun, 27 Jul 2008 06:39:52 -0000

amok project updates - Google Code: GettingStarted (A getting started guide for new amok users.) Wiki page added by chrisincambo

Sun, 27 Jul 2008 06:38:54 -0000

amok project updates - Google Code: using_amok Wiki page deleted by chrisincambo

Sun, 27 Jul 2008 06:38:01 -0000

amok project updates - Google Code: using_amok (A quick how to guide for new amok users.) Wiki page edited by chrisincambo

Sun, 27 Jul 2008 06:34:37 -0000

Prototype JavaScript framework - blog: First Prototype Developer Day: Monday September 29, 2008!

Fri, 25 Jul 2008 16:29:00 -0000

Prototype Core is happy to announce the first Prototype Developer Day! The Prototype Developer Day is going to be a recurring event bringing together Prototype Core members and users from the Prototype community to share experiences, offer insight into what’s coming up, and discuss topics like contribution, support, and the Prototype ecosystem. If you’re big on Prototype, you cannot miss this!

This fall, the Prototype Developer Day is being held in conjunction with The Ajax Experience, held in Boston from Monday, September 29 to Wednesday, October 1 2008. The Prototype Developer Day itself will happen on Monday.

Admission to the Developer Day is free. If you’re interested in attending the full three days of The Ajax Experience, you can save $100 with the code Prototype. Register before August 22nd and save an additional $100.

The provisional agenda for this Prototype Developer Day is as follows (more details coming up on the full agenda):

Start time	End time	Session	Speaker
8:00am	8:30am	Intro/Welcome	Prototype Core
8:30am	9:30am	Contributing docs	Christophe Porteneuve
9:30am	9:45am	Break
9:45am	9:50am	Greeting	Framework Summit Sponsor
9:50am	10:30am	Contributing code	Andrew Dupont
10:30am	11:15am	The Prototype ecosystem	TBD
11:15am	11:30am	Break
11:30am	1:00pm	Extended Q&A	Prototype Core

You will get a chance to hook up with members of Prototype Core and “close core”, and we all look forward to meeting you guys. Here’s the current rundown:

Sam Stephenson (to be confirmed)
Andrew Dupont (confirmed)
Juriy “kangax” Zaytsev (confirmed)
Mislav Marohnić (to be confirmed)
Tobie Langel (to be confirmed)
Christophe Porteneuve (confirmed)

For more information on coming with a group, contact Tracey West. You can view the agenda for The Ajax Experience, and then proceed to one or both of the following:

Want to register for PDD? You must use our special quick form. Registering for TAE doesn’t automatically sign you up for PDD, and the number of seats is pretty limited. (But, hey, there’s a free lunch!)
Register for The Ajax Experience.

script.aculo.us web 2.0 javascript: script.aculo.us development setup changed to github and Lighthouse

Fri, 09 May 2008 18:15:00 -0000

script.aculo.us is from now on developed using Git (hosted at github) for source code management and revision control, and Lighthouse for bug tracking.

Why git instead of Subversion? Well, it simply rules supreme, and makes working with many distributed developers with lots of branches a snap. You can find a good intro book on Git on Peepcode.

script.aculo.us 1.xx development will focus on bug fixes only, while I’m working on the next version of scripty (post on that coming up soon!).

Bug tracker http://prototype.lighthouseapp.com/projects/8887-script-aculo-us

Repository for script.aculo.us 1.xx http://github.com/madrobby/scriptaculous

Note that if you’re just using the library, this change won’t really affect you.

If you have open bugs on the old Trac please port them over to lighthouse yourself!

I’m also working on a replacement for the documentation wiki (which, quite honestly, sucks); so stay tuned for some updates in the near future. If you want to help out with the documentation effort, please contact me. :)

script.aculo.us web 2.0 javascript: V1.8.1: Prototype 1.6.0.1, bug fixes

Fri, 04 Jan 2008 03:15:00 -0000

This is a bugfix release that bumps script.aculo.us to version 1.8.1.

Mainly, this release contains some important bug fixes and optimizations in Prototype, fixes cursor keys in autocompleting text fields for IE and Safari plus fixes an issue with Effect.Morph on IE.

Download at http://script.aculo.us/downloads!

script.aculo.us web 2.0 javascript: V1.8.0: Prototype 1.6, Sound, tweaks and tricks

Thu, 08 Nov 2007 14:05:00 -0000

This is the final version of script.aculo.us 1.8, which comes with Prototype 1.6.0 final.

The included final 1.6.0 version of Prototype brings the latest and greatest awesome new features -- be sure to check it out on the Prototype site.

See the announcement for more information and a download link!

script.aculo.us web 2.0 javascript: V1.7.1 beta 3: Prototype 1.5.1, more optimizations and fixes

Fri, 25 May 2007 16:30:00 -0000

This is third beta of script.aculo.us 1.7.1, which provides Prototype 1.5.1 final compatibility and Sortable speed improvements.

The included final 1.5.1 version of Prototype brings the latest and greatest in new cool features and performance gains, so be sure not miss this one. :)

Beta warning: Things might not work as you might expect, though they really should—if you hit any problems, please use the bug tracker and give reports. The same that applies to Prototype applies for script.aculo.us too, so read the how to contribute page to see how you can help out!

See announcement for more information and a download link!

script.aculo.us web 2.0 javascript: V1.7.1 beta 1: 'Performance!'.times(3) + Sound

Mon, 12 Mar 2007 14:00:00 -0000

On the heels of the recent Prototype 1.5.1 release candidate, here’s the latest and greatest version of script.aculo.us: 1.7.1 beta 1.

The most important change is the update to Prototype 1.5.1 which yields major performance improvements, slick new JSON support and various fixes all around. Note that the version of Prototype that comes with script.aculo.us 1.7.1 beta 1 is actually a few steps ahead of the 1.5.1_rc1 release and already incorporates a few additional fixes, so please use the version that comes with the script.aculo.us download.

The other important feature is experimental sound support for those little .mp3-based sound effects, which works natively in IE, and relies on whatever mp3 plugins are available on other browsers (for Macs, this means quicktime). It’s thought as an alternative to flash-based mp3 playback for sounds effects (not music!). Kudos to Jules Gravinese for coming up with the initial implementation of this!

The effects engine has seen some performance overhaul, and together with the new Prototype performance goodnees is screaming fast. Also, a memory leak in the morph code was found and fixed on Firefox. More changes and features added include a new “failure” option to Draggables, and onDropped callback, more customization for in-place editing, and nesting single nodes in the DOM builder.

See the complete announcement for more information and a download link!

script.aculo.us web 2.0 javascript: V1.7.0: Morphing effects, Prototype 1.5.0 final

Fri, 19 Jan 2007 18:30:00 -0000

You've seen the demos-- now it's prime time!


* Update to Prototype 1.5.0 final

* Change the default setting for effects to support up to 60fps, if renderable by the browser. Add performance info to effects unit test.

* Add hash and CSS className support to Effect.Morph, fixes #6674 [Tobie]
    Examples:
      $(element).morph('myClass')
      // will morph to all the properties specified
      // in .className (in your external stylesheet).
      // All properties which cannot be morphed (such as font-style)
      // will be applied AfterFinish
      $(element).morph('font-size: 10px')  // or
      $(element).morph({fontSize: '10px'}) // will morph the font-size to 10px
      
* Add Element.morph() and Element.Methods.morph() as a shortcut to Effect.Morph
    Example:
      // basic Effect.Morph
      $('error_message').morph('color:#f00;font-size:17px');
      // fade out after a while
      $('error_message').show().morph('font-size:17px').morph('opacity:0',{delay:4});

* Add Effect.Transform that generates parallel executing Effect.Morph sets
    Example:
      // set up transformation
      var transformation = new Effect.Transform([
        { 'div.morphing': 'font-size:20px;padding-left:40em' },
        { 'blah'        : 'width:480px;border-width:10px;border-right-width:20px;margin:200px;margin-bottom:-20px;font-size:30px' }
      ],{ duration: 0.5 });
      // play transformation (can be called more than once)
      transformation.play();

* Add Effect.Morph core effect that morphs to a given CSS style rule. Effect.Morph does take orginal styles given by CSS style rules or the style attribute into consideration when calculating the transforms. It works with all length and color based CSS properties, including margins, paddings, borders, opacity and text/background colors.
    Example:
      new Effect.Morph('mydiv',{
        style: 'font-size:3em;color:#f00;border-width:2em',
        duration: 2.0
      });
      
* New option keepBackgroundImage: true for Effect.Highlight, fixes #5037 [docwhat, tomg]

* Minor tweaks for issues with application/xhtml+xml documents on Firefox, fixes #6836 [sjinks]

* Fix a possible exception with Sortables, fixes #6828 [craiggwilson]
      
* Add a paramName option to the inplace editor for overriding the default parameter name of "value"

script.aculo.us web 2.0 javascript: V1.7.0 beta 2: morphing with CSS classes, Prototype update

Mon, 18 Dec 2006 22:30:00 -0000

The second beta of script.aculo.us 1.7.0 is out now, and adds a cool new CSS classnames based morphing feature, alongside Prototype updates.

Bugs in beta 1 where also addressed, especially Opera compatibility.

Head over to mir.aculo.us to learn what this is about and grab the beta version!

Note: Obviously, the beta version is not recommended for production sites, and syntax might change before it gets stable (but it's pretty much final, so don't be too afraid).

script.aculo.us web 2.0 javascript: V1.7.0 beta 1: Morphing?!

Tue, 21 Nov 2006 09:50:00 -0000

The first beta of script.aculo.us 1.7.0 is out now, and brings you (tada!) morphing!

Head over to mir.aculo.us to learn what this is about and grab the beta version!

Note: Obviously, the beta version is not recommended for production sites, and syntax might change before it gets stable (but it's pretty much final, so don't be too afraid).

script.aculo.us web 2.0 javascript: V1.6.5: Effect.Event, latest Prototype, Builder updates

Wed, 08 Nov 2006 13:34:00 -0000

I’ve just pushed script.aculo.us 1.6.5 for your download pleasure. It’s a maintenance release that adds a few tweaks here and there—read on!

Update to Prototype 1.5.0_rc1 revision [5462]

Support the HTML ‘for’ attribute in Builder by using ‘htmlFor’, fixes #6472 [gjones, tdd]

var node = Builder.node('label', { htmlFor: 'myinput' });

Add support to run a specific failing unit test by clicking on the corresponding test result, fixes #6290 [leeo]

Add modifier key support to Event.simulateMouse, fixes #6391 [savetheclocktower]

Add new ‘with-last’ queue position option to queue effects to occur in parallel with the last effect to start in the queue

Add new special core effect Effect.Event for one-shot events that follow timelines defined by effect queues

123	new Effect.Event({ afterFinish:function(){ // do some code here}, position: 'end' });

Fix an possible crash of IE on Effect.SlideUp, fixes #3192 [thx nel]

Add Builder.build() to create nodes from strings containing HTML, [DHH]

var node = Builder.build("<p>this is <b>neat!</b></p>");

Add a pulses parameter to Effect.Pulsate to control the amount of pulses, fixes #6245 [leeo]
For example, this will pulsate twice (if the option is not given, it defaults to five pulses):

Effect.Pulsate('d8', {pulses: 2});

Fix an issue with clicking on a slider span resulting in an exception, fixes #4707 [thx sergeykojin]

Fix an issue with Draggables when no options are supplied, fixes #6045 [thx tdd]

This should be the last release before Ruby on Rails 1.2 comes out—the next thing will be script.aculo.us 1.7! Lots of good and cool patches are waiting for their addition, and should make it into the 1.7 release.

As always, kudos to the community for supplying patches, bug reports and tests—keep it coming!

script.aculo.us web 2.0 javascript: V1.6.4: New Prototype, drag and drop updates, BDD style testing! (UPDATED)

Tue, 05 Sep 2006 11:26:00 -0000

V1.6.4 (2006-09-06): New Prototype, drag and drop updates, BDD style testing! (UPDATED)

script.aculo.us 1.6.4, which marks the inclusion of the new release candidate of Prototype 1.5, is out now.

(For those of you missing the 1.6.3 version: that version was out yesterday but had a issue with IE that is now fixed in 1.6.4)

This release comes with the brand-new Prototype V1.5.0_rc1 version, adds several new features and options to drag and drop, features a whole new (experimental) way of doing testing, and adds some other goodies here and there. Also, thanks to the contributors for identifying and squishing bugs!

So—what’s new & cool?

Update Prototype to V1.5.0_rc1 (read more on Justin Palmer’s blog)

Add experimental alternate syntax for unit tests (Behaviour Driven Development-style)

Merge assertElementsMatch and assertElementMatches from Prototype’s [4986] unittest.js [Sam Stephenson]

Add assertRespondsTo and shouldRespondTo assertions


                  // object
                  var testObj = {
                    isNice: function() { }
                  }

                  // test
                  assertRespondsTo('isNice', testObj);

Make Sortable.serialize handle DOM IDs like “some_element_1” correctly, fixes #5324

Add support for onStart, onDrag and onEnd events directly on Draggables (invoked from the Draggables.notify), fixes #4747 [thx scriptkitchen]


                  new Draggable('some_id',{
                    onStart:function(){ /* ... */ },
                    onDrag:function(){ /* ... */ },
                    onEnd:function(){ /* ... */ }
                  });

Add autoSelect option to Autocompleters to auto select an entry if only one is returned, fixes #5183 [thx cassiano dandrea]

Added delay option to Draggables and Sortables, see test/functional/dragdrop_delay_test.html for usage, implements #3325 [thx lsimon, tomg]

Add version and timestamp to indvidual library files for easier identification (the files are preprocessed by the Rake fresh_scriptaculous task), fixes #3015 [thx Tobie]

Add assertIndentical and assertNotIdentical unit test assertions, which test for equality and common type, fixes #5822 [thx glazedginger]

Add integration test for Ajax autocompleter for results with no linebreaks, #4149

Added a custom exception to all base effects when used on non- existing DOM elements, added a assertRaise method to unit tests

Add element shortcuts to Builder that can be activated by calling Builder.dump() (see the unit test), fixes #4260 [thx napalm]


                  Builder.dump();  
                  var element = DIV({id:'ghosttrain'},[
                     DIV({style:'font-size: 11px; font-weight: bold;'},[
                       H1('Ghost Train'),
                       "testtext", 2, 3, 4,
                       UL([
                         LI({onclick:'alert(\'test\')'},'click me')
                       ]),
                     ]),
                   ]);

Make Effect.Puff work correctly for floating elements, fixes #3777 [thx michael hartl]

Fix selection of correct option in SELECT element generated by InPlaceCollectionEditor for indexed option arrays, fixes #4789 [thx steve]

Fix an issue with redrawing ghosted draggables that are inside a scrolled container, fixes #3860 [thx gkupps, tsukue]

Fix autoscrolling inside scrollable containers when window is scrolled too, fixes #5200 [thx wseitz]

Fix autoscrolling when dragging an element unto a scrollable container, fixes #5017 [thx tomg]

Fix a condition where overriding the endeffect on Draggables without overriding the starteffect too leads to a Javascript error [thx Javier Martinez]

Fix a possible error with the drag/drop logic (affects the solution to #4706)

Fix various issues with IE detection and Opera, and setOpacity, fixes #3886, #5973

Remove revert cache code obsoleted by #4706, fixes #3436 (again) [thx tomg]

As always, the required 1.5.0_rc1 version of Prototype is included with the download.

Big thanks to the contributors!

script.aculo.us web 2.0 javascript: V1.6.2: Bug fix galore!

Tue, 15 Aug 2006 15:32:00 -0000

V1.6.2 (2006-08-15): Bug fix galore!

This is a "serive" release and recommended for all users. While almost no new features where added, it includes several bug fixes, ranging from important (memory leak!) to cosmetic. List of updates:

Fix a problem in the drag and drop logic if an reverting/drag ending draggable was initialized for a new drag (for example by clicking repeatedly) for all cases where the default start/revert/end-effects are used, fixes #4706 [thx tecM0]
Fix possible memory leaks with Draggables, fixes #3436 [thx aal]
Throw nicer errors when requires script.aculo.us libraries are not loaded, fixes #5339
Make slider handles work when not displayed initially by using CSS width/height, fixes #4011 [thx foysavas]
Update sortable functional test with onUpdate counter
Make more Element extensions unit tests work on Safari
Add the assertMatch unit test assertion for asserts with RegExps [thx Ian Tyndall]
Fix a problem with Effect.Move causing "jumping" elements because of very low float numbers in some situations
Fix a missing semicolon in dragdrop.js, fixes #5569 [thx mackalicious]
Fix a slight inaccuracy with Effect.Scale that could lead the scaling to be one pixel off
Be more prototypish with Effect.Transitions.linear
Make Effect.Scale recognize font sizes that use the pt unit, fixes #4136 [thx aljoscha]
Fix IE hack in Effect.Opacity, fixes #5444 [thx nicholas]
Fix IFRAME layout fix for IE and Autocompleter, fixes #5192 [thx tommy skaue]
Fix only option in onEmptyHover, fiex #5348 [thx glenn nilsson]
Fix Effect.BlindDown and SwitchOff handling of supplied callbacks, fixes #5089 [thx martinstrom]
Fix a problem with field focus on Ajax.InPlaceEditor and loading external text, fixes #4988, #5244 [thx rob]
Do not attempt to scroll if scrollspeed is 0/0, fixes #5035 [thx tomg]
Fix a problem with Sortable Tree serialization, fixes #4939, #4688, #4767 [thx Sammi Williams]
Fix an endless loop with sliders, fixes #3226, #4051, #4765 [thx jeff]
Make autocompleter work with update DIVs that have scrollbars, fixes #4782 [thx Tommy Skaue]
Corrected options parsing on switchoff effect, fixes #4710 [thx haldini]

The required 1.5.0_rc0 final version of Prototype is included with the download.

script.aculo.us web 2.0 javascript: V1.6.1: Sortable Trees, Prototype 1.5.0_rc0 (fixes IE mem leaks)!

Thu, 06 Apr 2006 21:27:00 -0000

V1.6.1 (2006-04-06): Sortable Trees, Prototype 1.5.0_rc0 (fixes IE mem leaks)!

New features in V1.6.1 and V1.6.0:

Update to Prototype 1.5.0_rc0
Sortable trees [thx Sammi Williams, sammi@oriontransfer.co.nz]
See the functional test (test/functional/sortable_tree_test.html) and the CHANGELOG for more information!
Add Draggable object as third parameter to snap, fixes #4074 [thx mdaines]
Add parsing/setting of any currently set opacity CSS rule to default opacity effect on draggables, fixes #3682 [thx Mike A. Owens]
Added benchmark method to unittest.js; some cleaning up of unit tests
Major speedup for sortable with handles initialization [thx Jamis Buck]
Add passing through of scroll options from Sortable to Draggable [thx Gregory Hill]
Make it possible to scroll window on dragging, #3921 [thx rdmiller]
added visualEffect method for the Element Mixin, fixed so you can chain multiple calls. [Rick Olson]

Bug fixes:

Fix an IE flicker with SlideUp/SlideDown, fixes #3774, [thx sbbowers]
Fix a problem with window scrolling on draggables [thx Gregory Hill]
Fix a problem with id-based handle names and draggables
Fix shift-tab for autocompleter in Safari, fixes #4423 [thx matt]
Make Element.forceRerendering give up on any exception (this fixes various problems with IE)
Fix only option on Sortable.create to accept multiple class names, fixes #3427 [thx glenn nilsson]
Added workaround for a rendering bug in Safari when using floating elements with Effect.Appear

The required 1.5.0_rc0 final version of Prototype is included with the download.

script.aculo.us web 2.0 javascript: script.aculo.us training in Austria: "Ajax richtig verwenden"

Fri, 24 Feb 2006 18:45:00 -0000

Ajax training for a german speaking audience – here is the german press release:

In diesem eintägigen Seminar zeigt Ihnen Thomas Fuchs wie Sie die Benutzerfreundlichkeit und Interaktivität ihrer Websites verbessern. Das Seminar bietet einen Überblick über verbreitete Ajax-Entwicklungswerkzeuge und fokusiert auf die Verwendung der Prototype-Bibliothek und script.aculo.us. Weiters werden die Möglichkeiten der integrierten Ajax-Funktionalität von Ruby on Rails demonstriert.

Also, nichts wie anmelden, nur 20 Plätze verfügbar!

script.aculo.us web 2.0 javascript: Version 1.6.0: Switch to Prototype 1.5, draggable window scrolling, bug and performance fixes!

Wed, 22 Feb 2006 09:57:00 -0000

V1.6.0 (2006-03-28): Switch to Prototype 1.5, draggable window scrolling, bug and performance fixes!

New in V1.6.0:

Major speedup for sortable with handles initialization [thx Jamis Buck]
Update to latest Prototype 1.5.0_pre1 trunk
Fix shift-tab for autocompleter in Safari, fixes #4423 [thx matt]
Refactor effects.js to use the new Prototype 1.5 Element Methods syntax
Add passing through of scroll options from Sortable to Draggable [thx Gregory Hill]
Make it possible to scroll window on dragging, #3921 [thx rdmiller]
Make Element.forceRerendering give up on any exception (this fixes various problems with IE)
added visualEffect method for the Element Mixin, fixed so you can chain multiple calls. [Rick Olson]
Fix only option on Sortable.create to accept multiple class names, fixes #3427 [thx glenn nilsson]
Added workaround for a rendering bug in Safari when using floating elements with Effect.Appear

Note: The required 1.5.0_pre1 final version of Prototype is included with the download.

script.aculo.us web 2.0 javascript: Version 1.5.3: Ajax.InPlaceCollectionEditor, Sortable.setSequence, bug fixes!

Wed, 22 Feb 2006 09:57:00 -0000

V1.5.3 (2005-02-22): Ajax.InPlaceCollectionEditor, Sortable.setSequence, bug fixes!

New in V1.5.3:

Added Ajax.InPlaceCollectionEditor which uses a SELECT element instead of a text field (see test/functional/ajax_inplacecollectioneditor_test.html for usage), #3491 [thx anna]
Added Sortable.setSequence to programmatically reorder a Sortable, #3711 [thx Mike A. Owens]
Enable in place editor to use RJS (implements a new evalScripts option for the in place editor), #3490 [thx Richard Livsey]
Make name option on Sortable.serialize work again, fixes #3873
Make dragging cancel only on ESC key, not on any key, fixes #3817
Fix span positioning for sliders with ranges not starting at 0, fixes #3731 [thx michal]
Remove unneeded height restoring in Effect.BlindDown as that is handled internally by the restoreAfterFinish option to Effect.Scale, fixes #3667 [thx Ross Lawley]
Added unit test for #3732 (currently fails due to Prototype #3877) [thx michal]

script.aculo.us web 2.0 javascript: Version 1.5.2: Auto-scrolling option for Draggables and Sortables, Limit option for effect queues, Sortable.sequence, bug fixes!

Tue, 14 Feb 2006 10:20:00 -0000

V1.5.2 (2005-02-14): Auto-scrolling option for Draggables and Sortables, Limit option for effect queues, Sortable.sequence, bug fixes!

New in V1.5.2:

Added auto-scroll option to Draggables and Sortables, activate with scroll: 'id_of_scroll_container_element'. See test/functional/dragdrop3_test.html for usage/demo
Add limit option to effect queues to limit the maximum number of effects in a queue, new unit tests for scoped effect queues, fixes #3498 [thx Abdur-Rahman Advany]
Add Sortable.sequence method to extract the current sequence of a Sortable as an array, fixes #3675 [thx sphivo]
Added activate method to Autocompleter that allows you to trigger the suggestions through other means than user input [DHH]
Add assertEnumEqual for unit testing (from Prototype SVN trunk) [Sam Stephenson]
Element.collectTextNodesIgnoreClass to correctly filter child nodes, fixes #3380 [thx lam]
Fix a condition where OPTION elements could cause unwanted dragging on Draggables, fixes #3441 [thx tom]
Fix a crash because of an IE bug in Effect.SlideDown, fixes #3192 [thx Rob Mayhew]
Fix a wrong parameter in dragdrop.js, fixes #3555
Fix two typos in effects.js, fixes #3481 [thx jtolds]

script.aculo.us web 2.0 javascript: script.aculo.us wiki relaunched, now hosted by Stikipad

Sun, 15 Jan 2006 17:00:00 -0000

The script.aculo.us documentation wiki is now hosted by the nice guys over at Stikipad, a hosted wiki solution currently in beta (and yes, it’s a Rails app, naturally).

That being said, we’re going to be launching soon and you’ll be able to try out us out free of charge – who knows, we might even throw in a perk for being a script.aculo.us fan!

Thanks for giving the script.aculo.us wiki a new home, guys!

script.aculo.us web 2.0 javascript: Version 1.5.1: Effect.toggle, local effect queues, Effect.Move, bug fixes!

Tue, 27 Dec 2005 19:00:00 -0000

V1.5.1 (2005-12-27): Effect.toggle, local effect queues, Effect.Move, bug fixes!

New in V1.5.1:

Add select option to Autocompleter to optionally use textnodes from elements with a specific CSS class (see test/functional/ajax_autocompleter_test.html for usage)
In-place editor: add ok/cancel visibility options and onblur() submission, fixes #3233 [thx pulsation] (Note: currently, blur form submission breaks the cancel link functionality, if enabled)
Added Effect.toggle for slide, blind and appear/fade effects, fixes #2704 [thx Azad]
Added selective component loading to scriptaculous.js, see test/unit/loading_test.html for usage [thx David Zülke]
Added local/scoped effect queues [thx David Zülke]
New core effect Effect.Move that can do absolute/relative movement [thx David Zülke]
Make default effects options modifyable globally by setting Effect.DefaultOptions
Make Draggables recognize top/left CSS properties defined in an external stylesheet, fixes #3205 [thx ansonparker]
Fixed draggables starting to drag even if mouse button was released with no movement, [thx topfunky]

script.aculo.us web 2.0 javascript: Version 1.5.0 final!

Tue, 13 Dec 2005 18:46:00 -0000

V1.5.0 final Release: Celebrating Ruby on Rails 1.0!

After much hard work, script.aculo.us 1.5.0 is finally here!

A big thank you to all the contributors out there!

script.aculo.us 1.5.0 final is also a part of the Ruby on Rails 1.0 release, and comes with Prototype 1.4.0 final on board!