Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UIViewController #26

Open
SentoCrespo opened this issue Oct 16, 2017 · 3 comments
Open

UIViewController #26

SentoCrespo opened this issue Oct 16, 2017 · 3 comments

Comments

@SentoCrespo
Copy link

It would be reaaaaally nice to have life cycle methods:
viewDidLoad
will/did appear/disappear
etc.

Thanks for this nice kit!

@vhesener
Copy link
Owner

Interesting concept. I've thought about it in other lifecycle mechanisms, but not view controllers.

This will be different because UIViewController lifecycle methods are subclassed, rather than delegated. It's an interesting problem though.

Can you set the stage with a use case for how you would interact with these methods? I'm assuming from outside the controller, correct? Is there a particular navigation architecture (i.e. VIPER) that would benefit from this?

@SentoCrespo
Copy link
Author

Hello Sir!

You're very right, indeed.
Model View Presenter for instance or any other architecture that separates the view from who controls it like VIPER, or MVVM or whatever. The presenter would be able to control everything from outside it, although I know it might be coupled to a specific type but I was only curious about all this concept.

Right now I'm using RxSwift with some extension for UIViewController that allows me to do such thing:
https://github.com/devxoul/RxViewController

@vhesener
Copy link
Owner

Let me think for a little about how to do this. Stay tuned.

@vhesener vhesener mentioned this issue Oct 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants