Forcing a crash is a great way to test out the SDK, but is actually a little more tricky than you might think. 强制crash是很好的一种测试SDK的方式，但实际上是一个比你想象的更棘手一点。 How to force a crash We've built

Today i continued working on some RoboVM backend todos. Multi-touch is now working properly, the fix was rather simple, once you understand that you have to enable multi-touch on a view in a single line of code on iOS. 今天我继续工作在一些RoboVM后台待办事项上。 多点触控 现在完

A couple of quick updates. First of all, you can track the progress and todos on the RoboVM backend in this file. 一对快速更新。首先，你可以在这个文件中跟踪RoboVM后台进度和待办事项。 A couple of bugs have been fixed, including Preferences and various

To all watchers of the libgdx repository: i’m terribly sorry and hope i didn’t interfer with your work in any way

致libgdx资源库的所有关注者：我非常抱歉且希望我没有以任何方式干涉到你的工作。

This is meant as a cautionary tale about using Github’s API on a repository with quite a few watchers (460 in this case).

这是一个警示的故事通过在资源库上使用Github的API针对不少的关注者。（这个案例中是460）。

Earlier this year we migrated our code from Google Code to Github. We didn’t have a good migration plan for the 1200 or so issues back then, so we kept them on Google Code. We now have about 1700 issues on the tracker

今年早些时候我们从Google Code迁移我们的代码到Github。我们没有一个好的迁移计划去迁移1200个左右问题，因此我们保持他们在Google Code上。我们现在有大约1700个问题跟踪。

Today i finally wanted to tackle the issue tracker migration, using a Python script i found on Github. The script requires one to specify a Github user account that owns the repository the issues will get migrated to. I did a dry run on a fork of the main repo using my Github account, fixed up some issues in the script, and validated things to the best of my abilities. Things looked good.

今天我最终想去处理问题跟踪迁移，用一个我在Github上找到的Python 脚本。这个脚本必须指定一个我们将迁移到的自己资源库的Github 用户账号。我用我的Github账号在主资源库的一个fork上做了一个枯燥无味的运行，在这个脚本里解决了一些问题，且尽我最大的能力进行了验证。事情看起来挺好。

Then i ran it on the main repository. Luckily i was watching our IRC channel. After about 4 minutes, people started to scream. They each received 789 e-mails from Github. Every single issue i migrated, and every single comment of each issue triggered an e-mail notification to all watchers of the main repository.

然后我运行它在主资源库上。幸运地我一直在看我们的IRC渠道。大约4分钟后，人们开始尖叫。他们每个人都收到来自Github的789封邮件。每一个我迁移的单一issue，并且每一个issue的每一个单一注释触发一封邮件提醒给主资源库的所有关注者。

This wasn’t apparent to me during the dry runs, as i used my own Github account. The script posts all issues/comments with the user account i supplied, so naturally, i did not get any notification mails.

这个枯燥无味的运行对我来说不是显而易见的，作为我用我自己的Github账号。这个脚本用我提供的用户账号发布所有的问题或评论，所以自然地我没有接收到任何提醒邮件。

I stopped the script after 130 issues (4 minutes), and immediately started sending out apologies and a mail to Github support, to which i haven’t received an answer yet. I send roughly 300k mails through their server in a matter of minutes. If i hadn’t watched IRC, i’d have send out about 4 million mails to 460 people within an hour.

我在130个问题(4分钟)后停止了这个脚本，并且立即开始发送道歉还给Github支持一封邮件，我还没有得到答案。我通过他们的服务器在短短几分钟内就发送了大约30万封邮件。如果我没有看IRC，我肯定会在一小时内发送大约400万封邮件给460个人。

We are cleaning up the core a little, and in the process eliminate usage of Java collections and replacing them with our own collections. 我们正在清理核心的一点，并在这个过程中用我们自己的集合去替换和消除使用的Java集合。 One of our

A little less than a year ago, we moved all our code from Google Code to Github. That was a nerve racking but ultimately beneficial task. Since our move, we had almost 600 pull requests! 不到一年前， 我们迁移Google Code上所有代码到Github。它是

原文链接：http://www.badlogicgames.com/wordpress/?p=3166 NextPeer is a service for creating synch and asynch multiplayer games, with tons of features. The big differentiator between

在用libgdx游戏引擎进行案例开发时，遇到以上问题，google，stackoverflow.com,github.com/&hellip

原文链接RoboVM backend in libgdx nightlies and first performance figures!

翻译原文链接：http://www.maiyang.me/posts/2013/09/12/robovm-backend-in-libgdx-nightlies-and-first-performance-figures

简单翻译一下，如果有任何错误或不对的地方，请指正。

