Last updated at 2:05 pm UTC on 16 January 2006
Subclass of Object.
Classic model, which keeps a list of dependents.
Put notes here about the use of this class:
From: Mark Guzdial
Subject: Re: [newbie]Does Model + Morphic = MVC?
Date: Fri, 22 Feb 2002
We recently found a really important reason to subclass Model instead of Object for your models. If you're going to use dependencies AND you want to save your system as a Project (.pr) file, then subclassing Object will break all your dependencies. The global system dependencies are NOT saved with the Project. But if you subclass Model, all your dependencies are stored within objects, so the saving to Projects works just fine.