Difference between revisions of "SoC Ideas SpriteSheets"
From The Battle for Wesnoth Wiki
m (→Description) |
m |
||
| Line 1: | Line 1: | ||
{{Template:SoC2010Idea}} | {{Template:SoC2010Idea}} | ||
=Description= | =Description= | ||
| − | + | <h3>Allow wesnoth to support spritesheets</h3> | |
Wesnoth units are made of thousands of small png files, each containing the image of the unit in a given stance. This has the advantage of (arguably) being easier for artists. However this has a huge cost in term of memory usage. The point of this SoC would be to allow wesnoth to support spritesheets : huge images containing a mosaic of all images and related tools/code support | Wesnoth units are made of thousands of small png files, each containing the image of the unit in a given stance. This has the advantage of (arguably) being easier for artists. However this has a huge cost in term of memory usage. The point of this SoC would be to allow wesnoth to support spritesheets : huge images containing a mosaic of all images and related tools/code support | ||
=Additional Information= | =Additional Information= | ||
Revision as of 22:22, 28 February 2010
| This page is related to Summer of Code 2010 |
| See the list of Summer of Code 2010 Ideas |
| This is a Summer of Code 2010 Idea |
Description
Allow wesnoth to support spritesheets
Wesnoth units are made of thousands of small png files, each containing the image of the unit in a given stance. This has the advantage of (arguably) being easier for artists. However this has a huge cost in term of memory usage. The point of this SoC would be to allow wesnoth to support spritesheets : huge images containing a mosaic of all images and related tools/code support