[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-games-devel
Subject:    Re: [Kde-games-devel] GSoC Applicant Asking For Help
From:       Stefan Majewsky <stefan.majewsky () googlemail ! com>
Date:       2012-03-06 22:53:11
Message-ID: CACoMYZbWJ5x-RVxvsZRDnpd0bebi9q7pM-v0ow4hGH-SkYrhAA () mail ! gmail ! com
[Download RAW message or body]

On Fri, Mar 2, 2012 at 1:30 PM, Roney Gomes <roney477@gmail.com> wrote:
> I already worked with large applications, and by "large applications"
> I mean multiple files and more than 500 lines of code. The problem I
> see is that such applications had no other purpose than learn and see
> how some data structures work. I still remember the scary AVL trees.

You grow with your tasks. A typical game's code base is between 2 and
6 KLOC (KLOC = kilo LOC = thousand lines of code). However, you'll
find that a game consists of several areas which can be kept rather
separate if written carefully:

1. GUI chrome (main window, highscore dialog, etc.)
2. rendering the game view (loading images, arranging them on screen)
3. the actual game logic

For a simple game, the code size for these parts is something like
1:1:2. For parts one and two, use the right frameworks (cf. the other
games) and you're done. The third part is where you actually need to
take care since there are no frameworks for your problem-specific game
logic*, but then again this is also the kind of problem you should be
comfortable with according to your stated prior experience.

* Modulo domain-specific, yet general libraries like the upcoming libkcardgame.

Greetings
Stefan
_______________________________________________
kde-games-devel mailing list
kde-games-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-games-devel
[prev in list] [next in list] [prev in thread] [next in thread]