[译]是否有快速强制Crash的方法?
[译]更多RoboVM后台更新
[译]RoboVM后台更新
[译]我如何通过GitHub的API在短短的几分钟内发送30万邮件
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个人。
[译]Box2D API的改变
[译]重大的libgdx问题跟踪和Wiki Github迁移
[译]Nextpeer拥抱GDX,GDX后面拥抱Nextpeer
Couldnt load shared library
[译]RoboVM后台在libgdx nighties里的第一次演示
原文链接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. 就这样!