Re: [Super-tux-devel] Release Schedule/Milestones/GotM

[Tobias <tob...@gm...>]

Am Mi, den 11.02.2004 schrieb Bill Kendrick um 15:56:
> On Wed, Feb 11, 2004 at 05:31:25PM +0100, Ingo Ruhnke wrote:
> > Tobias Gläßer <tob...@gm...> writes:
> > 
> > > Hey, backscrolling _is_ already possible. ./supertux --debug-mode.
> > 
> > The question is not so much if backscrolling is possible, but more if
> > we want or need it. With vertical scrolling its a must have, but with
> > just horizontal scrolling its not really important and doesn't provide
> > much advantages.
> > 
> 
> Not to repeat myself too many times, but I'm against 'backscrolling'
> in a game with Super Tux's theme.
> 
> My previous jump-n-run game, Bobobot, allowed going back (although it
> wasn't scrolling), but that's because there was no sense of urgency.
> 
> It was merely the entire world in danger, not your girlfriend. ;)
> Also, there was no timer.
> 
> 
> <snip>
> > >>  * create a little credits-screen/extro or something like that
> > > Dunno, if that's needed.
> > 
> > To make it short, its a must have. It doesn't has to be groundbreaking
> > or anything, but simply poping back to the start menu or something
> > like that after the last level looks just so damn broken.
> 
> I agree.  We do have the 'Intro', so it'd be nice to have something ot
> 'end the story  [... for now]' (cue evil music)
> 
> 
> <snip>
> > 0.2.x - changing the engine to handle features listed in the current
> >     Todo, break compability with 0.1.0 levels, basically creating a
> >     pretty different game.
> 
> This is where I would fork completely.  Hell, it might even make sense
> to just start from scratch for the 'next game.'  Definitely DON'T
> just jury-rig on top of the current codebase to make a completely
> different game.  There'll be a lot of picking and choosing, and throwing
> away of code, from the first 'version' to make the 'sequel,' and it makes
> no sense to do that INSIDE the original's code!
> 
> -bill!

I don't want to make a completely different game, when the 0.2.x development starts.
Many parts (not all) of the current codebase are well designed, so
that extending them makes sense.
Things like scripting and other stuff certainly will make their way into this
development branch and porting it to C++ will be an obvious step from
my point of view. This step won't be too hard, since I can compile and
link the current codebase on my working directory already with g++.

Greetz...

Tobias Gläßer