The document discusses object-oriented programming and some of its key concepts. It notes that classes have a name, attributes, a constructor, and methods. It also mentions that the major programming methodologies and mobile operating systems are based on objects. Experts say object-oriented programming should always be used. The document provides an overview of objects and programming with objects.

1. From last time…
•
We talked about classes and objects and built a
Star and StarManager class!
•
Classes have:!
! // 1. name
// 2. attributes (variables)
// 3. a constructor method (run via ‘new’)
// 4. methods (actions)

2. DevArt
https://devart.withgoogle.com

3. Objects II
CAP

4. The Object-Oriented Paradigm
http://www.youtube.com/watch?v=2kjtQnPqq2U

5. It can safely be said that the object has been
the driving force in the programming industry
for a very long time and will continue to be so
for the foreseeable future… today, just about
every major software development
methodology is based on objects.
Matt Weisfeld!
Author, The Object-Oriented Thought Process

6. Mobile OS
Primary Dev
Language
Android
Java
iOS
Objective-C
Blackberry OS
Java
Windows Phone
.NET (C#, Visual Basic)
These are all object-oriented languages.

7. “When should I use object-oriented programming?”
For me, the answer is always.
Daniel Shiffman!
Learning Processing

8. Red, Green, Refactor
Usually this applies to test-driven development…!
1. Red: decide what you want to do; your goals!
2. Green: using setup() and draw(),
write the code that satisfies your goals!
3. Refactor:!
! a. into variables and functions!
! b. into objects

9. Demo!
Night Sky

10. For next time…
•
Reminder: no class on Monday!
•
Continue work on Iteration 1!
•
Homework 2 due Wednesday!
•
Read Shiffman, p. 141–153 (Arrays I)