Best way to implement custom view - objective-c

I'm looking for the best and fastest way to implement view pictured above and I need advice.
I should manually build views, subviews, cells and menus from the scratch or use NSTableView and modify in some way? Maybe some third way?

The views seem straightforward enough. Just use the standard views and subviews, image views etc. to build them. For the reordering of row functionality, you want to use a table view (with your custom cells).
This seems to me the fastest way to prototype, test and deploy.

Related

How to make Native Web View disappear?

Basically, I need to set a visible property, or just call a hide() method to make it invisible in the screen, is there any way to do that?.
This currently isn't possible. You have two options, either make the view very small (1x1 px) or remove and recreate the view.
This feature is on our list of enhancements on github, feel free to add a comment there if you have any requirements.
Cheers

TableView how to implement cells overlap with custom scroll

I need to implement vertical and horizontal tables with overlapped cells and custom scrolling.
It should looks like this:
Table can have many cells (about 1000), so recycling is need too.
Do you know any third party components or may be standart that can helps me. Or i need to write my custom "TableView"?
What you're describing would be very difficult in a standard UITableView, since it requires controlling the layout of individual cells. The good news is that Apple does provide an API for specifying the the layout of reusable cells in whatever manner you want; the only wrinkle being that it is for UICollectionViews, not UITableViews. If you don't need to support older versions of iOS, I would encourage you to watch the WWDC sessions on collection views, and then check out Schwa's Coverflow project for a solid implementation of a similar style layout.

Grid View with UIPageControl in iOS 5?

I know there are plenty of Grid Views out there for iOS and Objective-c, but I couldn't find one that fits me. Currently I use a grid view called UIGridView. It included only two files and was very simple to implement. However it cannot have more cells than it can fit on the screen. I want a dynamic grid view where I can have a UIPageControl to have multiple pages with cells. I like the UITableView but for this project it would be more efficient to have a grid view.
I currently use this grid view: http://www.chupamobile.com/products/details/380/Interactive+Grid+View/
Is there a simple grid view with page control? Or can I put my current grid view in in a UIPageControl?
Did you try CHGridView at https://github.com/camh/CHGridView ?
I settled with the MMGridView. It has horizontal page control scrolling. I just modified the cells to my liking. You can find the git source here: https://github.com/provideal/MMGridView
I am currently using AQGridView so surely i recommend that as it is the least buggy and its functions are very similar to UITableView.
Also that If you are trying to do this without XIB it will be little bit difficult for you to handle it but you can create a view controller with Xib file to Create the interface of your choice. Here is the Video of how it can be done in the best possible way by Evadne Wu. And here is the Sample Project
Now for the Paging Control
in AQGridView you just need to set Paging Enabled and it will automatically do the rest. Hope that helps.

Sencha touch 2/ app workflow with navigation view

There is a problem with sencha touch 2.
I am trying to understand how can I implement the same functionality which provides navigation view in sencha touch 2, but ....
Each item of the 'Ext.NavigationView' component should have it's own unique set of 'navigationBar' elements. I mean set of buttons, for example.
I know that I can do something like this:
this.getMain().getNavigationBar().rightBox.removeAll();
this.getMain().getNavigationBar().rightBox.add(this.getSettingButton());
//where 'getSettingButton' predefined by me a button
And do this action each time when 'push' event happens (clear 'navigationBar' and add appropriate set of buttons)
Of course, I even can implement 'Ext.Panel' with 'layout: card' and set of 'Ext.panel' elements in the 'items' property, each of which will be have unique 'toolbar'.
To control the behavior I can use 'setActiveItem' method.
But, I think each of these approaches is a bit weird, isn't it?
I expected that would be much more natural approach to implement it.
Most likely I don't know what I need. Confirm my doubts. What is the best way to do it.
Currently, Ext.NavigationView tends to perform navigation between "simple" views. "Simple" here means that your views are just panel with innerHTML, not the "complicated" ones with functional buttons, toolbars, etc.
As far as I know, there're 2 ways you could try:
If you still want to use Ext.NavigationView, you can customize your NavigationBar with titles, items (buttons, spacers, etc.) as normal components through navigationBar config, getter and setter.
(recommended) If your views are completely different from each other, you should use many Ext.Container with different items of your choice (for eg. first container with simple HTML announcement, second one with some extra Ext.Button, and so on). Simple use animateActiveItem() for animated navigation. This way is much more flexible, I suppose.

Customising UITableView scrolling!

Is it possible to make the table view allow scrolling only in one section and not others OR in other words allowing scrolling only in desired sections of the grouped table?
Many thanks.
Sure, this is entirely possible if you're willing to forego the use of a tableview. If you use a scrollview, you can achieve what you want by defining custom behaviour. It's not going to be easy but here are some suggestions:
Figure out how you want it laid out on the screen
Create a "floating cell" that will hang around, this will be your "not scrolling" section
With respect to #2 above, you'll have to figure out what kind of logic you want to make that floating cell disappear versus the other data.
The rest, you're effectively reimplementing a tableview.
Now, you can probably achieve this with a tableview, but it's be hairy big time.