Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

RubyMotion 3.0 Sneak Peek: Android Support

blog.rubymotion.com

Post reply on HN
Print view View original

11–20 of 80 posts

Re: RubyMotion 3.0 Sneak Peek: Android Support

#12

Post by thezoid »

bratsche wrote: post #6

"The object model of RubyMotion for Android is based on Java. Ruby classes, objects, methods and exceptions are Java classes, objects, methods, and exceptions, and vice-versa. No bridge is involved." But then later it says "The runtime uses the Java Native Interface (JNI) in order to integrate with Java". And then later it says, "RubyMotion Android apps are fully compiled into optimized machine code, exactly like the…

I believe you don't need to do anything along the lines of JRuby where you would sometimes need to bridge libraries from Java-land into Ruby.

This most likely makes the same assumption that you are using a similar kind of project management as in RubyMotion for iOS and using RM specific libraries.

Re: RubyMotion 3.0 Sneak Peek: Android Support

#14

Post by bratsche »

thezoid wrote: post #12
bratsche wrote: post #6

"The object model of RubyMotion for Android is based on Java. Ruby classes, objects, methods and exceptions are Java classes, objects, methods, and exceptions, and vice-versa. No bridge is involved." But then later it says "The runtime uses the Java Native Interface (JNI) in order to integrate with Java". And then later it says, "RubyMotion Android apps are fully compiled into optimized machine code, exactly like the…

I believe you don't need to do anything along the lines of JRuby where you would sometimes need to bridge libraries from Java-land into Ruby. This most likely makes the same assumption that you are using a similar kind of project management as in RubyMotion for iOS and using RM specific libraries.

I've never had the opportunity to bridge Java-to-Ruby for JRuby. But when I read "the runtime uses JNI", I read that as a bridge.

And when they start off with "Ruby classes are Java classes", then later say "everything is compiled to native" that seems like more double-speak.

Re: RubyMotion 3.0 Sneak Peek: Android Support

#15

Post by blacktulip »

mark_l_watson wrote: post #8

Does anyone know if the RubyMotion price of $200 will include Android support, or will that be a separate product?

It is most likely all included in one product. If it is a separate product it would not use --template `motion create --template=android Hello`

Re: RubyMotion 3.0 Sneak Peek: Android Support

#18

Post by cmelbye »

rahilsondhi wrote: post #16

Are mobile apps written with RubyMotion on par with the native equivalent? For example, I've heard a lot of people dislike PhoneGap, AppAccelerator, etc because the final app isn't as polished as something that is built natively.

Yes, it says that in the announcement:

> The object model of RubyMotion for Android is based on Java. Ruby classes, objects, methods and exceptions are Java classes, objects, methods and exceptions, and vice-versa. No bridge is involved.

You're still coding to the same native APIs, but you're doing it in Ruby. That's how RubyMotion works on iOS/OSX as well as Android now.

Re: RubyMotion 3.0 Sneak Peek: Android Support

#19

Post by rahilsondhi »

cmelbye wrote: post #18
rahilsondhi wrote: post #16

Are mobile apps written with RubyMotion on par with the native equivalent? For example, I've heard a lot of people dislike PhoneGap, AppAccelerator, etc because the final app isn't as polished as something that is built natively.

Yes, it says that in the announcement: > The object model of RubyMotion for Android is based on Java. Ruby classes, objects, methods and exceptions are Java classes, objects, methods and exceptions, and vice-versa. No bridge is involved. You're still coding to the same native APIs, but you're doing it in Ruby. That's how RubyMotion works on iOS/OSX as well as Android now.

Very nice, thanks!
Post reply on HN