blob: 744b4337288f52ee79436b2a3b9b074015f229f3 [file] [log] [blame]
{
"name": "VIPERS-Wireframe-Protocol",
"version": "0.1.1",
"summary": "Wireframe / router implementation - Protocols used by VISPERS.",
"description": "The wireframe layer in an VIPER-Application is used to create and to present view controllers and controller transitions. A VIPERS application uses an object conforming to the WireframeProtocol to route between the controllers of your app.\n\nIt is the powerful thing that wires the view controllers in your app together. It takes an NSURL and some parameters, talks to the components that create your view controllers (the ControllerProvider) which create the view controller connected to this URL, and gives it to those components which are responsible for presenting your controller (the ControllerRoutingPresenter).\n\nThe wireframe is responsible for navigating to the next view controller and communicates and connects all objects of the wireframe layer. It is used by the presenter layer to navigate to the next view controller. We recommend you to avoid using it in a view controller which is located in the view layer. It is better to call it from a delegate.",
"homepage": "https://github.com/VIPER-Swift/VIPERS-Wireframe-Protocol",
"license": "MIT",
"authors": {
"Jan Bartel": "barteljan@yahoo.de"
},
"source": {
"git": "https://github.com/VIPER-Swift/VIPERS-Wireframe-Protocol.git",
"tag": "0.1.1"
},
"platforms": {
"ios": "8.0"
},
"requires_arc": true,
"source_files": "Pod/Classes/**/*",
"resource_bundles": {
"VISPERS-Wireframe-Protocol": [
"Pod/Assets/*.png"
]
}
}