If you create your first classes you will get it wrong I am pretty sure.
First of all, use objects to describe data. This is trival and most people understand it very quickly, that's why the courses start with sutff like
class Animal
//some trivial shit about animals
class Dog: Animal
//some trivial shit about dogs
class Cat: Animal
//some trivial shit about cats
Etc. The problem is thinking these examples (Dog: Animal, Cat: Animal) teach you a lot about OO, and to stop there.
You can learn a lot more if you inherit real classes, and understand what it entails and what you be achieved with it.
Lets say your first goal is to create 2 (or more) custom Forms that already have some buttons buttons and features, but also a common look and feel.
I think this would be a good task to understand what you can really do with inheritance, and also extremely useful for someone making a game.
//"Form" is a synonym .. whatever your target language provides as a "window"
class BasicCustomForm: Form
class CustomForm1: BasicCustomForm
class CustomForm2: BasicCustomForm
You could put basic stuff in "BasicCustomForm" which is for your own custom look and feel, and functionality.
a simple example
Code:
class BasicCustomForm
var Border
var Space
var BackColor
var ForeColor
var Font
and a method Format() that adjusts all Controls to your Style
Code:
public Format()
{
var x=Border
foreach Control c in this.Controls
{
c.Top = x
c.BackColor = BackColor
c.ForeColor = ForeColor
c.Font = Font
x=x+Space
}
}
Code:
class CustomForm1: BasicCustomForm
CustomForm1()
{
//add some controls
Format();
}
and the same for
Code:
class CustomForm2: BasicCustomForm
CustomForm2()
{
//add some controls
Format();
}
Hope you get the idea, I would recommend you examples like this and understand what you can really do with Objects.
Certainly not just model Cats and Dogs, this could already be done with ancient concepts like structs.
