When you've got a lot of screen real estate to work with like a T4, what do you do with multi-functional components? Do you put both functions on the same screen or do you seperate the functions into two seperate screens?

I've been tweaking out a template for Xbox Elite with Xbox HD-DVD player. I can get all of the remote functions on one page, but I am struggling with the simplicity of it. If you're a user and you just want to use the DVD would it be ideal to have a seperate screen for the DVD setup and controls?

I would have to say so.

The temptation is that the larger the screen, the more you put on it. Also, you may not want to give any tweek control on a primary page so that someone does not change something that could cause a potential service call.

I find that most clients are not that saavy and can get easily confused by too many options. For example, when applicable, I will build a separate page for DVD audio for systems without a dedicated CD player (when using an Escient or other server) that only shows the required buttons for listening to a CD via the DVD player.

This is exactly why the best touch screen remote, in my experience, was the Marantz RC5200. It had a nice large screen but it had, in real buttons, a full cursor pad, M for Menu, and enter button. The later versions did the same but used some kind of graphic that looked like it the lettering on the Stargate portals, so people could not so easily remember how to use the buttons.

Anyway, my goals would be to
allow the client to have all regular functions on one screen only
not even put on the remote those buttons that could get them in trouble, say, EJECT on a DVD player. Maybe the ( - ) on a DVR so they couldn't reset without searching out the factory remote; no accidents there!
The most separate possible functions that come to mind are DVD and VCR of a combo unit. I would have those as separate devices on a remote!

Yes, the larger the screen, the more you can put in. Just remember that the less you put in, a)the less a user can be confused and b)the larger the buttons can be for us old folks.

To me the larger the screen the bigger the buttons can be with more spacing in between! On most of my T4's I use backgrounds that are more personal, one of my clients is a car guy so I had a couple pics of his cars as backgrounds. I would always have it as simple as possible. XBox game controls on one page and the HD DVD drive on another.

I agree with the above.

You want to keep related functions to one screen. You might even have multiple pages for a given device. For example I did a T4 that had an Audio request. The functions of the request are broken down into three pages.

Just becuase the screen is bigger you don't want to cram it all on to one screen. You now have more spacing and the buttons can be larger to its easier to navigate and control. With a remote like a T4, many customers want to stay using the touch screen interface and don't want to have to deal with the hard buttons. Therefore you will be putting more functions on a screen anyway, which takes up real estate.

The less on a touch screen the better. Use large buttons that are clearly labeled and ask the end user how they plan on using the remote. Most of my customers find that the gewiz factor of a large touch screen wares off fast if they are channel surfers that have to look at the screen every time they want to change the channel, or press the previous channel button. But if they are the turn it on and do not touch the remote again type then they may like the big touch screen better.

When talking to your client, make sure to include the spouse in the conversation. Many times in my discussions with the client, I realize that the person giving me the answers is making things more complicated than they need to be. Make sure to include the least tech savvy spouse in the decision making process. It is not uncommon for that person to make your life hell after you think you are done.

One thing many designers overlook is how many buttons you have to press to go from point A to B. Nothing should ever be more than 3 button presses, and common functions like turning on a system and selecting a source should be one button press. Having a welcome screen that you have to exit to select a source is a useless indulgence that may be pretty but quickly becomes a hindrance.

The rule is keep it simple and efficient, and then make it look pretty but form should follow function, no matter what the interior designer says.

i keep it as simple as possible, and only put n basic comands, unless they tell me otherwise. Even then I hesitate a little bit unless i fully trust that the client knows what they are doing