All the Media View developer needs to do is create an icon file.  It must be 22×80, with all four 22×20 states (normal, hover, active, and disabled) vertically stacked in it.  Here’s a sample one I created for John M’s excellent Grid View:

All that’s left is to point to it inside the Media View’s install.rdf file.  In the same <songbird:mediaPage> section we simply define a new <songbird:contentIcon> value, like so:

<songbird:mediaPage>
   <Description>
        <songbird:contentIcon>chrome://gridview/skin/mpIcon.png</songbird:contentIcon>
        <songbird:contentTitle>Grid View</songbird:contentTitle>
        <songbird:contentUrl>chrome://gridview/content/media-page.xul</songbird:contentUrl>
    </Description>
</songbird:mediaPage>

That’s all there is to it!

I just committed an encoding fix for Songbird’s Concerts add-on that, starting with tonight’s nightlies on trunk, should mean you start seeing some updated European countries in the available locations list.  The new countries include Denmark, Finland, France, Germany, Netherlands, Norway, Spain, and Sweden.

While the concert data is now being included, not all localisations are up to date.  Notably, out of that list, we’re missing the Danish, Finnish, Dutch, and Norwegian localisations entirely.  The Swedish localisation just needs a few more strings translated.

If you’d like to help out and see the full localised Concerts add-on in all its glory, please go register with Babelzilla.org and help translate the Concerts add-on here.

As you know we’re big believers in openness and as such we try to share our development plans and progress with you as regularly and freely as we can. This isn’t as straightforward when other companies are involved — especially large, global, public companies like Philips. So we apologise for not being able to talk openly, sooner, about this new relationship but we hope, even as a bit of a surprise, you can appreciate why this is a good thing for the company, the products, the platform, and all of our users. As always we’ll strive to give you an early heads up whenever we can.

While there’s obviously some special work we’ll do for Philips, we don’t think about this as one-off work.  Much of what we do for them, is work we’ve been planning  to do for all Songbird consumers.  For Philips, there’s certainly a custom feather and the add-ons that are important to them and their customers. We’re working to make sure that all of what we build is valueable for you and for partners … with as few exceptions as possible.

Our partnership with Philips is a great step for us — it drives distribution, revenue, and an even tighter connection to the CE side of the world. Of course the partnership means more features to consider and tradeoffs to balance – but in this case, that’s a great problem to have.  There is lots of overlap in desired features from both sides, so this probably means you’ll see some things accelerated, which is good news for all Songbird consumers. We know that users around the globe using the software and sending us their ideas ultimately results in a better experience for everyone. So keep your suggestions coming.

There’s no resting on this week’s milestone achievement, we’re working fast and furiously on the next release, which will hit early this year. Stay tuned for more as we move continue evolving plans and working through development.

Thanks again for all of your support!

we’ve been following the blog comments, reading the bug reports, and getting the feedback from GetSatisfaction bubbled up to us via our intrepid Songbird Champs.  there have been a few recurring issues worth mentioning/recapping, so here we go in no particular order:

1. Windows 7 Support
   • Yes, we throw a warning message up when you’re installing Songbird regarding it being unsupported on Windows 7.  This is mostly a “caveat emptor” warning, we haven’t done full and proper QA test runs to ensure things work on Windows 7.  That being said, we have plenty of users who run it just fine on Windows 7.  If you do continue to install and run it on Windows 7, you may experience bugs.  We’re working on full and proper Windows 7 support for the next release if you want to wait.
2. iPod Support
   • As mentioned previously, we are no longer maintaining the iPod Extension.  Continually playing an unsupported game of catchup with Apple sucked, and we’ve opted to go with iTunes Import/Export Syncing as our supported way of having users sync their music libraries with Songbird.  As mentioned in that blog post, we’ve open sourced the iPod Extension (which is built on libgpod), and would happily welcome any community patches to it.
3. Splash Screen
   • Yeah, we get it.  Some of you don’t like the splash screen.  Unfortunately it does, believe it or not, serve a purpose.  Not everyone has the super-latest-OMFG-ITS-1BILLION-TERAHERTZ machine… and especially on some platforms (Windows XP for instance), there was no feedback as to when the application was starting.  If you really really really hate the splash screen that much, then go grab Simon’s splish splosh extension to easily change or disable the splash screen.
4. Bookmarks
   • Over the next few releases you’ll see us phase out some of the more web browser specific features.  This is a conscious design decision to differentiate Songbird as more of a media player than a web browser.  Let’s face it, we’ll never be a better web browser than Firefox, Safari, or Chrome.  We’ve never intended for Songbird to replace your daily web browser.  Don’t take this to mean we’re removing the web browser component entirely… we can’t, and we won’t since we use this for rendering things like the Last.fm Radio Directory, the 7Digital Music Store, the Concerts Listings page, etc.  It just means we’d prefer for add-ons to take a more integrated approach along the lines of the 7Digital, Concerts, SHOUTcast, & Last.fm add-ons where servicepane nodes are displayed that link to custom chrome (or heck even to webpages tailored specifically for Songbird, such as the 7Digital store).
   • That being said, if you really really really want your bookmarks back, I’ve made a Songbird Bookmarks extension that re-enables the bookmarks servicepane node so you can get your old bookmarks back.
