RubyMotion - Ruby for iOS

Post by frou_dh » Thu, May 03, 2012, 5:48 PM UTC

pjmlp wrote: post #11

tobiasbischoff wrote: post #5

nice, but where is the advantage over just using objc? the hard part of coding for iOS isn't objc, it's learning how to use all the API's.

I agree, but many young developers have C phobia and somehow seem not to be able to grasp C based languages.

Post by acangiano » Thu, May 03, 2012, 5:48 PM UTC

jwarzech wrote: post #21

I've played around with what seems like ever alternative framework under the sun (Titanium, Rhodes, PhoneGap, MonoTouch, Corona) and have been pretty frustrated with how clunky they usually feel. However with everything its claiming and the decent price point I'm toying with purchasing site unseen...just wish I could try it for a few hours first.

Post by hlidotbe » Thu, May 03, 2012, 5:49 PM UTC

jeremymcanally wrote: post #18

ScotterC wrote: post #10

I could see this really taking off. My worry is that it would take off so well that the ruby gem community could get fragmented into libraries for RubyMotion and libraries for regular ruby projects.

I'm supposing that they will probably implement it as another platform option like you can do right now for JRuby/Windows/etc. It shouldn't affect much. I haven't looked at the documentation, though, so I can't say for sure.

Post by melvinram » Thu, May 03, 2012, 5:50 PM UTC

acangiano wrote: post #29

melvinram wrote: post #19

Will apps created using this have any problems getting approved with App Store?

No. From the FAQ ( http://www.rubymotion.com/support/#faq ): "Applications submitted to the App Store must conform to the Review Guidelines dictated by Apple. RubyMotion implements a dialect of Ruby that conforms to those rules. RubyMotion apps are fully compiled, do not download or interpret code and are using public iOS APIs through the exact same machinery as regular Objective-C apps."

Post by protomyth » Thu, May 03, 2012, 5:52 PM UTC

hlidotbe wrote: post #20

protomyth wrote: post #14

Earlier quoted context omitted.

The call syntax is still painful compared to straight Objective-C as it actually uses more characters and is not as clean. I really wish he had come up with something that resembled Objective-C better.

I may have missed something but API calls looks like a regular Ruby call with a hash and since all [] are dropped it's systematically shorter (not even counting the fact that you don't have .h/.m, declaration/implementation, it's not just a matter of API calls). i.e. [obj method: param second: param2]; vs obj.method(param, second: param2) which is exactly two characters shorter in ruby. And what would be the point of…

  UIColor.colorWithRed(red/100.0, green:green/100.0, blue:blue/100.0, alpha:1.0)

  [UIColor colorWithRed:red/100.0 green:green/100.0 blue:blue/100.0 alpha:1.0];