Backpack, the simple web-based manager of to-dos, notes, ideas, and schedules from 37 Signals, has had an upgrade.
The team discussed some of the changes, and the biggest addition is the ability to move any “widget” (note, to-do list, picture gallery, etc.) anywhere on the page, or even to another page.
We talked to Sam Stephenson, also of Prototype acclaim, to get his thoughts on the changes, and what we may see in Prototype and Script.aculo.us coming out of this practical work. He gave us some detailed thoughts:
Sam on Backpack
Under the hood, Backpack’s Pages tab has been completely rewritten. We moved nearly all of the application’s UI logic out of hand-written JavaScript files and into Ruby using RJS templates. This resulted in approximately 1600 fewer lines of application JS, and let us deliver pages with substantially less markup, since the edit states are now loaded on-demand instead of included in bulk with each page load. In addition, we’re running Backpack on the latest versions of Rails, Prototype, and script.aculo.us from SVN.
Most of the custom JavaScript in the new Backpack is used for wiring the interface in reusable ways. We’ve built a handful of mini-libraries that sit on top of Prototype and script.aculo.us, and we’re using them in several of our other applications in addition to Backpack.
One of these libraries adds support for specifying a CSS selector for script.aculo.us Sortable containment. It uses Prototype 1.6’s new Function#wrap to add the behavior in an aspect-oriented way without modifying the original Sortable source code. This is the library that powers Backpack’s widget reordering. It’s currently being used in Backpack and Basecamp.
Another library, internally called Hover Observer, uses an unobtrusive technique (monitoring the entire page for mouse movement) to add and remove a “hover” class on element hierarchies with certain class names. Combined with CSS, this allows us to easily show the edit/delete/move “nubbins” when you mouse over widgets on the page, or show drop-down menus when you mouse over applications in Open Bar.
The library also lets us specify enter and exit delays, so if you accidentally mouse outside of a target area, the hover class isn’t removed immediately. Think of it as a cross-browser implementation of the :hover CSS pseudo-class, on steroids. Hover Observer was developed for Backpack and is now being used in Basecamp and Highrise.
The last library is tentatively known as Transitions, and provides an extremely simple API for animating transitions between DOM states. I’m planning on releasing this library soon, so I’d appreciate it if you didn’t blog the details just yet, but here’s a preview:
The animation resizes and fades an element’s content from one state to another, much like the effect you see when switching preference panes in OS X System Preferences. Because the API is simple, RJS-compatible, and easy to integrate into existing applications, we were able to develop it and drop it into Backpack in a single weekend.
Edit any item in the new Backpack and you’ll see the transition - look closely, though, because it’s so fluid you might just miss it 
An example of the API:
JAVASCRIPT:
-
-
$(”element”).transition(function() {
-
// Modify $("element") or any of its children in this callback.
-
$(”element”).addClassName(”editing”);
-
$(”element”).down(”.container”).replace(”…”);
-
$(”element”).down(”h2″).hide();
-
})
-
Or, in RJS:
RUBY:
page[:element].transition do |p|
p[:element].add_class_name("editing")
p[:element].down(".container").replace(:partial => "…")
p[:element].down("h2").hide
end
So you basically only need to wrap your existing JavaScript in a transition() call. transition() clones the element you call it on, wraps it in several anonymous elements, resizes it appropriately, invokes your callback, and finally fades out the cloned element while fading in the new element and resizing the container to fit its dimensions. Transitions takes care of all the dirty wiring, and lets you focus on the “before” and “after” states of the DOM.
I’m extremely pleased with how everything turned out, and I’m looking forward to open-sourcing as much of our JavaScript infrastructure as possible in
the very near future. If you have a Backpack account, I hope you’re pleased with the changes, too.
Source: Ajaxian
Original Article: http://feeds.feedburner.com/~r/ajaxian/~3/139988190/stuffing-more-ajax-in-the-backpack
Anywhere.fm has launched a new online music player that looks and feels a lot like a web based version of the iTunes player, sans the music marketplace. Like iTunes, you can load maintain a music library, reorganize your songs into play lists, and veg out to visualizations. Anywhere.fm’s iTunes bulk uploader makes it easy to get up and running with your existing library.
