<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array"/>
  <modified type="array">
    <modified>
      <diff>@@ -558,8 +558,8 @@ See http://www.libgosu.org/rdoc/classes/Gosu/Window.html for a full set of metho
 
 === How did you decide on naming of methods / classes?
 There's 1 zillion ways of naming stuff. As a general guideline I've tried to follow Gosus naming.
-If Gosu didn't have a good name for a certain thing/method I've checked Ruby itself and then Rails since alot
- of Ruby-devs are familiar with Rails.
+If Gosu didn't have a good name for a certain thing/method I've checked Ruby itself and then Rails since alot of Ruby-devs are familiar with Rails.
+GameObject.all is naming straight from rails for example. Most stuff in GameObject follow the naming from Gosus Image#draw_rot.
 
 == TODO:
 * add :padding and :align =&gt; :topleft etc to class Text</diff>
      <filename>README.rdoc</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>62df2a758bdb4ebb4c10780659ba7bb0aec46ddd</id>
    </parent>
  </parents>
  <author>
    <name>ippa</name>
    <email>iplord@iplord.com</email>
  </author>
  <url>http://github.com/ippa/chingu/commit/2c70414c59dae59021ddc6a570ff3085a0aecf71</url>
  <id>2c70414c59dae59021ddc6a570ff3085a0aecf71</id>
  <committed-date>2009-10-07T13:28:19-07:00</committed-date>
  <authored-date>2009-10-07T13:28:19-07:00</authored-date>
  <message>readme fixes</message>
  <tree>960909a37b5dc4ad2f192030b067359d6024baf5</tree>
  <committer>
    <name>ippa</name>
    <email>iplord@iplord.com</email>
  </committer>
</commit>
