Mute tickets
This week I’ve been going trough CatWalk’s tickets slated for the TurboGears 0.9 release.
Some of the issues resolved are:
- hitting return in edit or add view generates an error
- adding support for accesskeys for save and cancel
- load default values in the add view
- implement support for inheritance
- deal with ForeignKeys which default to none
- when deleting an instance delete any related join the instance had
Closing tickets it’s by itself a gratifying experience, but could sound improve this?
I love Mail.app’s swoosh sound when a mail had been send.
Or Finder’s paper crunching when the trash had been emptied.
High-end car makers spend time designing the sound of a closing door and
the iPod’s tine speaker inside solely purpose is to give that reassuring clicking feedback
when you scroll the wheel.
But web app’s are all mute- at least the ones I use and know.
Is silence a proactive design choice or just something we don’t take into account (yet) when crafting the
user experience?
November 16th, 2005 at 11:51 pm
That’s an interesting notion there. Should we be playing little sounds to enhance the user experience? OS’s do it, apps within those OS’s use the OS sounds… why not web apps.
I wonder if there is a reliable way to play sounds via a web app when, say, a button is clicked or a tick box is ticked, or an option saved.
/me goes to ponder
November 17th, 2005 at 1:53 pm
I’ve been casually looking into this for a project I’m working on. There seems to be a couple javascript libraries that rely on an integrated flash object to play sound. Unfortunately, most of the demo pages are very unreliable on all the mac browsers I’ve tested.