You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
It's been a full year since I acquired RubyMotion and became its steward. Over this time, RubyMotion has pushed thirteen releases (and is about to push number fourteen). Throughout this process, I have genuinely listened to the community's feedback and incorporated it within each release. Here are some highlights of what's changed. RubyMotion Applied The RubyMotion Applied GitHub Repo launched to
Laurent: In late 2011 when I decided to start working on a commercial mobile toolchain using the Ruby language. I really didn’t expect it to be successful that quickly. It has since been for me a wonderful, challenging, and rewarding journey. Today, 5 years later, it’s finally time for me to appropriately hand over the baton to someone else. Someone who has the motivation, the knowledge, and the a
Ruby support can be added to any modern Android application by adding JRuby as a dependency. The Ruboto project aims to add some additional sample code to make the integration between Java, Ruby, and the Android platform a pleasant developer experience. The Apps created thereafter depend on JRuby (jruby-jars) at runtime to provide full access to Android's Java APIs. Installation is straight-forwar
Announcing motion-provisioning: Simplified provisioning for RubyMotion iOS, tvOS and macOS apps Eventually, every iOS and macOS developer has to go through the motions of trying their app on a device or submitting it to the AppStore. This requires navigating the complex Developer Portal website to generate certificates and provisioning profiles. Reading tons of tutorials and Googling the cryptic e
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く