Search Results for "git:/git.code.sf.net/p/docfetcher/code" - Page 2

DeckTransition is an attempt to recreate the card-like transition found in the iOS 10 Apple Music and iMessage apps. The transition can be called from code or using a storyboard. To use via storyboards, just setup a custom segue (kind set to custom), and set the class to DeckSegue. Set modalPresentationCapturesStatusBarAppearance to true in your modal view controller, and override the preferredStatusBarStyle variable to return .lightContent. By default, DeckTransition has a swipe-to-dismiss gesture which is automatically enabled when your modalʼs main UIScrollView is scrolled to the top. ...

...Make sure to use ScrollingNavigationController instead of the standard UINavigationController. Either set the class of your UINavigationController in your storyboard, or create programmatically a ScrollingNavigationController instance in your code. Use followScrollView(_: delay:) to start following the scrolling of a scrollable view (e.g.: a UIScrollView or UITableView). To DRY things up you can let your view controller subclass ScrollingNavigationViewController, which provides the base setup implementation. You will just need to call followScrollView(_: delay:): To move another view, like a toolbar, alongside the navigation bar you can provide the view or multiple views as the followers parameter.

Using Cartography, you can set up your Auto Layout constraints in declarative code and without any stringly typing! Call the constrain* function with your UIView or NSView instances as well as a closure in which you declare the constraints between the different attributes of your views. For every view on the left hand side of an equality or inequality operator, Cartography will automatically set its translatesAutoresizingMaskIntoConstraints property to false.

Kitz aims to make your development life a bit easier by reducing the boilerplate code you have to write. Just focus on building amazing new features! All Kitz are shipped with released apps. They also have full test coverage, minimal dependencies, and are collaboration friendly! In case the app can't open the external application, it will fall-back to a web URL that is guaranteed to succeed by opening the browser.

...Rather than design some arbitrary layout for a demonstration, I figured a good test for the practicality of Neon would be to replicate an existing screen from a major app, one that everyone could recognize. Now, keep in mind you'll probably want constants defined for many of these size/padding values, in order to keep the code cleaner and easier to maintain, but I decided to use real numbers for most of the values to make the code less obscure when new people are reading through the demonstration.