RubyMotion #inspect conference update

I’ve updated the lodging section of the website. If you’re coming to the conference in May, check it out for tips on where to stay. You can see it here

New speakers have been added, HipByte wrote about it here.


If you missed the last issue, you can find it here: issue #21

Happy coding, Todd Werth (@twerth)

Articles, News, New Gems, and Blog Posts


Apr 8th, 2014 – “How to Add Reveal to Your RubyMotion App Without Modifying the Rakefile” by Mark Villacampa

Apr 8th, 2014 – “meetup – Quarterly Hands on RubyMotion in Chicago” by David Astels

Apr 7th, 2014 – “screencast – Custom Table View Cells & AutoLayout” by Jack Watson-Hamblin

Apr 7th, 2014 – “gem – A RubyMotion Wrapper for the awesome Phony gem” by Christopher Speer

Apr 6th, 2014 – “BostonMotion 6 – RubyMotion Meetup” by BostonMotion

Apr 4th, 2014 – “podcast – Hack and Heckle 057 – RubyMotion Sydney meetup organizer interview” by Leigh Appel

Apr 3rd, 2014 – “video – Kod.io 2014 – RubyMotion’s Secret Sauce by Joshua Balanco” by Joshua Ballanco

Apr 3rd, 2014 – “RubyMotion #inspect 2014: First Batch of Speakers, Lodging Information, Sponsors” by RubyMotion

RubyMotion news


RubyMotion 2.26

  • Fixed a regression introduced in the previous release that was causing a
    crash when checking if a class supports weak references on iOS 6.

RubyMotion 2.25

  • Added support for Xcode 5.1 and iOS 7.1 final.
  • Added support for OSX 10.6 as deployment target (experimental).
  • Improved user feedback by printing a warning when overriding a protocol
    method that was previously defined with one of the `attr_*’ methods. This
    may print false positives.
  • Improved `rake ctags’ to index the application’s .rb files. Thanks to
    Hwee-Boon Yar for the patch (pull request #152).
  • Improved use of WeakRef' to raise an exception when trying to create a
    weak reference to one of the unsupported classes. For more information, see
    Which classes don’t support weak references?’ at http://bit.ly/1iiSOaU.
  • Added some introspection support to `ImmediateRef’. It can now report the
    actual class, its methods, and a inspect description string.
  • Added gemspec call to Gemfile for gem template. Thanks to Mark Rickert for
    the patch (pull request #151).
  • Fixed a bug where `rake device debug=1′ did not work with Xcode 5.1.
  • Fixed an error in `rake device debug=1′ if it would use UTF-8 as app name.
  • Fixed a bug where an application could not be installed and launched on the
    Simulator or a device due to the application bundle containing a directory
    called `Resources’. This will now fail the build with a descriptive error.
  • Fixed a bug where the OS X REPL did not work on 10.7 Lion.
  • Fixed a bug where KVC property validation methods defined in Ruby would not
    be compiled with the appropriate (Pointer) types.
  • Fixed a bug where Ruby methods defined on Objective-C tagged pointer
    objects could not call methods on itself.
  • [iOS] Made tap' test helper work withUISwitch’.
  • Fixed a bug where methods with BOOL arguments would not be handled properly.
  • Fixed a bug where the cycle detector did not work for Array/Hash objects.
  • Fixed a memory leak in Object#{method, public_method, instance_method,
    public_instance_method}.
  • Fixed a bug where Boxed#copy would cause a crash.
  • Fixed a bug where Range#copy would cause a malloc_error_break error.
  • Improved Object#instance_variable_set performance. ~20% faster.
  • Improved Object#method performance. ~50% faster.
  • Improved method dispatcher performance. ~5% faster.
  • Improved fine-grained lock performance. ~20% faster.
  • Improved memory management performance. ~25% faster.

RubyMotion App of the Week


image

Apr 8th, 2014 – Winds Aloft Forecast

“aloft is the beautiful new way to check NOAA winds aloft forecasts from your iOS device!”

iOS Marketing Tip of the Week by Mark Rickert


From time to time, I’d like to start taking questions from Dispatch readers. If you’ve got an App Store marketing question you’d like me to address, please email me at mark@mohawkapps.com.

This question comes from my good friend, Gant Laborde. Gant asks:

There’s a lot of websites for submitting your app for indexing, and giving away app codes. Are any of them worth a damn?

I’ve been developing iOS apps since 2011 and I’ve never submitted my app to an app indexing service, yet my apps show up. Most of these websites simply scrape Apple’s public RSS feeds and search APIs. This gets them pretty much all the data they need to run their sites and make money off affiliate links (see Issue #19 for my tip on how to make money off linking to the App Store).

The really interesting part of the question is about redeeming promo codes. I’m a big fan of Tokens which is an app that helps you create and distribute promo codes and then tells you when they’ve been redeemed. This makes it really easy to track who you sent codes to and what percentage of your promo codes are used. The app is free for one app, so try it out and see if it makes your giveaway workflow better. There are other services out there, but I’ve found Tokens to be the best in terms of functionality, user experience, and developer workflow.

RubyMotion Tip of the Week by Gant Laborde of Iconoclast Labs


Understanding NSLog vs puts

Most Ruby devs know the difference between puts and p. They know that p will simply call puts with inspect e.g.

p foo == puts foo.inspect

p doesn’t just call to_s, so It’s much better for debugging and that’s why I personally use p all the way up until I get a chance to implement awesome_print_motion, and switch p out for ap. I’ll even leave it in my production apps as Mark Rickert suggests.

This is great for debugging the Ruby side, but it’s no panacea. Sometimes you’ll crash before you can even see your messages. Keeping your messages at the Ruby level, means that you’re not writing a file, and you can’t directly utilize the Apple System Log facility. This is where using NSLog would be best (bonus is that they get time and process stamped, too!).

You’ll always be able to find your results logged:
On Device rake crashlog:device

Simulator rake crashlog

You’ve got options, so use the method that works best for you!

One more thing


The community is working on an app for the #inspect conference. Look for it next week.


If you have any tips, blog posts, or want to sponsor this newsletter, please send emails to todd@infinitered.com