{"issue":{"state":"open","pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"user":{"avatar_url":"https://secure.gravatar.com/avatar/e620aac2ae74107613858a793cc0996a?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"e620aac2ae74107613858a793cc0996a","url":"https://api.github.com/users/jnaglick","login":"jnaglick","id":868189},"milestone":null,"labels":[],"assignee":null,"updated_at":"2011-10-29T14:34:29Z","comments":0,"closed_at":null,"url":"https://api.github.com/repos/jnaglick/ezrl/issues/2","body":"These classes are needed so freaking bad. They are just wrappers that give names to 2-tuples (pairs). Coordinate is for x/y, Size is for w/h, Range is for min/max. \r\n\r\nIt's debatable if you really need 3 different classes just for different names but I think that abstraction would be nice.\r\n\r\nRight now a ton of stuff is just passing around these paired-values, usually as multiple arguments to a method or as methods returning a python tuple. This worked for a while but I'm finally starting to see places where it's limiting code flexibility","html_url":"https://github.com/jnaglick/ezrl/issues/2","number":2,"title":"Create \"Coordinate,\" \"Size,\" \"Range\" classes","id":2087132,"created_at":"2011-10-29T14:34:29Z"},"action":"opened"}