Proposal for API design about github-issues

[chriseidhof]

I'm not sure exactly what the semantics are...

push means that the view controller will eventually be pushed? What does dismiss do? Currently, dismissing is very much implicit (which is not necessarily a good thing).

[nverinaud]

push means continuing the flow normally (for NavigationController this means pushing a new vc on the stack). What I have in mind is that this function (and the others) are adapters for the custom >>> operator which permits composition. The need is to decouple the custom operator >>> from NavigationController and have it accepts adapters.

Here are 2 other examples:

// NavigationController module
let navController = NavigationController.root(screen1)
let flow = navController
>>> navController.push(screen2)
>>> navController.push(screen3)

// SplitViewController module
let splitViewController = SplitViewController.root(NavigationController.root(screen1), screen2)
let flow = splitViewController
>>> splitViewController.leftController.push(screen3)
>>> splitViewController.replaceDetailOnRight(screen4)

The idea is to have mondules with their own semantics, and make them >>> friendly.

In the example I provided in the first post, presentModally may alter the next possible transitions so that only a dismissal is possible to continue the normal flow. A custom flow may be injected though to perform a modal presentation of a navigation flow, then at the end of this flow, perform the dismissal.
It could be designed like this :

let modalFlow = root(screen10)
>>> push(screen11)
>>> push(screen12)

let flow = root(screen1)
>>> presentModally(modalFlow) // dismiss remains implicit and occurs at the end of the modal flow
>>> push(screen2)

You agree that the idea behind all of this is : view controllers act as (pure) functions and navigation is just functions composition. >>> composes functions and push, presentModally, etc, wraps screens to play well in this composition.

[chriseidhof]

Cool! I'm currently on a long trip, but will look at this when I'm back in
august. I'm all for making this entire thing not navigation-controller
dependent...

On Fri, Jun 26, 2015 at 9:26 AM, Nicolas VERINAUD [email protected]
wrote:

push means continuing the flow normally (for NavigationController this
means pushing a new vc on the stack). What I have in mind is that this
function (and the others) are adapter for the custom >>> operator which
permits composition. The need is to decouple the custom operator >>> from
NavigationController and have it accepts adapters.

Here are 2 other examples:

// NavigationController modulelet flow = NavigationController.root(screen1)

NavigationController.push(screen2)
NavigationController.push(screen3)

// SplitViewController modulelet flow = SplitViewController.root(NavigationController.root(screen1), screen2)

SplitViewController.LeftController.push(screen3)
SplitViewController.replaceDetailOnRight(screen4)

The idea is to have mondules with their own sementics, and make them >>>
friendly.

In the example I provided in the first post, presentModally may alter the
next possible transitions so that only a dismissal is possible to continue
the normal flow. A custom flow may be injected though to perform a modal
presentation of a navigation flow, then at the end of this flow, perform
the dismissal.
It could be designed like this :

let modalFlow = root(screen10)

push(screen11)
push(screen12)
let flow = root(screen1)
presentModally(modalFlow)
dismiss()
push(screen2)

You agree that the idea behind all of this is : view controllers act as
(pure) functions and navigation is just functions composition. >>>
composes functions and push wraps screens to play well in this
composition.

—
Reply to this email directly or view it on GitHub
#9 (comment)
.

Chris Eidhof