Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I actually wrote the code mentioned by Airsource Ltd at <a href="http://forums.macrumors.com/showthread.php?t=532573" rel="nofollow noreferrer">http://forums.macrumors.com/showthread.php?t=532573</a>, so pointing me to my own code wasn't much help, thx anyway, my fault, but hey, who doesn't use different screennames on different forums? ;-)</p> <p>Anyway, it was approved after submission to the appstore, and IMHO it is very useful when dealing with long lists. Paging is something commonly used on the web, and I wouldn't like to force a user to scroll down/up a list with 500+ (did I say 500+? what about 1000+?) rows.</p> <p>I agree that a horizontal swipe on a list should/will enable the user to delete/edit a row as a default behaviour. But isn't that context-specific? </p> <p>If I as a user am the "owner" of the data, I would expect to be able to delete rows. But would I expect to be able to delete rows in a list of apps in the AppStore, or a list of books in an Amazon app? </p> <p>A horizontal swipe on a list is just a gesture, depending on the context, it should do what the user would expect. </p> <p>Given the scenario of a list with 500+ rows, what would you do? Show the first 25 rows with a "Show me more"-Footer? -> then you'd have 50 Rows? and so on? in the end, you'd have 527 rows? Unless you go hardcore-drawing you cell, the table will draw choppy too on top of it. But even if scrolling smoothly, this wouldn't resolve the problem of scrolling up/down 2000 miles of pixels.</p> <p>Or put a Header/Footer with "Previous Page / Next Page" - Buttons, thus only showing 25 rows at a time? You'd then force the user to scroll to the top or bottom to switch to the previous or next page....</p> <p>I'm open for any suggestions. It appears just as a natural gesture to me to swipe left or right on something that has a "previous/next" something.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload