Or any CI server that works well.

Could you please do separate e.g. branch?

Using master, both "carthage bootstrap" and "carthage update" both yield the error:

uncaught exception 'NSInvalidArgumentException', reason: 'working directory doesn't exist.' 

It looks similar to Carthage/Carthage#745 However, changing the Cartfile to different things didn't help.

The Rex Cartfile is identical to something I am using for a private project and it works fine there. So, something deeper is happening here.

Not sure this is fully possible but would like to try and have this be swift only.

Currently I've been adding things as needed but there's a lot in RAC 2 that should be ported.

Finish up and add the query stuff I was experimenting with 6-months ago.

I think for consistency we should have everywhere properties, or is there any reason for this?

Use UIButton.rex_pressed. It's the most interesting because it also binds the enabled state of the actions property.

And maybe also the source of documentation too

Just wanted to say thank you for maintaining this repo. Very helpful in MVVM patterns. Cheers!

Hi,

I just wanted to ask if we should aim for a new release with the release of RC1 or simply stick with alpha 4, since there were only bugfixes in RC1?

I'm going to write more generic print method, but don't know what to do with .Next and .Error. I cannot just call signal |> print(.Next) or signal |> print(.Error). These cases need to be called with arguments. Could you please help? Should I implement additional enum?

See the actual code below.

public func print<T, E>(_ event: Event<T, E>? = nil)(signal: SignalProducer<T, E>) -> SignalProducer<T, E> {
    return signal
        |> on(event: { aEvent in
            if let event = event {
                switch (aEvent, event) {
                case (.Next, .Next):
                    println(aEvent)

                case (.Error, .Error):
                    println(aEvent)

                case (.Completed, .Completed):
                    println(aEvent)

                case (.Interrupted, .Interrupted):
                    println(aEvent)

                default:
                    break
                }
            } else {
                println(aEvent)
            }
        })
}

I want to show error popup when an error happened to signal. How can I handle SignalProducer errors to show error to user?

let emailAndPasswordChecksSignal = emailTextSignal.combineLatestWith(passTextSignal)
        .flatMap(.Merge) { (email, password) -> SignalProducer<(), TextFieldErrorType> in
            if email == nil || email?.characters.count < 1 {
                return SignalProducer<(), TextFieldErrorType>(error: .EmailIsNotCorrect)
            }
            if password == nil || password?.characters.count < 1 {
                return SignalProducer<(), TextFieldErrorType>(error: .PasswordIsEmpty)
            }
            return SignalProducer<(), TextFieldErrorType>(value: ())
        }

        let loginAction = Action<UIButton, (), TextFieldErrorType> { _ in
            return emailAndPasswordChecksSignal
        }

I use MutableProperty to fill values coming through a Bluetooth protocol, and them being represented at real-time in different sections of the application.

I was thinking (and maybe it could be useful to add in this library) a method which fills a producer or signal with .Next(value) events eachtime the original producer or signal doesn't send any value for a NSTimeInterval. Using the DateSchedulerType shouldn't be hard to achieve this behavior.
When the signal or the producer sends again a value, the "Default" event is replaced inmediately and the countdown starts again.

What do you think?

rex_text filters nil values, so it does not send any value when text is erased in UITextField

I'm not currently doing iOS development in my day job and as a result haven't been able to maintain this library to the degree I would like. There's been discussions about moving Rex under the ReactiveCocoa org and it effectively becoming RAC5 since it provides the missing Swift Cocoa bindings. IMO, moving to RACCommunity would be a good first step in that transition. It'll ease the maintenance burden I haven't kept up with and provide a staging area to prep for the RAC5 transition.

/cc @RuiAAPeres @mdiep @RACCommunity

Should use Jazzy and remove it from the README

I know that all this will be changed in nearest future, but in any case rex has following issue.

      self.textView.text = "Hello world"
      self.textView
         .rex_text
         .startWithNext { _ in
            //is not called for "Hello world"
      }

iOS wrapper for -[UIApplication beginBackgroundTaskWithExpirationHandler:]

Hello! With the last release of RAC (4.2.1) and Rex(0.10.0), I get the following error:
/Carthage/Checkouts/Rex/Source/SignalProducer.swift:84:23: error: ambiguous use of 'debounce(_:onScheduler:)'

I've solved it by fixing RAC version in 4.2.0

github "ReactiveCocoa/ReactiveCocoa" == 4.2.0
github "neilpa/Rex" ~> 0.10.0

Maybe you could make a new release to be compatible with 4.2.1? Thank you!

The MutableProperty wrappers are effectively copy & pasted with a few tweaks here & there for types, associated keys, and so on. It would be wise to figure out a way to use the gyb (Generate Your Boilerplate) tool from the Swift project to help us overcome a lot of that (sadly necessary) boilerplate.

Does Rex support ReactiveSwift and if so how can I use it?

How do you define UI properties that are in Rex.

E.g. Can we expect UIButton rex_image property or UIPageControl rex_currentPage? Or very useful NSLayoutConstraint rex_constant and rex_priority properties?

Sure UIKit has lots of different properties and adding them all will make this simple tiny library very complex. But I think there are still lots of often used that can be also added

Thanks!

Hi,

