[mythtv] [mythtv-commits] Ticket #8805: Source->Switch Source missing

[Stuart Morgan]

On Wednesday 15 Sep 2010 14:37:56 Kevin Kuphal wrote:
> > *shrug* My first choice would be to just map it to some other key,
> > but it's more because I think most users will be looking for "Switch
> > Source" whether they know it or not and may find Switch Input instead.
> > Then they will file bug reports demanding Switch Input be rewritten
> > to function like Switch Source (why is my DVB card showing up eight
> > times and crowding my other cards off the menu?!?!) But there are
> > other solutions to the problem. We could for instance move things
> > like Switch Input to a Developer sub-menu, or we could simply rename
> > it to something more opaque. For this one feature I don't care. But
> > since we have a goal of simplifying the UI, how we handle it
> > should probably fit within some greater plan.
> 
> I'm not sure what the negative is on Switch Input but since Inputs and
> Sources tie together, wouldn't a multi-level menu work?

I think because you're thinking like a power-user or developer and not the 
average user, a significant other, grandparent, young child.

We've all failed to see this from a different perspective in the past, which 
is why the UI and user experience is not what it should be. We're trying to 
change the culture, even at the cost of upsetting a tiny minority of 
technically minded, power-user types.

We want fewer options in menus, more relevant choices, simple language free of 
acronyms and technical jargon, fewer settings and more automation, less 
cluttered screens etc

Take Simon's reason for keeping input switching - a broken/poorly functioning 
card. In other words, input switching is a workaround for problem with his 
hardware. One which might be fixed using input priorities btw. There are 
dozens of settings, menu options and similar which are also there as 
workarounds for bugs, mis-configurations or because it was easier than doing 
it properly.
-- 
Stuart Morgan