www.codinghillbilly.com   kyle.baley.org  Subscribe / Contact
 
 
 
 
LATEST POSTS
Thursday, November 23, 2006

Looking through the features of Windows Media Player 11, one might think that they have something against Hillbillies. Firstly, they appear to have made playlist management much more intuitive. Or at least they claim to on the website. I haven't actually played with any of the new features yet.

This kind of reduces the impact of what I had planned for Flamingo, which was to have playlists as sort of a combination of saved searchs, not a static list of songs. That way, you could add songs by artists you like and not have to redo your playlist.

If it were just that, though, it wouldn't be too big a deal. Especially given that I'm not pursuing any sort of commercial venture with this. The problem is, not only has WMP 11 undermined my efforts with features that are six versions too late, it also completely changes how Flamingo currently works.

With WMP 10, you would select a bunch of songs, click Play, and that list of songs would appear in the Now Playing list. With WMP 11, instead of a list of songs in the Now Playing list, you get a single entry that says Default.

The songs still play, mind you. But you can't see which ones you've selected, nor can you select a song on your own. You can only navigate forward and back through the list without knowing what you'll hit next.

It is because of this exact deficiency with the Hillbaley Radio (built using Windows Media Services) that I started Flamingo in the first place (at the request of a friend who wanted the ability to "filter out the crap" when listening to my library). So now I'm back to square one. Except that it took much, much longer to build software that doesn't work any better than what Media Services does out of the box.

The issue with WMP 11 is that it wraps the playlist I generate in another playlist. What Flamingo does is generates an XML file in .wpl format and serves it up in a response, relying on WMP to interpret it and do its thing. But rather than simple interpreting the .wpl file as-is, the way WMP 10 does, WMP 11 creates another .wpl file of its own with a single entry called Default. That entry is a reference the temporary .wpl file Flamingo serves up.

The net result is that you are now listening to a playlist that references another playlist, not a playlist that references a bunch of songs.

Most inconvenient.

Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

Copyright © 2010 Kyle Baley. All rights reserved.
 
CATEGORIES
.NET General (18) alt.net (4) altnetconf (9) ASP.NET AJAX (40) ASP.NET MVC (29) Bahamas (1) Bahanet (9) BDD (1) Brownfield (21) Career (10) Castle (1) Code coverage (1) Code review (2) Coding Style (6) Communication (1) Community (18) Conscientious Coding (35) Continuous Integration (11) dasBlog (12) Development (16) DevTeach (4) Domain (2) Environment (4) Estimating (1) Featured (14) Flamingo (10) Games (1) Google App Engine (3) GWT (9) Hardware (6) Java (2) Javascript (7) Linq (2) Livelink (6) Lucene.NET (2) MbUnit (1) Metrics (2) Miscellaneous (25) Mocking (4) NAnt (4) NHibernate (12) NInject (1) Office (3) Office Development (6) Open Rasta (1) Patterns (6) Presenting (14) Professional Development (15) Refactoring (10) ReSharper (11) REST (3) S#arp Architecture (5) Security (3) Software (11) Sundry (19) TDD (19) Tools (22) User Interface (6) Utilities (9) Visual Studio (8) VSTO (1) Web development (12) Windows (3) Working Remotely (17) Workplace (3) Writing (6)
 
LATEST POSTS
 
POPULAR POSTS
 
 
ARCHIVE