Spry: Obnoxiously Easy iOS Development With RubyMotion
github.com
github.com
The thing is, when you create a table view in iOS apps, most of the work is for design and interaction like swiping to show a set of controls.
But you're right, there's a lot of work to do to support the concerns in a real app. I'm looking forward to it.
A lot of talk about RubyMotion has been about how Ruby developers and those who aren't familiar or comfortable with Objective-C can develop for iOS. I don't see why it can't work in the other direction as well: a nice entry point for people familiar with Objective-C looking for an easy-in for Ruby.
I develop in Objective-C as well, and I am very interested in what RubyMotion will bring to the table. So far, what I've seen is typical Objective-C code translated to Ruby. That doesn't offer me any advantage. What I want to see is something that will significantly boost productivity. REPL seems like one of them, but I want to see something on the code level.
There are few things I wish it was simpler (e.g. Core Data) but I guess this will be fixed over time with RubyMotion wrappers and some kind of DSL.
This specific example saves some code over building the app from scratch in straight ObjC. But, you could get the same savings with a regular ObjC library that does the same thing, too.
It's an Active Record(ish) syntax layer for the Parse iOS SDK.
Why are we OK with this conflation of language for marketing gimmicks?
I'm developing an education app and would love for it to be in Rails. Know where to find a good Rails coder comfortable with RubyMotion and iOS?