Changes

Under Construction

{{OOP344 Index | 20123}}

Your objective at this stage is to create series of core classes designed to interact with the user. These '''Core Classes''' then can be used in development of any interactive application.

It is highly recommended to develop the classes in the order they are stated here. You must create your own tester programs for each class (if possible); However, close to due date of each release, a tester program may be provided to help you verify the functionality of your classes. If tester programs are provided, then executables of the test programs will be available on matrix to show you how it is supposed to run.

Start by creating mock-up classes (class declaration and definition with empty methods that only compiles and don't do anything).

Each class MUST have its own header file to hold its declaration and "cpp" file to hold its implementation. To make sure you do not do circular includes follow these simple guidelines:

* Use includes only in files in which the actual header file code is used.

* '''Avoid "just in case" includes.'''

Use the following rules to create filenames for your class.

*Each class MUST have its own header file and cpp file for implementation

*Use the class name for the name of the file but make sure it is all lowercase.

*:For example '''CFrame''' class should have '''cframe.h''' and '''cframe.cpp''' files for its implementation.

<big><pre>

CFrame

</pre></big>

==CFrame==

The code for this class is provided in your repository. You must understand and use it to develop your core classes in your repository.