Storyboarding, scripting and learning outcomes

I have put aside the interface development for the past two days and have begun to explore ways to develop the learning outcomes of the game. Today I have been looking through the reading material recommended by Greg and have been noting key information that could be used to script the game. (i.e. information for splash pages, intro pages, tutorials and dialogue boxes throughout the game). I have also been identifying interesting ways that this information can be visually presented to the viewer. From this information I hope to generate a detailed script and storyboard for the game.

Mouse is partially-functional

The 'drag' coding in the mouses 'drag and drop' is functional. I now need to make particular 'drop' zones and get that part working. This is taking more time than originally anticipated but is a major factor in the game so needs to be sorted. Before I go any further I will sit down and try to define a general structure for all of the game code. Classes etc.

Interface under construction

Ariel plan

Drag and Drop Mouse

The idea of the mouse turning into the food as you need to drag and drop it to areas is nearly functional. By the end of today I should have it fully functional.

Coding

Working on using my own classes and objects within the playground project. Should be able to pretty soon.

Game Structure Diagram

Diagram

Made a diagram today that is a cross between a use case diagram and a flowchart. It gets the point across hopefully. The diagram highlights the general flow of the game and any major programming areas that need to be developed (and to remember all of them!). The diagram shall be uploaded when converted to digital form sometime during the day.

Programmers Funny Stuff

This is for someone who is coding this in the future, or for me to look back at when I'm finished coding. After some time trying to figure out how to change the cursor image and writing this :-
TPlatform::SetCursor( TTexture::GetSimple("cursor/cursor"), TPoint(2,2) );
I figured out it was this :-
TPlatform::GetInstance()->SetCursor( TTexture::GetSimple("cursor/cursor"), TPoint(2,2) );

...D'oh!

This is the first sketch of the proposed interface design. As you can see from the large amount of pencil notes, there are plenty of adjustments to make before we reach the final design.

Today i wrote up a detailed game scenario, and noted the functions required to complete one task within the game. Brendan looked over these notes and has been researching ways to programme key gameplay features.