Instructor: Tom O'Connor

Syllabus

• Review Lecture and Project milestone schedule
• Attendence Requirements
• Accessibility

Required Class Textbooks

We'll be mostly working out of the first book

• Pascal Rettig, Professional HTML5 Mobile Game Development, 2012 Wrox Press, Inc. (ISBN 978-1-118-30132-6)
• Jacob Seidelin, HTML5 Games: Creating Fun with HTML5, CSS3 and WebGL, 2012 John Wiley and Sons (ISBN 978-1-119-97508-3)

Supplementary Textbooks

These are the same from the first class. useful things to have around

• David Geary, Core HTML5 Canvas: Graphics, Animation, and Game Development, 2012 Prentice Hall (ISBN 978-0-13-276161-1)
• Douglas Crockford, JavaScript: the Good Parts, 2008 O’Reilly (ISBN 978-0-596-51774-8)
• Sergey Mavrody, Sergey's HTML5 & CSS3 Quick Reference, 2012 Belisso Corp. (ISBN 978-1-468-15007-0)

Class Structure

• Lectures - Relevent materials to your project, demonstration code
• Presentations - Everyone will present their games every other week for each of the 5 milestones
• Lab - Time in class to work on your projects, get help from the instructor and your cohort, do code reviews

Class Project

Development Environment

Check out the Chapter 7 in Rettig

Local Web Server

Even for local testing you'll need to run a web server (can't do AJAX without it). An easy tool is Mongoose, which is a standalone executable.

By our Alpha milestone we will need to have our games hosted online. Online web hosting service TBD (I'm still researching)

Source Version Control

It is going to be required that we use a service like BitBucket or GitHub for storing your repository online, because that's how you will submit your code.

I recommend using Git for source control. A wonderful tutorial can be found at http://gitimmersion.com/

Both sites also support Mecurial, a similar source control system.

Git Concepts

• git add - add files to be committed (-u switch to add all changed files)
• git rm - mark files to be deleted from source controls (. to remove all deleted files)
• git commit - commits any changes under a new revision number (-m switch to add a comment)
• git remote add origin - sets the online server to be your BitBucket address
• git push - sends your latest committed code to the server (BitBucket, will require you type in your password)
• git status - displays the status of any changed/added/deleted files

Adding your project to BitBucket with Git

Adding your project to BitBucket

1. download a Git client (http://git-scm.com/download)
2. Use command line in the directory where your source is at
   1. Use "git init"
   2. Use "git remote" to link to server
   3. Use "git commit" to commit changes to local source control
   4. Use "git push" to
3. Setup BitBucket
   1. Create a BitBucket account
   2. Choose "Create Repository"
   3. Add code to your repository:
      • Chose "I'm starting from scratch"

        								cd /path/to/your/project to get this sample code
        								git init
        								git remote add origin https://magicchicken@bitbucket.org/magicchicken/temp-please-delete.git
        							

      • Choose "I have code I want to import" to get this sample code

        								cd /path/to/my/repo
        								git remote add origin https://magicchicken@bitbucket.org/magicchicken/temp-please-delete.git
        								git push -u origin --all   # to push changes for the first time
        							

Pending Notes (check back soon!)

How to compare versions of files, check file history, etc

GUI clients for Git

Forking, Cloning

Production - Task Tracking

Keep track of features you need to work on, and estimate how long they will take.

• Breakdown into detail as much as possible
• You're not going to be good at estimates, but that's okay.
• Track and record how long it actually takes, then you'll get better at making estimates over time. This also helps me know how long things are actually taking you guys.
• It's an important habit to develop: thinking about the big picture, breaking it down into tasks, thinking about how to dissect a problem, transparency when working on a team, etc.

You can use whatever you want: JIRA, Trello, Asana, a text file in your repository, a notebook with little checkboxes, doesn't matter to me.

I'll be using Workflowy because it fits with my own work-style (putting things into lists)

Sites like BitBucket and GitHub have built in task tracking software