-
Notifications
You must be signed in to change notification settings - Fork 208
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
adds 'BW::NetworkIndicator' #349
adds 'BW::NetworkIndicator' #349
Conversation
Sweet, and I think it would also make a lot of sense to integrate with In this case, thread safety is a realistic consideration - did you check out @bogardon's implementation or other iOS network indicator implementations? (SDNetworkActivityIndicator, AFNetworkingActivityIndicatorManager, etc) Also the tests failed on Travis? |
Ah, those failures are from the HTTP integration actually. I'll check it out. I'll see what needs to be done about thread safety, too. Thanks Clay! |
Ah gotcha. Yeah, I think the networking indicator should be included by default w/ |
… delayed (avoids flickering), thread support (all updates are on the main thread)
Man, turns out all the queries that get created in I've added a warning message to |
Dang it. Specs pass locally, I'll see what's up. |
@colinta It could be that the iOS version is passing and the mac version is not. See @clayallsopp's recommendation for me that helped the specs pass: #335 (comment) |
Yeah i think you're right; getting 'cancel called on nil' when running on osx. thanks for the heads up! 😃 |
I'm still getting a 'failure' on osx, but it's in the
|
Strange behavior on my machine, but specs are passing on travis. :-/ |
Can someone run
and see what it says? |
This is interesting, and broken for me on master. Adding some logging, I see Travis runs 10.8, which could be making a difference. Sounds like a rubymotion bug @colinta? I've opened #351 and submitted a that aside, I'm down for merging this if it's okay with you @colinta? |
Yeah, the error isn't related to the |
adds 'BW::NetworkIndicator'
- 'bubble-wrap/http' is now deprecated and will be removed in 2.0, see #308 + `BW::UIActivityViewController` wrapper added, see #335 + `BW::NetworkIndicator` added, see #349 + `BW::Location.get_compass` & `BW::Location.get_compass_once`see #348 + `NSString#to_color` ARGB support, see #350 + `Object#method` support for `BW::Reactor`, see #359 * Prevented a possible exception when stopping `BW::Location`, see #358 * Fixed a bug when requiring just 'bubble-wrap/ui'
- 'bubble-wrap/http' is now deprecated and will be removed in 2.0, see rubymotion-community#308 + `BW::UIActivityViewController` wrapper added, see rubymotion-community#335 + `BW::NetworkIndicator` added, see rubymotion-community#349 + `BW::Location.get_compass` & `BW::Location.get_compass_once`see rubymotion-community#348 + `NSString#to_color` ARGB support, see rubymotion-community#350 + `Object#method` support for `BW::Reactor`, see rubymotion-community#359 * Prevented a possible exception when stopping `BW::Location`, see rubymotion-community#358 * Fixed a bug when requiring just 'bubble-wrap/ui'
Regarding #263 and #171, I agree w/ @clayallsopp that
UIApplication.sharedApplication.networkActivityIndicatorVisible
should be controlled by a centralized module.I didn't call it
BW::HTTP::NetworkIndicator
, because I think it could be used as a standalone module (maybe they're not using BW::HTTP).methods available:
BW::NetworkIndicator.show
BW::NetworkIndicator.hide
BW::NetworkIndicator.visible?
BW::NetworkIndicator.reset!
Specs included.