Open main menu

CDOT Wiki β

Changes

The CUI Framework - OOP344 20132

3 bytes removed, 09:25, 25 June 2013
no edit summary
==Objective==
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.
* like any other implementation, these implementations could be buggy
==Tips==
* [[GIT for OOP344 Projects| Guide for using Github]]
Start by creating mock-up classes (class declaration and definition with empty methods that only compiles and don't do anything).
* '''Avoid "just in case" includes.'''
==CUI General Header file (cuigh.h)==
The general header file holds the common setting and definition between all the Core Classes. Review this header file at each stage of the project for changes.
<big><syntaxhighlight lang="cpp">
</syntaxhighlight></big>
==File Names==
Use the following rules to create filenames for your class.
*Each class MUST have its own header file and cpp file for implementation
*:For example '''CFrame''' class should have '''cframe.h''' and '''cframe.cpp''' files for its implementation.
==Hierarchy==
<big><pre>
CFrame
</pre></big>
==Issues, Releases and Due Dates==
*Issue Name Format
*:Issue and branch name format: '''V.V_Name''' <br />
*:example; issue: Add Text Class to the project (issue 2.9.1) issue and branch name on gitub: '''2.9.1_AddTextClass'''<br />
=Classes=
==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.