KDE Games/Kolf 2

From KDE Community Wiki
Revision as of 22:05, 3 January 2009 by Majewsky (talk | contribs) (update to r950202)

This page is intended to list the tasks that need to be done in Kolf 2.


Objects

This category contains everything related to the objects that appear on the course scene.

Status Classes Task description Assigned to
DONE Object
Overlay
Base class design
DONE Ball
Putter
Putting
TO DO Putter Advanced putting interface <nobody>
DONE WallObject
WallOverlay
Wall
DONE RectBlockObject
RectOverlay
Rectangle-shaped solid block
TO DO EllipseBlockObject Curved solid block (collision code missing) <nobody>
TO DO LandscapeObject Landscape (including puddles, slopes, etc.) as height map <nobody>
IN PROGRESS HoleObject The hole one has to reach
TO DO BlackHoleObject A black hole which moves you to another position of the scene <nobody>
TO DO WindmillObject A generic moving obstacle <nobody>
TO DO BumperObject Something that reflects the ball with increased speed when the ball touches it <nobody>

It may be that some objects are missing in this list. Do not forget to add these. (Of course, you can also add new objects that did not exist in Kolf 1.)

Engine

This category contains everything related to game management.

Status Classes Task description Assigned to
DONE Course course data management
IN PROGRESS Game game progress and scores (still to do: split class into abstract base class Kolf::Game and Kolf::NormalGame to make a Kolf::EditorGame possible)
DONE LocalPlayer support for local players

You are free to implement more player types, or even more game types (tournaments?).

Interface

This category summarizes work that is being done on the interface.

Status Classes Task description Assigned to
DONE MainWindow
View
basic interface classes
TO DO NewGameDialog a dialog to select a course and configure some game parameters <nobody>
DONE ScoreCard
ScoreView
a dock widget showing the game progress
DONE View2D top-down view
TO DO View3D three-dimensional view

Bigger tasks

This category contains all areas where work has not started yet. Once you start to work on this, it is recommended to split these areas into tasks.

  • editor interface
  • networking via GGZ