fix for issue #5 #15

Closed
wants to merge 1 commit into
from

Projects

None yet

3 participants

naming conventions for non-iOS framework Ruby methods

  • cleaned up Beer, Locations and GestureTable projects
  • cleaned up Mustache project
  • cleaned up Paint project
  • cleaned up Timer project
  • cleaned up Tweets project
  • cleaned up HelloGL project
@timbogit timbogit renaming non-overridden/non-iOS framework methods to follow Ruby conv…
…entions

- cleaned up Beer, Locations and GestureTable projects
- cleaned up Mustache project
- cleaned up Paint project
- cleaned up Timer project
- cleaned up Tweets project
- cleaned up HelloGL project
3065729
Owner
lrz commented May 18, 2012

I'm not super comfortable with this change. I don't think using camelCase is that bad here. What do you guys think?

I proposed this a while back (see issue #5), and it seemed that at that point in time only people agreeing commented ... hence the Pull Request. I personally it helps people (like me :-) who are not yet super familiar with the iOS framework to understand which parts of a project are purely implementing framework constraints. IMHO, it therefore improves readability of the examples.

Owner
alloy commented Nov 5, 2013

As described here we’re not going to enforce any style rules and so I think it}s ok if the samples reflect this.

In fact, having different styles in the repo might make it easier for people to determine what they like.

Thanks for the work, though!

@alloy alloy closed this Nov 5, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment