Re: [Super-tux-devel] TODO 0.0.7
Brought to you by:
wkendrick
From: Michael G. <mi...@ge...> - 2004-03-17 21:09:01
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Christopher A. Webber wrote: | On Wed, 2004-03-17 at 10:10, Ricardo Cruz wrote: | |>/ I would go with the following layers: |> |>- slower speed background (moving in a slower speed than the games one); |>- normal speed background (moving in normal speed); |>- normal tiles - the ones that Tux has interaction with; |>- normal speed foreground; |>- slower speed foreground. |> |> Maybe we could have 3 layers of backround and foreground. |> A part from this, there would be a static image or color for the background |>and the moving platforms and bad guys./ |> | | I thought quite a bit a bout this, and I realized that we don't even | need to set how many there are going to be. All we need to do is have | two definite ones: background and foreground. Users can set on their | levels extra layers that either fit between the background and the | foreground or lie above the foreground. The speed on these should not | be hard-coded, it should be set by the user. | It might sound complicated, but it really isn't. Just have the layers | work via a linked list and have each (besides the foreground) have its | own variable for its relative moving speed. | We can use this later to also add an extra layer where lightning effects | and such are placed. | Anyway, that's what I think would be best. | | Christopher Allan Webber | | | | | The bottom line I like this idea, but would like to add that a fore-fore-ground list is also necessary for some of the desired effects (stuff that isn't interactive, but is painted on top of the active layer). Also, are these layers going to be tile-based, or one big looong png file? I can certainly see advantages and disadvantages both ways. - --Mike -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFAWL/KrJDiig1GCW0RAvzvAJ4mpN1k/hRsP8CwuGjusxUpIGUDjACfZOKq DOZLYRZG5gJ35VeNoiQmW+0= =WRMc -----END PGP SIGNATURE----- |