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

How to program UI now, without unsafeCocoaAction? #21

Closed
nikita-leonov opened this issue Sep 19, 2016 · 3 comments
Closed

How to program UI now, without unsafeCocoaAction? #21

nikita-leonov opened this issue Sep 19, 2016 · 3 comments

Comments

@nikita-leonov
Copy link

It seems that unsafeCocoaAction was removed for the obvious reasons, but now it is unclear what to do with the programming of UI. Is there other sub-project with an extension of Action with unsafeCocoaAction that should be used for this purpose?

@mdiep mdiep added the question label Sep 19, 2016
@mdiep
Copy link
Contributor

mdiep commented Sep 19, 2016

unsafeCocoaAction remains part of https://github.com/ReactiveCocoa/ReactiveCocoa since it's Cocoa specific.

@mdiep mdiep closed this as completed Sep 19, 2016
@nikita-leonov
Copy link
Author

Thanks, sounds reasonable. Do I understand it right that ReactiveCocoa will be only Cocoa-specific, while ReactveSwift will be its Swift based foundation? As a result, there will be no two Action classes in both ReactiveSwift and ReactiveCococa code-bases.

@mdiep
Copy link
Contributor

mdiep commented Sep 19, 2016

ReactiveCocoa is now built on top of ReactiveSwift. All the cross-platform bits are in ReactiveSwift; all the Cocoa-specific bits are in ReactiveCocoa. So Action is in ReactiveSwift, but CocoaAction is in ReactiveCocoa.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants