GUI Improvements

[los93sol]

I know how to modify screens now, but how in HADesigner do I start a new skin with it's own directory and file structure from scratch?  I've gotten familiar with using MySQL Query Browser and the other tools to find my way around a skin, but I don't understand how to just start from scratch in a folder other than Basic.

[tschak909]

Well, I go over this a bit in my first skin screencast, but basically:

* Copy the Basic folder to a new folder, any name.. doesn't matter
* Create a new entry in Skin with your skin's name, and directory, at the very least. Pattern the row after Basic.
* Create any designobj screen overrides you need in Screen_DesignObj, taking into account your new PK_Skin number.

-Thom

[los93sol]

I hate to beat a dead horse with a stick, but I really think two skins need to be created that match, one for orbiter devices optimized for touch screen devices, and one for media directors optimized for remote, keyboard, and gyro navigation.  It seems silly to have overly huge buttons and fonts on my media director when surely nobody has or is using their TV as a touch screen, getting up to walk to the tv to change the volume, etc.  Am I misunderstanding something or has this just not been completed yet.  I understand the fallthrough system for different devices in HAD and agree that it should be used when dealing with touch screens, but don't understand why the media directors don't have their own UI to opimize them.

[tschak909]

Not going to repeat myself.

You've already answered this question in your post.

-Thom

[totallymaxed]

I hate to beat a dead horse with a stick, but I really think two skins need to be created that match, one for orbiter devices optimized for touch screen devices, and one for media directors optimized for remote, keyboard, and gyro navigation.  It seems silly to have overly huge buttons and fonts on my media director when surely nobody has or is using their TV as a touch screen, getting up to walk to the tv to change the volume, etc.  Am I misunderstanding something or has this just not been completed yet.  I understand the fallthrough system for different devices in HAD and agree that it should be used when dealing with touch screens, but don't understand why the media directors don't have their own UI to opimize them.

We use ASUS Eee Top's in UI1 as 'kitchen top' or wall mounted touchscreens - everyone I have shown one of these too loves them. Using the UI1 Orbiter like this on a touchscreen makes you realise how good this UI really is... the touchscreen is what it was made for. Same goes for Tschak's WebDT Orbiter to of course....

Andrew

[colinjones]

I hate to beat a dead horse with a stick, but I really think two skins need to be created that match, one for orbiter devices optimized for touch screen devices, and one for media directors optimized for remote, keyboard, and gyro navigation.  It seems silly to have overly huge buttons and fonts on my media director when surely nobody has or is using their TV as a touch screen, getting up to walk to the tv to change the volume, etc.  Am I misunderstanding something or has this just not been completed yet.  I understand the fallthrough system for different devices in HAD and agree that it should be used when dealing with touch screens, but don't understand why the media directors don't have their own UI to opimize them.

We use ASUS Eee Top's in UI1 as 'kitchen top' or wall mounted touchscreens - everyone I have shown one of these too loves them. Using the UI1 Orbiter like this on a touchscreen makes you realise how good this UI really is... the touchscreen is what it was made for. Same goes for Tschak's WebDT Orbiter to of course....

Andrew

Andrew - what kind of price do you pay for them (or rather resell them for)? Trying to see what is a reasonable price locally in Aus...