There’s always been a significant faction of foobar2000 users whose primary attraction to the player is its appearance, or rather the level of control given to its users over its appearance. In its infancy, with the standard (and still default) UI, very little was possible — the main window consisted solely of a tabbed playlist and several functional toolbars — but people nevertheless took a lot of pride in making it their own, and some impressive things were done with relatively minimal flexibility. It was in the standard UI that users began experimenting with album-level presentation, choosing not to repeat redundantly the artist and album name on each line of the playlist, but to use the second, third, and sometimes fourth lines to display other info, such as year, label, genre, replaygain info, etc. Each of these customizations was unquestionably unique, but most of the broad details of the interface were consistent and inescapable.
The Columns UI component began as an experiment in allowing for multiple columns within the playlist display, emulating the Windows Explorer “Detail” view (and many other Windows programs), with sortability via clickable column headings. Eventually Columns UI added a sidebar and, later, panels, allowing the whole foobar window to be split up indefinitely into panel-based component displays, the playlist viewer becoming just another one of these. This granted much greater flexibility, allowing users to tailor the interface even more precisely to their needs. You could now display album art as prominently as you wanted, or not at all; your entire library tree could be embedded within the main window, rather than tucked away in a pop-up; and with the trackinfo panel’s exceptionally lax (by that era’s standards) stylizations, the personalization of your foobar became even more addictive, and, more importantly, rewarding.
Many seemed hell-bent on concocting the most garish presentations imaginable: giant gothic blue-on-black custom fonts, deep-red 200-px-tall spectrum analyzers, all, of course, coupled with custom OS “vis.”
While some still preferred the purity and elegance of the standard UI, the personalizations made possible by Columns UI were inarguably functional ones, for the most part. Fonts, colors, distribution of panels, and a rudimentary method of text alignment were really as far as you could go. At the core of all the boasted screenshots was a recognizable structure, all slight variations on the theme of playlist+trackinfo+albumlist+albumart. Outside of displaying album art, there was nothing profoundly new that Columns UI allowed you to do — rather, Columns UI gave you more control over how you did what you needed to do.
And yet, many (and in increasing number) seemed hell-bent on concocting the most garish presentations imaginable: giant gothic blue-on-black custom fonts, deep-red 200-px-tall spectrum analyzers, all, of course, coupled with custom OS “vis” and the most tasteless collections of death-/black-/speed-metal slash industrial slash deep house techno. For whatever reason, people are attracted to this, and these screenshots rapidly brought more curious foobar novices into the forums, wanting a “cool” music player of their own.
At the time, these people were not in the majority of new enlistees. Many continued to jump on board for the incomparably robust program that was still very much the heart of the foobar community, despite all the dressing up. The occasional rogue thread would crop up, asking questions that had been answered countless times before; the new user would be chastised, sent to another relevant thread, answered directly, or any combination of the three. These occurrences were perennial but negligible, and besides, they fell into the unspoken hierarchy of usership; it was the role of the foobar sophomores to help these people out, because they had only recently been in a similar position.
Foobar2000 was in a state of relative stasis. Version 0.9, the successor to 0.8.3, was released in early 2006; the set of “essential” core components was more or less firmly established, only waiting to be perfected; users tweaked their interfaces, inching ever closer to an asymptotic UI utopia; things were good.
Two seemingly simple components engendered a monumental shift in the way people thought about foobar.
Eventually, the inflexibility of the trackinfo panel began to bother some people, particularly that each instance of a trackinfo panel was limited to one font and size. A user named terrestrial began developing “Track Info Panel Mod,” which allowed for in-panel font changes, as well as the inclusion of images. It was this last feature, images, where things really began to get off track. The freedom to arbitrarily place any image within the foobar window is almost strictly unfunctional, motivated purely by the desire to make foobar look good. The introduction of this component encouraged a shift in mentality about foobar, producing ever more flashy screenshots, and attracting ever more users seeking eye-candy.
As Track Info Panel Mod evolved and grew in popularity, people craved increasingly more control. The functionality was amended hastily, by sloppy, ad hoc revisions of the bizarre, cumbersome formatting language. Still, it was only one component, it had found a niche, and it kept to itself.
A few months later, terrestrial began development on a second component, “Single Column Playlist” (SCPL). This began as a simple attempt to replace Columns UI’s playlist view, which, ironically, is the one thing that Columns UI was originally created for. Rather than a static grid of multiple columns and rows, terrestrial envisioned a blank canvas, much like Track Info Panel Mod (TIPM), upon which images and track info could be laid with almost total freedom. Additionally, SCPL was able to group playlist items into collapsible albums, introducing the kind of album-level handling that had eluded foobar users for so long.
One got the sense that people were beginning to believe that foobar was TIPM/SCPL.
Meanwhile, TIPM had begun to allow foobar commands to be associated with images, so that images in the panel could act as buttons. This was naturally extended to SCPL, and with that, two seemingly simple components engendered a monumental shift in the way people thought about foobar. TIPM and SCPL dominated huge portions of people’s foobar windows; the album art panel was rejected in favor of placing album art in TIPM and SCPL; statusbars, toolbars, and even titlebars were replaced with button-loaded TIPM panels. And with glassy effects everywhere, huge flame backdrops, and iTunes-like album art reflections, older components began to seem just that — old. An albumlist panel, with its Explorer tree appearance, and separated from the prettier panels by gray bars, was no longer acceptable as part of a seamless, highly stylized UI. Were these configurations functional? In some cases, yes, but largely, no — or rather, function was of a distant, secondary concern.
The effects of this were twofold: first, the forums were flooded with people who had seen these screenshots and wanted a decked-out music player to match their translucent, purple-LED-spangled case mods; second, because of TIPM/SCPL’s convoluted new formatting language, foobar’s already notorious learning curve was pitched to unprecedented new heights. Avatar-less users were everywhere, starting new threads with their first post, asking questions about TIPM/SCPL. These questions belonged in the components’ threads, of course, but one got the sense that people were beginning to believe that foobar was TIPM/SCPL.
Inevitably, TIPM and SCPL were merged into one component, Panels UI, which replaces entirely the Columns UI interface: “Panels UI looks and acts like one large Track Info Mod panel (advanced text positioning, multiple font configurations, displaying images, etc.) that can inside of it host new panels.” Alarmingly, a very recent poll shows that, out of 89 foobar users, 42.7% are using Panels UI. And the threads continue to this day:
- panels UI sort problem (quick question)
- few question [sic] about Panels UI
- how do i make a button that will open the menu? (With foo_ui_panels)
- PanelsUI Coding Questions (Questions I Cannot Find Answers To.….….…)
- and my favorite: please help. panels UI :( (renamed to rocket scientist UI?)
Admittedly, Panels UI is capable of improving foobar’s functionality. If you took the time to develop a real expertise in the formatting language, the look and feel of foobar would be limited only by your imagination. And my suspicion that the graphics-intensive nature of Panels UI places an unjustifiable burden on your system resources has been largely untested (by me). Performance was the reason I got into foobar in the first place, and though I tried Panels UI for a few weeks with mixed results, the more measured, sober approach to foobar development demonstrated by older “essential” components ultimately drew me back to Columns UI, which I am still happily using today.
I do think it would be a wise solution to create a Panels UI section in the foobar forums. These threads are not going away, and never before has a single component spawned so many one-off threads. Unfortunately, the notoriously stubborn forum administrators would never agree to this, as it would violate the even-handedness with which foobar involvement has always been treated — “Why shouldn’t my component have its own forum?”
There is a new blog meant to report foobar news from the forums, but its focus, too, is primarily on Panels UI. But at least its posts are informative and considered, not thoughtless questions from frustrated n00bs, and it does allow and encourage contributions.