rubymotion-community / BubbleWrap

Cocoa wrappers and helpers for RubyMotion (Ruby for iOS and OS X) - Making Cocoa APIs more Ruby like, one API at a time. Fork away and send your pull requests
Other
1.18k stars 208 forks source link

Extract BW::HTTP to the bubble-wrap-http gem #363

Closed clayallsopp closed 10 years ago

clayallsopp commented 10 years ago

Also prints out the following message when building your app:

$ rake
   Warning BubbleWrap::HTTP is deprecated and will be removed - switch to a different networking library soon (see https://github.com/rubymotion/BubbleWrap/issues/308).
   Warning You can use the 'bubble-wrap-http' gem if you need compatibility: https://github.com/rubymotion/BubbleWrap-HTTP
     Build ./build/iPhoneSimulator-7.0-Development
clayallsopp commented 10 years ago

(travis failing due to #359 behavior)

pixlwave commented 10 years ago

The warning message gets printed for rake --tasks which I presume is undesirable behaviour? It's showing up as 3 "runnable" tasks in the most recent version of SublimeRubyMotionBuilder.

clayallsopp commented 10 years ago

I'd say that's more of a bug with SublimeRubyMotionBuilder - it should check for commands which start with rake ____. (you'll also see extraneous output in rake -T whenever a RubyMotion update is available)

pixlwave commented 10 years ago

Ok, well @watson1978 said the opposite when I reported it there.

Watson1978 commented 10 years ago

SublimeRubyMotionBuilder lists the task which retrieved with bundle exec rake -T, then run selected task with bundle exec rake ..... It is very simple.

Hmm, I added "Set Up" section recently in https://github.com/RubyMotionJP/SublimeRubyMotionBuilder/blob/master/README.md#set-up Did you try?

Watson1978 commented 10 years ago

OK, I think @digitalfx problem will be solved with https://github.com/RubyMotionJP/SublimeRubyMotionBuilder/commit/19a48b5986bd5bee5ac871a4d4a4a751b3bbcc7c

pixlwave commented 10 years ago

Yep that's done the trick. Thanks both.