Official Objective-C style guide for Kodeco (raywenderlich.com) focusing on readability for print and web.
The raywenderlich.com Objective-C Style Guide is a comprehensive set of coding conventions for Objective-C used by Kodeco's authors and contributors. It standardizes code style across books, tutorials, and starter kits to ensure consistency and readability, particularly for educational content in print and web formats.
Objective-C developers, especially those writing or contributing to Kodeco's educational materials, books, tutorials, or starter kits. It's also useful for teams seeking a readability-focused style guide for Objective-C projects.
Developers choose this guide because it's tailored for educational content, emphasizing readability and consistency across multiple authors. It provides clear, opinionated rules that help maintain code quality in print and online tutorials.
A style guide that outlines the coding conventions for Kodeco
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Details conventions for every aspect of Objective-C, from language usage to error handling, with clear 'preferred vs not preferred' code examples throughout the README.
Optimized for tutorial and book formats, using rules like 2-space indentation and consistent spacing to conserve print space and enhance learner comprehension online.
Informed by Apple's official documentation and reputable guides, ensuring adherence to modern Objective-C standards such as using NS_ENUM() and instancetype.
Created by multiple experienced Kodeco authors, providing a balanced set of conventions tested across books, tutorials, and starter kits for consistency.
Includes Kodeco-centric elements like the 'RWT' class prefix and whimsical rules (e.g., smiley face :]), which are not applicable or professional for external projects.
Rules such as 2-space indentation and avoidance of colon-aligning are designed for space conservation in print, potentially conflicting with digital-first or team-specific style preferences.
Opinionated dictates like always using dot notation for properties and forbidding the 'and' keyword in method names can clash with other guides or developer habits.
Does not address Swift or mixed-language development, limiting its relevance in modern iOS/macOS ecosystems where Swift is increasingly dominant.