Multitasking - Should I go for UICollectionView or UITableView? - ios

My requirement is basically listing some details of an employee.
So, it is a list of 100s of employees.
The app is an iPad landscape application. The screen will look somewhat as follows.
I was thinking of a UITableView with a custom cell, that contain labels horizontally arranged on it as per my client's requirement.
But on considering the multitasking in iOS 9, I now face an issue in using this as I will not be able to maintain the same layout if the view reduce to 1/3rd or 1/2.
Now the best option I can think of is to use a UICollectionView with the labels shown as rows. That is something as follows:
I would like to get your suggestions on this and the best practises to be considered on designing a similar layout.

Related

iOS Multiple Scrolling Sections - Right way

i have question regarding one screen which i should implement in app, as iOS giving us various possibilities i don't know which one is the best practice for this current task.
Sections as visible on the screen should scroll and while we select one of them, should show unique data.
Scrolling Data Is Static.
My ideas:
1) Create multiple tableView's to support scrolling and get button actions.
2) Using the scrollView - programmatically add buttons on scrollview with multiple IBActions.
3) Modify UIPickerController to support such template.
As i mention there are lot of options and maybe i have missed more, but question is: In which way you would finish this tasks and how do you think is right way to handle such a design because on iPhone 5s we know that this UIView will be resized and will be smaller so UIView should be inserted in ScrollView itself.

UITableView or Collection View?

I have an iPad app which always stays in landscape mode. It is more of a data centered app with 5 columns and couple of hundreds of rows.
In current implementation, I have used UITableView. The rows' height could be anything depending on the data that comes in from server and all the columns can have different size.
The question is, can I use UICollectionView instead of UITableView? Will there be any performance issues? If yes, which is better in grid like layout? I understand UICollectionView is to be used in iOS pictures app like layout but how it behaves for grid like layout?
Thanks,
Pruthvid
What you describe is exactly what UICollectionView is designed for, it's the perfect solution. The limitation is only to the version of iOS you will be able to support (if you need to go back that far).
The choice really comes down to the visuals you want. Of you want each row to have a height defined by the maximum height of any column value in that row and the row appears as a single row item and the last row of the table should be full width then you may prefer to use a table view.
The collection view gives you more options for accessory views (as opposed to just the headers and footers of the table view).

UITableView vs UIScrollView

I am working on an animation application. I would like to have an horizontal UITableView or horizontal UIScrollView that will show little images representing a drawing at page X.
Since that my animation app can easily have 200 drawings, this means that my UITableView or UIScrollView can contain 200 images.
Finally, I would like to implement UIAnimation, where the user will be able to reorder the images by drag and dropping. I would like to have something smooth...
I have 2 questions :
Which classes is the better for memory management? I think I understood UITableView automaticly unload cells that are off screen, not UIScrollView. Is that true?
Which one might be easier to implement, considering possible heavy load? (I found this for horizontal UITableView : EasyTableView
Thank you
You should look into tiling with UIScrollView. There have been some very good sessions talking about advanced use of UIScrollView at WWDC over the past three years, and the videos of those sessions are available if you're a registered developer. They'll show you how to use UIScrollView's tiling feature to load just the content that you need, much as UITableView loads only the content that it needs.
As far as I'm aware, UITableView doesn't work in a horizontal mode, so UIScrollView is currently your only choice if you're only considering classes in Cocoa Touch. I'm sure there are some third party options, but I don't know enough to recommend one.

What's the technique to do expand/compact stack on iPad like Reeder and Photos?

On iPad, both the native Photos app as well as Reeder use a "expand/collapse stack" technique. Initially there is a stack of items on top of one another, each angled a bit with different corners showing. When you interact with them, the stack expands into a full screen and the items are laid out in a grid. When you collapse them, they collapse back into a stack.
What's the best way to set up my views to do the same thing? Should I just have a bunch of UIviews (one for each item) and manipulate their coordinates/transforms with an animation, or is there something more to it? Any example apps with code?
(Note: I am not asking about the interaction to invoke expand/collapse, I'm only asking what's the most appropriate way to lay out and set up my items.)
These days, use UICollectionView with different layouts and transitioning between layouts.

Implementing a table on ipad - possible solutions

I want to implement a table which is similar to the tv guide that you see in Yahoo app on iPad. The user needs to be able to scroll horizontally, vertically and even diagonally. The cells have to be resized dynamically based on the content.
Is this possible using UITableView or AQGridView? Or is there any other other approach to implement this kind of an interface?
You can achieve such behavior using a rotated UITableView inside a UITableView
have a look at this tutorial:
http://www.raywenderlich.com/4723/how-to-make-an-interface-with-horizontal-tables-like-the-pulse-news-app-part-2

Resources