An update to David Shaw's Midnite PCF. The buttons are mostly from his PCF. I have included additional buttons for my devices, and included a bunch of DVD covers for my DVD jukebox. All devices have discrete power. I have also setup this PCF to use PIP with both my satellite and cable connections.

Building upon Daniel Tonks' graphics and overall design, with some design elements from David Shaw (a few graphics) and Jon Linville (his clean screen program is effective, as well as his pre-made DVD macros which I used for my DVD changer). I have made the PCF very user - and wife - friendly, and easy to code with a dedicated section for IR codes and macros.

A mixture of quite a few pre-existing templates, plus some new stuff. Graphics taken from Daniel Tonks' template.

A simple design where you can switch to any device at any time.

This clean and simple design was based mainly on "OS X" graphics, device images from "Daniel's TSU3000" together with some of my own images. System begins on the "power" page where you can turn on/off TV, home theater (DVD) & cable with one button, go the the "lighting" page or go the specific device power controls. Across each page are shortcuts to "power", "DVD", "cable", "TV", "lights", "surf" and "activities". "Surf" includes 9 pages classifying channels into favorites, nets, learn, fun, news, sports and music.

This PCF template follows the Tonks standard, with his graphics (and a few others) linked to the IR codes located under a hidden "CODES" tab. I have a fairly simple setup - only 5 devices, with some macros used for the TV where discretes wern't available. Please note that I use the hard buttons for channel up/down, volume up/down, and mute - so these commands do NOT show up on the graphics screens. I have rearranged several of the layouts to get as much functionality on each primary screen as possible - some of the buttons are a little smaller than I'd like, but work well when controlled by a fingernail OR one of the small plastic styluses found with any of today's touch-screen PDAs (Palm, HP, etc). There are a few less-than obvious connections - using the page markers - to get to some hidden pages I wanted access to, but not obvious for the kids (raw codes pages, and other debugging stuff). Have fun!

This is a revision of my previously submitted file. It makes better use of graphic icons for buttons and cleans up some inconsistencies in my previous upload. The principal design objective here was to make the screen as legible as possible given the rather dim nature of the TSU3000. I have been testing various screen icons and layouts on several people and feel that older users find it easier to use this schema than the more elegant 3D designs. Another objective was to make use the hard buttons: the row of buttons under the screen is used exclusively for navigating between screens.

This is my first configuration. I did not use any graphical elements from the Daniel Tonks remote that I'm aware of. Don't get me wrong, it's a nice remote but I wanted to try to create something original. My graphics may look dark but they have to be to show up on the TSU3000 (i.e they're not that dark on the remote). Like many of the configurations here, I created a hidden page of codes for every device then linked the buttons to the code pages. I learned the codes for every button on every remote that pertained to the device regardless of whether or not I intended to use it in my design. I thought that if by chance I had a remote that someone was looking for that they might appreciate having the entire remote. Most of my devices have two or three GUI pages. At the top are tabs with devices related to each other. The white tab indicates the current page and the dark tabs are buttons to switch to the other devices. On the left side of each screen is a block of common buttons that carry over to each page. In the middle is a graphic that I created and what I would consider rather large, simple buttons that are easy for me to press. See the readme.txt file for more details.

This configuration is almost completely based on the pioneering work of Mr. Tonks -- thank you. It does, however, contain a couple new twists (and, of course my devices). It includes an activites based approach for the non-initiated (grandma, babysitters) and a device based interface for others. Both interfaces can be used interchangably, and take full advantage of the hard buttons. I've tried to keep it simple by limiting each activity and each device to only one page of the key buttons, which I've found to be effective for about 99% of the collective functionality of 6+ remotes.

I have finally produced what I think is great design. Logical layout for the programmer with seperate screens for IR codes and user functions. Simply navigation for the family with the hard keys tied to most used features and bottom buttons for home and FIX buttons that toggle video and audio inputs/outputs. Nice graphics (with a little help from guistuff) that really use the full palette available.