Skip to content

zilongshanren/programmers-guide

Repository files navigation

Programmers-Guide

This is the Cocos2d-x programmers guide. It is licensed under the Creative Commons BY-SA license. You can find it here

Directory layout

  • blank.md - a blank page that is used when building print versions
  • build.sh - BASH script that build web and print versions, deploys to server
  • chapters - markdown content and images
  • mkdocs.yml - MKDocs configuration
  • outline.md - outline of what this guide covers (may be out of date)
  • README.md - this file :-)
  • theme - custom theme for web version

What do you need to build for OS X?

How to run/test

  • cd <where you cloned this repo>/programmers-guide
  • run mkdocs serve

Any changes made while mkdocs serve is running are automatically rebuilt.

How to build for deployment

  • cd <where you cloned this repo>/programmers-guide
  • run build.sh

Content is build in docs and deployed to site. This script also builds the ePub and PDF versions as well as deploys out to staging (slackmoehrle.github.io) and http://www.cocos2d-x.org/programmersguide

How to add new content

  • make sure to break lines at 80 columns.
  • chapters are actual book content while appendix are installation and tools
  • via a pull request. Please do not edit chapters directly.
  • If you are creating a new chapter, please don't make it feel and sound like an API Reference. This is a guide suited for new users (even though advanced users will benefit too). Please tell a story about your content. We want to make this engage the user. If in doubt: Read Chapter 2 and notice it feels like a chapter in a book.
  • Contact me via e-mail or on the forums to discuss what you want to add, edit, etc.
  • drafts are chapters that are under construction or review and not yet approved for the guide. (i.e new material). If you are adding to an existing chapter or appendix, please do so via a pull request.
  • each chapter has a markdown file and 3 image directories associated with it. The image directories are -web, -print and -img. -web is properly sized images for displaying on the web. print is properly sized images for displaying in the epub and pdf. -img is were to put the original images (also displayed when viewing from GitHub).
  • the build.sh script does copying and renaming of directories during the build process since the markdown files expects files at a specific path. Take a look.
  • If a chapter does not have any images there is no need to create directories for it.

cleaning up the build script

  • since I started this I know a lot more and want to clean up the build script to be generic and sub functions instead of a single long script. I plan to do this in the next version.
  • we will be moving away from pandoc in favor of PrinceXML to build the PDF.
  • we will be using grip to generate HTML output for the print versions.

I found an error

Conventions used in this book

  • auto is used for creating local variables.
  • using namespace cocos2d; is used to shorten types.
  • each chapter has a compilable source code sample to demonstrate concepts.

Outline.md - outline of what the guide will cover (may be out of date)

Appendices

Chapters

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published