Comments on: #8 VIPER to be or not to be? http://swifting.io/blog/2016/03/07/8-viper-to-be-or-not-to-be/ Swiftly coding in Swift Mon, 08 Aug 2016 20:00:39 +0000 hourly 1 https://wordpress.org/?v=4.5.3 By: Ruslan Remenkov http://swifting.io/blog/2016/03/07/8-viper-to-be-or-not-to-be/#comment-55 Tue, 19 Jul 2016 14:57:18 +0000 http://swifting.io/?p=292#comment-55 One of the best articles about VIPER!
Thank you so much! :-D

…but I still don’t see the whole picture. Can you share simple Swift VIPER project with 2 modules: 1 will be simple, and 2nd will contains a couple of submodules with data transferring between each other?

PLEASE! :-D

]]> By: Michał Wojtysiak http://swifting.io/blog/2016/03/07/8-viper-to-be-or-not-to-be/#comment-26 Thu, 07 Apr 2016 20:57:21 +0000 http://swifting.io/?p=292#comment-26 Hi Miguel,

We have read about other clean code architectures (uncle Bob’s comes to my mind) and appreciate their higher flexibility that VIPER provides. However we do not have practical experience with them yet. Thanks for the link to clean swift. It will be of great use when starting new project.

Best regards,
swifting.io

]]> By: Miguel http://swifting.io/blog/2016/03/07/8-viper-to-be-or-not-to-be/#comment-25 Thu, 31 Mar 2016 11:24:51 +0000 http://swifting.io/?p=292#comment-25 Hello!

Have you tried other clean-architecture aproaches?

We are currently implementing clean swift (http://clean-swift.com) , what are your thoughts about it?

Thanks!

]]> By: Darek http://swifting.io/blog/2016/03/07/8-viper-to-be-or-not-to-be/#comment-24 Mon, 21 Mar 2016 16:31:57 +0000 http://swifting.io/?p=292#comment-24 Great post!
Paraphrasing Carlsberg’s classic, probably the best VIPER description on the web.

Keep going guys! :)

]]> By: michael wang http://swifting.io/blog/2016/03/07/8-viper-to-be-or-not-to-be/#comment-22 Sat, 19 Mar 2016 14:25:09 +0000 http://swifting.io/?p=292#comment-22 if the project is very complex and changing fast , what should i do ? kick the app design’s ass?

]]> By: Michał Wojtysiak http://swifting.io/blog/2016/03/07/8-viper-to-be-or-not-to-be/#comment-20 Tue, 15 Mar 2016 20:33:43 +0000 http://swifting.io/?p=292#comment-20 Hi Pawel. Good question.
This is a perfect case to show in sample VIPER app that we plan to release.
To explain it shortly. When there is a need to present a new ViewController we do the following:
1. Wireframe function of presenting module has a parameter ‘fromView’ where we pass current ViewController.
2. In this function we instantiate presented module with method that returns fresh ViewController to present.
3. At this point we have both presented and presenting ViewControllers available in the same function body.
That’s enough to perform various kinds of navigation.

Best regards,
swifting.io

]]> By: Michał Wojtysiak http://swifting.io/blog/2016/03/07/8-viper-to-be-or-not-to-be/#comment-19 Tue, 15 Mar 2016 20:23:58 +0000 http://swifting.io/?p=292#comment-19 Hi Sameh, looks very good. Thanks for sharing!

Best regards,
swifting.io

]]> By: Pawel Krawiec http://swifting.io/blog/2016/03/07/8-viper-to-be-or-not-to-be/#comment-17 Tue, 15 Mar 2016 10:20:39 +0000 http://swifting.io/?p=292#comment-17 Thanks for great post.
However, I have question about presenting new view controllers – how do you pass current view controller instance to wireframe?

]]> By: Sameh Mabrouk http://swifting.io/blog/2016/03/07/8-viper-to-be-or-not-to-be/#comment-13 Sun, 13 Mar 2016 12:49:22 +0000 http://swifting.io/?p=292#comment-13 Thanks for sharing your great VIPER experrince. Happy to share with you this tool. A simple OS X App for generating VIPER modules’s skeleton to use them in your Objective-C/Swift projects.
https://github.com/iSame7/ViperCode

]]> By: Egor Tolstoy http://swifting.io/blog/2016/03/07/8-viper-to-be-or-not-to-be/#comment-12 Tue, 08 Mar 2016 12:35:29 +0000 http://swifting.io/?p=292#comment-12 Thanks for mentioning Generamba!
You can also look at our example VIPER project: Rambler.Conferences – https://github.com/rambler-ios/RamblerConferences

]]>