TomE Media Shell - HTPC front end
I've been messing with my own front end for an HTPC. Why? There are dozens, but there are some really strange setups out there that are overly restrictive. In some, the plugins can only be written in C. In others, you have to use specific DVD players or media players. In short, most of them suffer from being a core plus plugins with the interchange being a bottleneck. I wondered if, using basic scripting tools, something similar to these systems could be whipped up. If made from things like HTA, web apps, PHP shell scripting and ActivePHP, Winamp COM object, Windows Media Player COM object, etc. it would end up not being core+plugins. Rather, it would pretty much nothing BUT plugins. Screens can be sourced locally on the machine, can pull data or entire screens from remote servers or a blend of approaches.
I'm currently calling it TomE (pronounced Tommy) for This Odd Media Environment as well as short for Thomas Edison (without having to deal with any trademarks on "Edison") since he invented/popularized most of the precursors to the stuff in a Home Theater PC: the light bulb, recorded audio and the motion picture.
HTA is the primary container for the user interface and drives the whole thing. As such, anything that HTA supports is directly available and anything HTA can access (which I've not run into anything it can't) is also wide open. Obviously, basic DHTML/HTML/Javascript/CSS is supported, as is Flash and any other plugins you have, PHP directly using the ActiveScript extension from PECL, all of the IE-only stuff we avoid in normal site development like powerpoint-style transitions and HTC components are open as well. As my particular niche has always seemed to be gluing things together, this approach fits very well with my way of thinking and things flow well.
I picked up a bunch of icons from kde-look.org, which has quite a bit of really nice vector-based (SVG,etc.) icons and wallpapers which give you nice smooth exports to PNG for whatever size you want. Had to use one of the available PNG alpha transparency scripts to enable that, but once enabled, it makes for a much better framework for theming (I hate calling that "skinning". Coming from a taxidermist family, skinning has some different connotations for me) while still retaining the same look and feel. Should work well for being able to have multiple color schemes for the same theme.
It's pretty much a pile of prototypes right now, but I'm really happy with how it's turning out. These technologies glue together really easily and allow me to leverage existing web development technology experience and built-up components, thus speeding the glueing process.
Photo screen:

This screen is a mockup of a basic image gallery. It uses PHPThumb to build both the web images and the thumbnails without modifying the original source directory or files. Currently requires local (or at least network share) access to the images.
Weather screen:

This one is more complete and is actually fully functional. I had some code and notes lying around for building a weather web page anyway as XML based weather fetching has interested me for some time. So, stringing that together into the TomE framework made sense as a test-case. It really went together easily. It still needs some better setup for handling more of a range of weather, but I'll add that as the weather changes with the seasons. It gets it's data from RSSWeather.com, which is a relatively new service. It's easier to parse/read than the stuff from NOAA/the weather service, but not as complete.
