Tablet interface required #13
Comments
|
Yes, a tablet interface should be made. I personally don't have a tablet and haven't look into this yet. Although, I have been looking into getting one so who knows this might happen soon. |
|
If you would like any help with mock ups or testing, I would be happy to help you out. Let me know |
|
I think I will do the fancy different views on landscape and portrait. Like when you click a show, the episodes will be shown next to it. If you click an episode, then it would be displayed next to it. Feel free to shoot ideas for interfaces around for SickStache or even CouchTatertot (if you use that). |
|
I made a mock-up of what it could look like on the Nexus 10. Let me know what you think! The ROM is Paranoid Android, hence no top notification bar, however that wouldn't make any difference as it would just move the app down a few pixels should it be running stock |
|
That looks sweet. Think it would work with 3 panes? The only reason I ask is because I would have to A) Get the season info and every episodes info before it would pop up I want B but B is really really hard to pull off. A has the down side of using a lot of data. Ironically, I probably could have fixed some of this with sync adapters lol. Damn. |
|
You could probably squeeze it into 3 columns, you just wouldn't have the breathing room either side - Also it would need a completely different layout for portrait mode and not sure if 3 columns could be easy to use on a Nexus 7. Can't you just do B anyway but on click, load the info as it expands down? If you were doing it in Javascript for instance, you could just have a function to load the episode information into the container when a episode header is pressed - hence saving on data. |
|
Well there is kind of problems with both ideas. A) There is no clean way to say get all episode information (you can us the advanced api but then again for shows like "The Daily Show with John Stewart" that is almost 2000 episodes. That's a lot of information to send and receive. B) Well, I really would like this one but I need to explain how android ListViews work. A ListView could contain thousands of items. We cannot store all of the views in memory. So, they recycle the views that you scroll past and reuse them. This makes asynchronous activity ... challenging. Its not impossible, its just harder. Now, I was thinking that I could skirt around this issue by using the episode name header and the information as one view and hiding the info until the click. This would remove a "layer" of the expanded list view. This way when you click. I could go out online and get the info. When I come back, add the new information to the data store. Then, check if the view is still on screen; update if it is. Otherwise in the code to display a header, check its click state and display as needed. |
|
I'm currently working on CouchTatertot patch (It needs it way more) but after that I should get to this. If you want, I still have a lot to do with CouchTatertot. If you can come up with a good mockup for that, I might just be able to include it with that patch. It needs work for both Tablets and Phones :( |
|
Are you on Google + or any other way of talking besides this public place?
|
|
ok i can finally work on this. Its going to be slow, but hopefully ill get it done. |
Haven't found any actual bugs however I think a tablet interface if definitely required.
The shows screen is fine on my nexus 10, however where there is any text used' it is far too small to read and click on. I can only assume it isn't scaling correctly
The text was updated successfully, but these errors were encountered: