Thanks for the replies, Thorsten!
FWIW...my #1 enhancement request is to quickly save the current song info from an Internet radio station
, as mentioned in http://forums.rokulabs.com/viewtopic.php?t=10868
. From a skinning perspective, this could be a SaveSongInfo
action, which appends date/time, title, artist, and album fields to a text file, e.g. /My Documents/VMR_save_song_info.txt. Any file name and location works for me as long as I can find it
I hope this is still on your list. It would be an incredibly useful tool to research and purchase new music that I hear on Internet radio stations.
It would also be nice to have a SetSkin(x)
action, to easily switch between, e.g., a music library UI and a radio station UI. I know, you already provide SetLayout(x), and I could rework my separate skins as layouts. But it feels cleaner to me to put different functional UIs in different skins, and use sublayouts mostly for the size and position of the controls.
A few followup comments on the other items...
1) PlayPlaylist(n) action
for skin elements (mentioned in this thread
If it's not much work I'll add it in the next version.
I'm using the SoundBridge playlist presets instead for now, and one nice benefit is that SB presets save the shuffle state
. Now I have some playlists that always play in the same order (e.g. my News stations), and others that always play in a random order (e.g. my Lounge stations). So if you do implement a PlayPlaylist action, please consider supporting the shuffle state as well. I guess this could be with a second parameter, e.g. PlayPlaylist(n, shuffleFlag), or with a separate action, e.g. PlayPlaylistShuffled(n).
2) Larger scrollbar thumb (e.g. 32px width and min-height) on browse forms for fingers-only control.
That will be in the next version, too (not via skinning but as an application option)
Related to this, it would be great if VisualMR supported D-pad (5-way button) navigation
on PocketPC. This is another way to control the program with your fingers.
On the Browse screens, the left/right buttons could move through large lists one viewport at a time, or through A-Z like the Roku remote, or by sqrt(listLength) items to minimize the number of button presses (at the risk of confusing some users).
On the Now Playing screen, left/right buttons could be Previous/Next, up/down buttons Volume +/- 5, and the center button Pause/Play.
This seems like a good first step toward SmartPhone support, since all SmartPhones have a D-pad.
4) Replace browse form buttons with a toolbar of 32px icons. These would be easier to tap with fingers, and they would fit almost twice as many commands in the same space (e.g., the "Back" and "Now Playing" commands would now fit in this toolbar).
I was thinking about making the whole browse forms skinnable, too. Buit either way it's abit to much work for me at the moment so it'll have to wait.
If/when you do consider this, I suggest limiting the skinnable aspects to just the actions and images for that row of buttons, at least initially. IMO the browse screens do not benefit from free-form skinning like the nowplaying screen, and a fully skinnable form is more difficult to skin... But if that is the easiest thing for you to implement, full skinnability is better than no skinnability.