Pages is the easiest way of setting up a UIPageViewController

PagesController is a subclass of UIPageViewController and we make the things I don't really like: it's delegate and dataSource of self. I think it's better approach to make it a subclass of UIViewController and have a property of UIPageViewController. What do you guys think @zenangst @3lvis @kostiakoval ?

We need to handle page change in subclasses (like PresentationController), but it's not good to occupy pagesDelegate which could be needed during the actual usage.

Add 3 props:

public var pageControlBackgoundColor: UIColor?
public var pageIndicatorTintColor: UIColor?
public var currentPageIndicatorTintColor: UIColor?

Hi there, I am intrigued by the simplicity of the example shown in the README. But I'm at a loss as to how to implement any of this. All the example says is to do this:

let viewController1 = UIViewController()
viewController1.title = "Controller A"

let viewController2 = UIViewController()
viewController2.title = "Controller B"

let pages = PagesController([viewController1, viewController2])

Which left to our own wits, I have no idea where to put this code, or initialize it, anything. I've imported the library into my project. Created 3 ViewControllers (all through the storyboard) and associated them with their appropriate classes in code.

See below of the setup.

// is initial view controller
class Start: UIViewController {
    override func viewDidLoad() {
        super.viewDidLoad()
    }
    override func viewDidAppear(animated: Bool) {
        let viewController1 = First()
        let viewController2 = Second()
        let pages = PagesController([viewController1, viewController2])
    }
}

class First: UIViewController {
    override func viewDidLoad() {
        super.viewDidLoad()
    }
}

class Second: UIViewController {
    override func viewDidLoad() {
        super.viewDidLoad()
    }
}

All I get is a black screen.

Using the code:

let viewController1 = Tutorial_1_ViewController()
let viewController2 = Tutorial_2_ViewController()
let pages = PagesController([viewController1, viewController2])
self.presentViewController(pages, animated: true, completion: nil)

pages is displayed, but the page is just black and doesn't allow scrolling. Showing each of the viewControllers individually works correctly so it isn't an issue with them.

Any ideas?

Thanks for the Class though :)

Hello,

I got the following error with XCODE 10:

:0: error: fatal error encountered while reading from module 'Pages'; please file a bug report with your project and the crash log :0: note: compiling as Swift 4.2, with 'Pages' built as Swift 4.1.50 (this is supported but may expose additional compiler issues)

1. While running pass #1 SILModuleTransform "PerformanceSILLinker".
2. While deserializing SIL vtable for 'PagesController' in module 'Pages' error: Abort trap: 6

Since startPage is a public property on PagesViewController, I assume that it's meant to be available to developers to change and enforce a start page during runtime?

I noticed that when your currentIndex = 0 and if you set startPage to 1, the page at index 0 is still accessible as usual.

Not sure if it's a behaviour worth considering adding but I've created quick PR #39 to fix that

Hi there! I've updated Pages to be compatible with Xcode 10 and Swift 4.2 and bumped the pod version up. Please let me know if any question, and would love to get this merged asap!

Thanks, Alex

I have been trying to implement UIPageViewController in my App. After trying conventional UIPageViewController now I am trying yours and everything goes as I wish but one thing is making me crazy . I need paging to happen after user taps a signup button and it okay I had e managed to make it and to the current problem I am facing , There is four pages(UIViewController) for paging when the user reaches the 4th page and after on swipe I need to jump to a ViewController which is not part of Paging. I have done it using Next button click but on swipe I didn't get it right. is it possible using swipe ?

referencing: #40

I've added code that does two things:

1. On startPage's didSet observer, run goTo(startPage) if the user's currentIndex is less than startPage
2. Check that parameter index is more than startPage when goTo(index: Int) gets called