search

trdlo / client175

Automatically exported from code.google.com/p/client175
GNU General Public License v3.0
0 stars 0 forks source link

iPad browser issues #41

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Let me start by saying this UI amazed me when I found it.  Surprised what can 
be done in a browser.

Now I appreciate you didn't design this for an iPad but the beauty of having a 
PC connected to the sound system and having a "wife friendly" way of 
controlling it is a killer app in my house.  Not sure how you could make money 
from this on the Apple App store but the other MPD version for iPad is a few $.

The following are issues running on an iPad with iOS 5.0.1.  My MPD database 
has about 44,000 tracks so there is a good data set to work on.

Volume slider - if I press and hold on the volume slider then drag the screen 
will drag not the slider.  I can click on a place on the slider to get it to 
move but that is rather hard due to the size.  Not sure if you have any control 
over this slide control, not sure of the alternatives.

When I use the search in the top right for say "Garfunkel" it displays the 
results in the centre pain as expected.  The problem is that I cannot double 
click to expand "Simon & Garfunkel", the act of double tapping cause the screen 
to expand.  Would it be possible to have an "expand" icon on this line to 
achieve the same thing?

There is no way to move the bars that create the 3 separate panes.  This is not 
a problem because it sizes correctly in the first place and the hide & expand 
buttons work well on the left pane.

I got strange results using the "Artist / Albums" > "Minimum 10 songs" items.  
I got the animation, a pause and no data.  I am guessing that as I have a lot 
of data and a slow device that this timed out gracefully.  Again not sure if 
there is any way to tune this.

When I use the expand gesture to zoom the screen collapses and the layout goes 
all wrong.  If I pinch it back to normal size it springs back to normal and 
works fine again.

I also tried this on my Android phone and the same sort of results (but the 
screen is too small).

Original issue reported on code.google.com by mat.lud...@s4apps.com on 21 May 2012 at 8:42