Collapsible tableview section for static cells in swift 3 - tableview

I have created a sidebar using static table view having 2 sections. I created this using storyboard only. I want to have the sections collapsible. I found this resource in github
https://github.com/jeantimex/ios-swift-collapsible-table-section
But they have made a collapsible tableview section without any storyboard and for dynamic cells. I can't figure out how to do this. Any help would be highly appreciated.

Related

How to create a page that leads to multiple scrollviews in swift

The beginning page is a table view. On the table view there is table that contains four different topics(picture provided). I would like each topic to lead to a new page that is a scroll view. I have successfully programmed so that the first topic will lead to a scroll view. However, I am having trouble creating more than one scroll view page for each topic. enter image description here
How to:
Create destination view controllers in your storyboard.
Create segues by CTRL-dragging from cell to the view controller that should be shown when the cell is tapped.

Is there a way to add a footer view to NSTableView?

I need to add a view very similar to a table footer view in iOS, but to NSTableView. Is there a painless way to do it?
Many thanks!

One TableView implemented in several ViewControllers

I am looking for a way to create a TableView to show a list of posts on a social networking site. I want to place the exact same prototype table in several ViewControllers and based on the current ViewController, it will be populated with different information. Is there a way to do this with Storyboard? I assume that this is quite easy using only code, but I would like to drag and drop elements to create the prototype cell.
Thanks
For each view controller you should create a new table view. You could reuse table view cells by creating a custom nib cell and populating each table view accordingly.
This is a good tutorial on how to populate a table view with an rss feed.
https://www.youtube.com/watch?v=NyrGnbzXpxk
You can then find the rss feed of each social media page that you want to include in each table view.

Store App Dashboard: GridView and Multiple Charts

I'm working on a Store app that consists of several charts. I've already developed the charts and have them rendering using the chart control in the various forms.
I have been asked to bring these together in an app that allows the user to scroll left and right through each of the charts.
Every example I have found for using a GridView data binds the content of the GridView to item templates.
What I'm trying to get my head round is how I could please these chart controls directly in to a GridView.
Any help would be greatly appreciated.
Cheers,
Roy
As per my understanding of the question you need to have charts as items in a grid view.
If this is what you want, I have dome this before using charts from 3rd party toolkit.
You need ( may be variable sized) templates with each item having a different template of its own.
You need a items list with data for all the charts.
Then upon runtime you need to assign the template to each item.

Backbone.Marionette Layouts, regions and views

In may Marionette app I do have set a layout with 3 regions
headerRegion
mainRegion
footerRegion
I am using the footer region to display detail views of my models (itemViews).
Now I do have the situation, that I want to use this region with collectionView in combination with a button-group: Add-Button (adds a model/itemView) and a OK-Button (closes/hides the collectionView and the button-group. I would like to handle these 2 itemViews as a component, showing and hiding them in 1 step.
I am not sure what the right way to do this is.
Option1:
show collection view in subregion1 of footerRegion and the button-group in subregion2 of footerRegion
Option2:
create a new Layout and nest it
Option3:
do it somehow with a compositeView?
Option4:
some combination with jquery hide/show the button-group?
My vote is for Option #2: nested layout. I do this a lot and it works very well. It's easy to manage and easy to work with, IMO.

Resources