SoC Ideas SpriteSheets2014 - Revision history

Timotei21: Fix category dpl

2014-03-12T23:19:13Z

Fix category dpl

Aishiko: /* SpriteSheet */

2014-03-01T21:01:44Z

‎SpriteSheet

Aishiko: /* SpriteSheet */

2014-02-28T21:38:15Z

‎SpriteSheet

Shadowm: /* SpriteSheet */ Fixed link

2014-02-14T23:05:09Z

‎SpriteSheet: Fixed link

Shadowm: /* SpriteSheet */ Style, punctuation

2014-02-14T22:30:26Z

‎SpriteSheet: Style, punctuation

Shadowm: MediaWiki discourages using = for first-level headers

2014-02-14T22:13:40Z

MediaWiki discourages using = for first-level headers

SkeletonCrew: Added spritesheet page

2014-02-12T20:12:42Z

Added spritesheet page

New page

{{SoC2014Idea}}

=Description=
<h2>SpriteSheet</h2>
Page for the idea: [[SoC_Ideas2014_Template]]

Wesnoth uses a thousands of images, that are all stored in separate files.
It would be more efficient to store multiple images in a single file. In order
to make that possible the Wesnoth engine needs to be adapted to allow this change.

{{#dpl:
|resultsheader=''There are %PAGES% submitted student proposals for this idea''
|oneresultheader=''There is 1 submitted student proposal for this idea''
|suppresserrors=true
|noresultsheader=''There are no submitted student proposals for this idea''
|category=Summer of Code 2014 Student Page&SoC Ideas IDEA NAME
|notcategory=SoC 2014 Not Submitted To Google
|include=#Description
|nottitlematch=SoC2014_Template_of_Student_page
|mode=userformat
|format=,,<br/>See [[%PAGE%|%TITLE%]] for more information.<br/><br/>,
}}

=Additional Information=

Currently, all the Wesnoth unit animations are based on thousands of small png
images, each image representing the unit in a single pose. For terrains the
situation is the same, it has a base image with a lot of transitions to other
terrains, which are now stored as seperate images.

In a sprite sheet approach, each unit is represented by a single, huge, image
where all the unit images are put on a mosaïc pattern and the game knows where
to look for a given image.

The advantage of having a large image with all positions is that it's more
efficient in memory. Also one large file is more effecient on the harddisk and
faster to load than a lot of smaller files. So the change to spritesheets will
have a lot of advantages. Also several Wesnoth artists prefer using sprite
sheets over multiple single images.

This project involves changing the Wesnoth Markup Language (WML)* definition
for images to specify a sub image in a sprite sheet and change the image loading
code of the engine. Creating tools to transform existing images to a sprite sheet
can be an optional objective.

Regarding the implementation the student is free to come up with his/her own
solution and discuss that with the developers during the application period.

*) WML is a XML like language, used to describe the data/content of Wesnoth.

=Whom to ask about this=

mordante on IRC.

@@ Line 21: / Line 21: @@
   |format=,,<br/>See [[%PAGE%|%TITLE%]] for more information.<br/><br/>,
 }}
 ==Additional Information==

@@ Line 21: / Line 21: @@
   |format=,,<br/>See [[%PAGE%|%TITLE%]] for more information.<br/><br/>,
 }}
 ==Additional Information==

@@ Line 3: / Line 3: @@
 ==Description==
 ===SpriteSheet===
-Page for the idea: [[SoC_Ideas2014_Template]]
+Page for the idea: [[SoC_Ideas_SpriteSheets2014]]
 Wesnoth uses thousands of images, each of them stored in separate files.

@@ Line 14: / Line 14: @@
   |suppresserrors=true
   |noresultsheader=''There are no submitted student proposals for this idea''
-  |category=Summer of Code 2014 Student Page&SoC Ideas IDEA NAME
+  |category=Summer of Code 2014 Student Page&SoC_Ideas_SpriteSheets2014
   |notcategory=SoC 2014 Not Submitted To Google
   |include=#Description

@@ Line 5: / Line 5: @@
 Page for the idea: [[SoC_Ideas2014_Template]]
-Wesnoth uses a thousands of images, that are all stored in separate files.
+Wesnoth uses thousands of images, each of them stored in separate files.
 It would be more efficient to store multiple images in a single file. In order
-to make that possible the Wesnoth engine needs to be adapted to allow this change.
+to make that possible, the Wesnoth engine needs to be adapted to allow this change.
 {{#dpl:

@@ Line 1: / Line 1: @@
 {{SoC2014Idea}}
-=Description=
+==Description==
-<h2>SpriteSheet</h2>
+===SpriteSheet===
 Page for the idea: [[SoC_Ideas2014_Template]]
@@ Line 22: / Line 22: @@
 }}
-=Additional Information=
+==Additional Information==
 Currently, all the Wesnoth unit animations are based on thousands of small png
@@ Line 49: / Line 49: @@
 *) WML is a XML like language, used to describe the data/content of Wesnoth.
-=Whom to ask about this=
+==Whom to ask about this==
 mordante on IRC.