IOS UI Development: Selector Screen Design Approach

Question

I am looking to create a document “selector” screen similar to the pages and numbers on an iPad / iPhone:

I come from WPF background and have some experience with iOS. In doing so, I'm looking for a good approach to creating something like a tile-based interface that Apple uses to open documents on pages.

I am not related to folder animation.

What is the best approach to creating only a tile interface? I would suggest that I build some kind of view that is inside the UIScrollView , but this is the nature of this sub-view, which I'm a little confused about. Does iOS have any control panel or grid-like elements, could I load a set of elements (e.g. documents) into?

What do you guys think?

Answer 1

I do not know of any third-party classes to handle this for you, but there may be some of them.

The main structure will be a UIScrollView containing a set of views, each of which represents one cell in the grid. You set the scroll view contentSize based on the total number of fragments. Then you create tile views on demand and place them inside the scroll view.

The delegate object of the scroll view will be responsible for controlling the scroll position, removing visible tile views when they become visible, and (optionally) removing tile views that come out of view. This basically works with UITableView: at any given time there are only about six instances of UITableViewCell, they are processed when scrolling up and down the view. (Imagine a train in which someone behind picks up the rails and passes them to someone in front, laying them in front of the train. As far as the train knows, the rails go for miles.)

If you have to post all the views yourself, take the time to explore the CGRect family of methods, including CGRectDivide . They will be useful in drawing up opinions, as well as in calculating what is visible and what is not.

Answer 2

There are several third-party classes / libraries that you can get to create this function, AQGridView comes to mind. But there are no default default classes for this.

If I had to develop this type of implementation, I would subclass the UITableViewController. Expand it to have columns. Then a subclass of UITableViewCell will display the image. That way, all the container code and everything will already be there, and all you have to do is customize it according to your needs.