Just wanted to say that there is a bug or something in the compiler, which makes the compiler throw a warning when using StaticString.stringValue. This can be avoided by using string interpolation instead, as described here: CocoaLumberjack/CocoaLumberjack#471 (which refers to this StackOverflow: http://stackoverflow.com/questions/25867546/swift-warning-integer-overflows-when-converted-from-builtin-int32-to-builti)

That seems to be the way the world is going...

Very useful to associate any type of object: structs/enums
currently associatedObject allows to associate just AnyObject instances

private class Box<T> {
   let unbox: T
   init(_ value: T) {
      self.unbox = value
   }
}

extension NSObject {
   public final func associatedObject<T>(key key: UnsafePointer<()>, @noescape initial: () -> T) -> T {
      if let boxedObject = objc_getAssociatedObject(self, key) as? Box<T> {
         return boxedObject.unbox
      }
      let object = initial()
      objc_setAssociatedObject(self, key, Box(object), .OBJC_ASSOCIATION_RETAIN)
      return object
   }
}

I have successfully built Rex with Swift 2.3 based on 6243fc5.
Would it be possible to release a new version?

Should we update the bundle name from me.neilpa now that the repo is under RACCommunity?

Setup: I have a UICollectionView with 4 UICollectionViewCell's that contain a UILabel

class SectionBarCollectionViewCell: UICollectionViewCell, ReactiveView {

    static let DefaultIdentifier = "identifier"
    var viewModel = MutableProperty<SectionBarCellViewModel?>(nil)
    let titleLabel = Label()

    override init(frame: CGRect) {
        super.init(frame: frame)
        commonInit()
    }

    required init(coder aDecoder: NSCoder) {
        super.init(coder: aDecoder)
        commonInit()
    }

    func commonInit() {
        contentView.addSubview(titleLabel)
        bindObservers()
    }

    func bindObservers() {

        titleLabel.rex_text <~ viewModel.producer |> flatMap(.Latest) { $0?.title.producer ?? SignalProducer(value: "") } |> ignoreNil
    }

    func bindViewModel(viewModel: AnyObject) {
        if let viewModel = viewModel as? SectionBarCellViewModel {

            self.viewModel.put(viewModel)
        }
    }
}

when I profile my application it seems that the UILabel won't get destroyed when the UICollectionViewCell's are deinit

if i do it without binding, it destroys the UILabel as suspected when the Cell is deinit.

viewModel.producer |> flatMap(.Latest) { $0?.title.producer ?? SignalProducer(value: "") } |> start(next: {[unowned self] title in self.titleLabel.text = title })

I'm not sure how i can use rex_pressed, since its value is a CocoaAction

I made my own extension to receive events on a TouchUpInside

extension UIButton {

    public var rac_press: Signal<UIButton,NoError> {
        return associatedObject(self, &press, { _ in

            let action = Action<UIButton,UIButton,NoError>{ input in
                SignalProducer(value: input)
            }

            self.addTarget(action.unsafeCocoaAction, action: CocoaAction.selector, forControlEvents: .TouchUpInside)

            return action.values
        })
    }
}

private var press: UInt8 = 0

Does this makes sense? or do i misinterpret your rex_pressed?

I wanted to create a PR for this. But I cloned the repository and checked if the related file (Source/UIKit/UIDatePicker.swift) is included in the iOS framework target. Alas, it is! Now I'm at a loss why the UIDatePicker extension is not included in the generated header file for Rex. Any ideas?

The 0.10 version of the cocoapod is not yet published to the Cocoapods repo: https://cocoapods.org/pods/Rex

Could the maintainer of the pod publish this new version so we can easily upgrade to it? Would be nice, thanks in advance!

See discussion at end of #46

my cartfile:

 github "neilpa/Rex" "swift2"

my xcodebuild version:

$ xcodebuild -version
Xcode 7.0
Build version 7A218

my log file:

https://www.dropbox.com/s/wa4ujjm6fdqembc/carthage-xcodebuild.OWgLIO.log?dl=0

Hi,

Would you be willing to create a new tag for the alpha 3 so that it can be easily targeted? Or should I assume that 0.9.0-alpha.2 would be good enough?

Cut a 0.11 release targeting RAC 4.2 (or 4.2.1?). I think @RuiAAPeres deserves the honors if he wants it.

Hello,

UILabel has var text: String?

Why rex_text does not have MutableProperty<String?> type?
currently have to write in many places label.rex_text <~ optionalText.map { $0 ?? "" }

Thanks!

Hi,

trying to bind an AnyProperty<Bool> to a UIButton.rex_enabled by using <~ and experienced EXC_BAD_ACCESS. I played around and it seems that this also crashes when only accessing UIButton.rex_enabled

initial Code:

    override func viewDidLoad() {
        loginButton.rex_enabled <~ loginViewModel.validCredentials
        super.viewDidLoad()
    }

this crashes also:

    override func viewDidLoad() {
        loginButton.rex_enabled
        super.viewDidLoad()
    }

loginButton comes from an @IBOutlet and I can confirm that there is no issue with the button instance.

Do I miss anything here or is this a bug?

ReactiveCocoa 4.2.0
Rex 0.10.0
Result 2.0.0
xCode 7.3.1