Design and Architecture

class Room {

public:
 void OpenWindow(int index)
 {
  try {
   // move plant pots out of the way
   plants[index].Remove();
   windows[index].Open();
   plants[index].Replace();

  } catch(DroppedPlantPotException& dppe) {
   // oops...
   CleanTheFloor();
  }
 }

private:
 std::vector<Window> windows;
 std::vector<PlantPot> plants;
};

public class Door
{
  public Door()
  {
  }

  public void Open()
  {
    _isOpen = true;
    Mediator.Instance.NotifyColleagues(DoorState.Open);
  }

  public void Close()
  {
    _isOpen = false;
    Mediator.Instance.NotifyColleagues(DoorState.Closed);
  }
}

public class House
{
  private int _ambientTemperature = 22;

  public House()
  {
    Mediator.Instance.Register((object o) => { _ambientTemperature -= 2; }, DoorState.Open);
    Mediator.Instance.Register((object o) => { _ambientTemperature += 2; }, DoorState.Closed);
  }
}

DiiJAY wrote:

Ok, So it will be a benefit to make nested classes private and create extra code for wrapper methods and events in the main class for this sort of architecture instead of make a direct connection to the Cpu object?

DiiJAY wrote:

will this even be true if I referenced Motherboard and Cpu as interfaces ?

Megidolaon wrote:

I can't really see the advantage of adding the methods for connecting to the db to the hotel class, but that would be actual oop, while I'm doing something close to procedural programming or?