I’ve spent the weekend integrating the libgdx RoboVM backend into our build as well as the setup-ui. I’m happy to report that both tasks have been completed! If you want to give it a spin, here’s what you need to do:

我耗费了整个周末将libgdx RoboVM后台不仅集成到我们的构建里而且还有setup-ui。我很高兴向大家报告，这两个任务都已经完成了！如果你想用它，下面是你需要做的：

• Get a Mac, you can only develop for iOS with a Mac. This also includes getting a developer certificate from Apple if you want to test on a device. Sorry, blame Apple

• 获取一个Mac,你仅仅能在Mac上开发iOS.如果你想在设备上测试，你还要从苹果获取一个开发者认证。 对此我很抱歉，归咎于苹果。

• Install the necessary prerequisits. For RoboVM that means installing an Eclipse plugin, from this plugin URL: http://download.robovm.org/eclipse/ and installing XCode on your Mac. That’s it!

• 安装必要的prerequisits。为了RoboVM意味着要安装一个Eclipse插件， 插件URL：http://download.robovm.org/eclipse/ 并且在你的Mac上安装XCode. 就这样!

原文链接THE FUTURE OF LIBGDX ON IOS

翻译原文链接：http://www.maiyang.me/posts/2013/09/11/the-future-of-libgdx-on-ios

简单翻译一下，如果有任何错误或不对的地方，请指正。

The latest Xamarin update, which brought us Mono 3.0, breaks our libgdx iOS backend. More precisely, it breaks the IVKM Monotouch port by Michael Bayne, on which we rely to run our JVM bytecode on iOS. Michaels already working fixed up most things, but there are still some bumps on the way to a fully working version, which requires the assistance of Xamarin.

最新版的Xamarin带来了Mono 3.0,破坏了我们的libgdx的iOS后台，更确切的说，它打破了Michael Bayne的IVKM Monotouch的端口。 我们依靠在iOS上运行的JVM字节码。Michael已经修复很多事情，但仍然有一个完整的工作版本需要Xamarin去协助，在过程中有些颠簸。

Seeing how every update of Xamarin breaks our iOS backend, i can no longer promote this solution with good conscience. My skills and time budget are insufficient to support Michael, and not being able to fix things myself makes me really uncomfortable. The code i contributed to IKVM Monotouch was trivial compared to what Michael pulled off.

看到Xamarin每次更新如何打破我们的iOS后台，我再也不能具有良好的良知来推动这个解决方案了。我的技能和时间预算不足于支持Michael，不能够自己解决的事情，我真的很不舒服。相较于Michael的努力,我对IKVM Monotouch编程的付出简直是不值一提。

For this reason i’m announcing the deprecation of the Xamarin based iOS backend. Here’s how that will go down: We’ll push out the 0.9.9 release in the coming weeks, containing the stable IKVM monotouch port that is compatible with the previous release of Xamarin iOS (6.2.7.1). We’ll tag the release as always, the remove any signs of the Xamarin backend from the repository as well as our build system. This will simplify our build considerably We’ll create a replacement for the setup-ui, which is long overdue, and update the documentation were necessary. If you are currently working on a game, you should avoid updating to the latest Xamarin iOS version. Stick to libgdx 0.9.8, or the upcoming 0.9.9, or any nightly release in between those two versions.. If you already updated Xamarin iOS, you can downgrade to a working version (6.2.7.1 pkg) as discussed in this issue. We will start packaging the RoboVM backend starting with 0.9.9, which should now have feature parity with the Xamarin backend, thanks to a metric ton of hard work by Niklas Therning, creator of RoboVM. You should be able to “port” your game to that backend without huge problems (ymmv).

出于这个原因，我宣布弃用Xamarin基于iOS的后台。 这里，将如何往下走：

在未来几周内，我们将推出0.9.9版本，含有稳定的IKVM MonoTouch的端口，兼容以前的版本（6.2.7.1）Xamarin的iOS。 我们会标记release，一如既往地删除任何迹象Xamarin后端的储存库，以及构建系统。这将相当简化我们的构建。 我们将为setup-ui创建一个更换，这是期待已久的更换和更新的文件是必要的。 如果您目前正工作在一个游戏上，你应该避免更新Xamarin到最新的iOS版本。坚持libgdx0.9.8或0.9.9的到来，或任何在这两个版本之间的nightly release..如果您已经更新Xamarin的iOS，你可以降级到一个工作版本（6.2.7.1 PKG）在这个问题上讨论。 我们将从0.9.9开始包装RoboVM后端，现在应该有奇偶校验功能与Xamarin后端，谢谢由RoboVM的创作者Niklas Therning付出的巨大努力。你应该没有很大的问题就能够“移植”你的游戏（因人而异）。