0.4 Xna0106-encapsulation in c#

Revised: Thu May 05 12:44:19 CDT 2016

This page is part of a Book titled XNA Game Studio .

Table of Contents

• Table of Contents
• Preface
  • The three main characteristics of an object-oriented program
  • Viewing tip
    • Figures
    • Listings
• General background information
  • Abstraction
    • How does abstraction relate to encapsulation?
    • Some analogies
    • A new type
    • Already known to the compiler
    • Not known to the compiler
  • Define data representation and behavior in a class
    • Create instances of the new type
    • Objects have state and behavior
    • The state and behavior of a GUI Button object
      • A C# class named Button
      • The state of Button objects
      • The behavior of a Button object
  • Encapsulation
    • Expose the interface and hide the implementation
    • Should be able to change the implementation later
    • Class member access control
      • Five levels of access control
      • A different interpretation
      • What is an assembly?
      • Public, private, and protected
    • A public user interface
    • A set Accessor method
    • A get Accessor method
    • Not a good design by default
    • Not bound to the implementation
• Preview
• Discussion and sample code
  • Will explain in fragments
  • Two classes
  • Will switch between classes
  • The declarations
  • Beginning of the class named Props01
    • Access a public instance variable in the object
    • Store a string value in the object's instance variable
    • Get and display the value in the object's instance variable
  • Beginning of the class named TargetClass
    • Declare a public instance variable
  • Different kinds of variables
    • Instance variables
      • The public access modifier
      • The private access modifier
      • The protected access modifier
    • Local variables
    • Class variables
      • More bad programming practice
    • Reference variables
    • Primitive variables
      • An analogy
  • Call the object's public accessor methods
    • The setColor method
    • The getColor method
  • Would be a property in Java
  • The definition of setColor and getColor in TargetClass
    • Typical method definitions
    • Data validation
      • What do you do with invalid data
      • Program output
    • Set, get, and display a property value with a valid value
      • Looks can be deceiving
      • A set Accessor method
      • A get Accessor method
      • The set Accessor and get Accessor methods for the property named height
      • A hidden parameter named value
      • Validating code
      • A read-only property
      • Little more to say about this
  • Call manipulator method and display results
    • A manipulator method named doubleHeight
  • Set and get the property with an invalid value
  • Pause until the user presses any key
  • The end of the program
• Run the program
• Run my program
• Summary
• Miscellaneous
• Complete program listing

Preface

This module is one in a collection of modules designed primarily for teaching GAME 1343 Game and Simulation Programming I at Austin Community College in Austin, TX. These modules are intended tosupplement and not to replace the textbook.