5. Automatic Album Art Fetching
   • One of the new features in Songbird 1.4.3 is automatic album art fetching.  Depending on what mode you have album art in (either “Now Playing” or “Now Selected”), album art will be automatically fetched for the currently playing or selected track.  If you’re on a slow or high latency connection (and this can vary depending on your album art fetcher add-ons and priorities, set via the Album Art preferences), you may experience a lag when selecting or playing tracks as Songbird goes to fetch the album art.  We’ll work on improving the performance of this in the future, but for now – I’ve made an extension to allow you disable or enable this automatic fetching behaviour.

In other news, I’ve managed to raise $2320 so far!  Only $680 left to go to meet my goal of raising $3000 for the San Francisco AIDS Foundation.  Surely one of your New Years’ resolutions was to donate to stevel’s 545 mile bike ride from SF to LA, right?  If not, hopefully one of your resolutions involved donating to charity?    In any case, if you haven’t donated yet, I (and the SF AIDS Foundation) would really appreciate your donation and support…

• A few bugs caught by awesome Songbird users found in the beta release we pushed on Wednesday
• An office mouse infestation Ali discovered

Mice! Oh my!

We’re planning to push our next public release of Songbird (1.4.1) next week, and wanted to give you a quick rundown of what’s new for the release and what changes you’ll need to make in order to bring your extensions and Feathers up to date for 1.4.1.  The major change is a brand new Feather called Purple Rain.  One of the consistent pieces of feedback we had regarding Gonzo was that there was a lot of confusion between the concepts of collapsing/expanding (using the splitter/grippy) a display pane vs. showing/hiding (using the buttons).  We’ve done away with the concept of showing/hiding, and moved to large more obvious splitters.  Users were also having trouble with the small display pane header buttons/tabs (used in Album Art, mashTape, etc.) so we’ve changed that functionality as well.

For extension developers, this means if you’ve previously utilised the display pane header navigation elements, you’ll need to change to our new model which uses sub-menus available via the display pane add-on picker/drop-down menu.  The good news is it’s fairly straightforward, and is super extensible to allow your extension to create entirely unlimited sub-menus/menuitems.  We’ve got this all detailed in our Extension Update Guide for Songbird 1.4.1 available on the developer wiki.

For Featherers, things are somewhat more involved.  We listened to a lot of the usability feedback we got from our users.. so on the plus side, we think the Feather is much more straight-forward and obvious to use for new users.  The downside is it’s a fairly major update to get your Feather working.  You’ll want to take a look at our Feathers Update Guide for Songbird 1.4.1 to get all the salient details.  The easiest thing to do is to startup the Feathers Creation wizard and create a new Purple Rain based Feather to get all the layout and widget changes, and then pull any existing images.  If you’re trying to migrate a Gonzo based Feather, keep in mind a lot of dimension sizes have changed, so your graphics probably won’t drop in one for one.  It may be possible (though untested) to keep your Gonzo based Feather, and just update the CSS with the changes done in Purple Rain, and then create new images for the new elements (such as the new Media Views and display pane images).  If you’re having trouble with updating Feathers, please drop by our songbird-dev Google Group for more info and some help!

(many many thanks to Michael Purses, one of Songbird GetSatisfaction champs for pitching in this weekend to help put together the Feathers Update Guide)

We’re getting ready to ship Kanye, KoЯn, Songbird 1.4.1.  (so tempted to call it Kandy-Koated Kanye Korn after one of kreeger’s favourite candies)… due to some mishaps with the translate webapp, we weren’t able to get the new strings showing up on the site until yesterday.  Thankfully there aren’t many (<30), so we’re hoping our localisation community out there can dig in and help us plow through the remaining untranslated strings so we’ll have a multi-lingual bird ready for next week’s release.

Apologies for getting it resolved so late, we would definitely have liked to have had more time for localisers to finish working on the strings… but we really do appreciate everyone’s time and effort they put into these localisations for us.

If you’re interested in localising, and aren’t already on the songbird-l10n Google Group, go sign up!  It’s what we use for help and coordination among localisers.

What does this mean? If you’re looking to pull and build your own, make sure you pull the Songbird1.4 branch. If you’re just looking for nightlies, make sure you grab them from the Songbird1.4 branch as well.

Again, just want to say thanks and a huge shout-out to the Mozilla Europe gang.  They put on a great event.  One of the most socially inviting and warm conferences I’ve been to.