SummerOfCodeIdeas

From The Battle for Wesnoth Wiki
This page is related to Summer of Code 2010
See the list of Summer of Code 2010 Ideas



I want to be one of your Google Summer of Code students, what should I do...

Here is a quick list of things to do to get you started

  • MOST IMPORTANT Join the irc channel (#wesnoth-dev on irc.freenode.net) and introduce yourself. We will not give formal interviews, but we will clearly favor people we have learned to know during the selection process (basically communication via IRC is mandatory for our project! it is the main way of "every day communication" for Wesnoth. For the same reason, it's also a good idea to regularly read the IRC logs.).
  • VERY IMPORTANT Start a wiki page about your idea:
    • copy-paste the source of SOC_Template_of_Student_Page to a new page, picking a suitable name for it. Please include either your real name or your irc nickname as part of your page title. For example: SummerOfCodeProposal_Nickname Through the {{SoC2010Student}} template, your page will be included in the 'Summer of Code 2010 Student Page' category, and, your page will appear in the list of student pages at the end of this page.
    • List your account names (gna.org, forum.wesnoth.org, irc nick) so that we can recognize you
    • Fill the questionnaire.
    • Detail your idea as much as possible, look at other students pages, and please give milestones and studies you've done
  • Create an account on gna.org (required for committing later on)
  • Create an account on the wesnoth forum, and tell an admin of the forum or leader of the group on the IRC channel to mark it as a GSoC Student account (admins/group leaders are: Boucman, Crab, fendrin/Fabi, Ivanovic, Mordante/SkeletonCrew, Noy, shadowmaster, Sirp/Dave, Soliton)
  • Though not mandatory, it is highly advisable to go to the EasyCoding and NotSoEasyCoding pages and implement one of these ideas (or any idea of similar scope) so we have an idea how you work. Be sure to use your gna account when submitting these patches so we know who it is coming from. You can also implement some features from our feature request database at gna. When you implement something, also list it on your own page with a reference to the patch. This should give you a good idea what the Wesnoth sourcecode is like and will provide a good start to getting used to our coding style, too.
  • Once you have everything done here and think your idea is okay, go to page at google to submit your application. You have to submit it before April 9th at 19:00 UTC (12:00 noon PDT) or you have no chance to get in!

List of Ideas for the Project (Suggestions from wesnoth developers)

NOTE: this list of ideas is automatically generated from the 'description' section of pages in Summer of Code 2010 Idea category. DO NOT TRY TO EDIT THIS LIST BY HAND - IT WON'T WORK. INSTEAD, CREATE A NEW PAGE WITH THE {{SoC2010Idea}} template.


Create an eclipse plugin for wesnoth UMC development

Page for the idea: SoC_Ideas_Eclipse_Plugin

We want to use the eclipse platform as the IDE to assist Wesnoth UMC (user-made-content) Development. To do that, we need to create an eclipse plugin which will allow to rapidly start UMC development and which will act as a frontend for existing wesnoth UMC development tools. To do so, we need to try to integrate existing solutions as much as possible.

There are no submitted student proposals for this idea
See SoC Ideas Eclipse Plugin for more information.

Port Wesnoth input framework to a more flexible system

Page for the idea: SoC_Ideas_Gui2_Input

Since 2007, Wesnoth has been rewriting its GUI system with a more flexible system allowing all user interface aspect to be specified through WML. One of the changes has been to change the GUI input system. The input system still only support keyboard and mouse. With the rise of the more powerful hand-held devices(hand-held game consoles and phones) Wesnoth gets ported to these devices as well. The scope of this SoC project is to add more different kind of input devices like pads and touch screens.

There are no submitted student proposals for this idea
See SoC Ideas Gui2 Input for more information.

Extend Wesnoth Lua AI Support

Page for the idea: SoC_Ideas_Lua_AI

Lua AI support was recently added to wesnoth. Expose c++ AI support functions that Wesnoth has, to Lua.

There are no submitted student proposals for this idea
See SoC Ideas Lua AI for more information.

Rewrite wesnoth network stack using boost::asio

Page for the idea: SoC_Ideas_Network_Stack_Rewrite

Rewrite wesnoth network stack using boost::asio.

There are no submitted student proposals for this idea
See SoC Ideas Network Stack Rewrite for more information.

New Alliance system

Page for the idea: SoC_Ideas_New_Alliance_System

Wesnoth currently has a very simple alliance system, players are either allied, neutral, or enemies. The idea is to replace this with a system of privilege granting. Each player can grant privileges to other players but can't force other to grant the corresponding privilege. Thus it's only through diplomacy and trust that you can build an alliance.

There are no submitted student proposals for this idea
See SoC Ideas New Alliance System for more information.

Implement persistent storage of gameworld data between semi-related scenarios

Page for the idea: SoC_Ideas_Persistent_Gameworld

Allow WML authors to store/access persistent data 'in context' of a specific campaign/add-on/group of addons/ group of games. This will allow things like 'achievements' or 'massive multiplayer campaigns' to work.

There are no submitted student proposals for this idea
See SoC Ideas Persistent Gameworld for more information.

Allow wesnoth to support spritesheets

Page for the idea: SoC_Ideas_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

There are no submitted student proposals for this idea
See SoC Ideas SpriteSheets for more information.

WML Debugging Support

Page for the idea: SoC_Ideas_WML_Debugging

Improve the ways to debug Wesnoth's domain-specific language, WML.

There are no submitted student proposals for this idea
See SoC Ideas WML Debugging for more information.

Make your own ideas

Page for the idea: SoC_Ideas_Your_Own_Ideas

If you have your own idea the best thing is to join IRC wesnoth-dev at irc.freenode.net and discuss the idea with the developers there. If the developers think your idea is interesting and like the feature you can start to turn it into a full proposal. Once done discuss it again on IRC so the developers can accept your idea.


There are no submitted student proposals for this idea
See SoC Ideas Your Own Ideas for more information.

Information about our Project

The information we provided google with about our project can be looked up at the site SoC Information for Google.

Also see the DeveloperResources link (from the Project page).

People to bug on IRC

We have prepared a list of people with their "area of competence". This is to give you an idea on which areas those people can be of help for you. Of course you should always just ask in the IRC chan, but those are the most likely ones to answer questions in the respective area. And here is the list:

SoC People to bug on IRC

Student pages

NOTE: this list of student pages is automatically generated from the 'description' section of pages in Summer of Code 2010 Student Page category. DO NOT TRY TO EDIT THIS LIST BY HAND - IT WON'T WORK. INSTEAD, COPY-PASTE THE SOURCE OF SOC Template of Student Page TO A NEW PAGE. Please include either your real name or your irc nickname as part of your page title. Example of page title: SummerOfCodeProposal_Nickname


TODO: Copy this page and write your proposal summary in it

TODO: Write a small (1-4 sentences) description of your proposal here.
See A SoC Template of Student Page for more information.

xxx - Extend Wesnoth Lua AI Support

I would like to make a simple but efficient interface in which Lua scripts can be easily integrated/edited/removed from the existing C++ core AI system, without effecting existing code. This would allow me to code the AI scripts faster and allow other developers to continue the modification of the AI system later as well.


See SummerOfCodeProposal Achilles Lua for more information.

Awilkins - Improve Upon WML Debugging

I plan on fixing the incorrect error messages returned by the misuse of macros in WML files. The fixed error messages will display the accurate file and line number of where the macro was called incorrectly.
See SummerOfCodeProposal Awilkins for more information.

Billynux - Rewrite Wesnoth network stack using boost::asio

  • email : billybiset@gmail.com
  • irc : billynux
  • gna.org : billynux

The project consists of developing a network framework in the form of an API and subsequently an implementation that can be distributed as a library for the development of client/server applications. This library will be used to implement Wesnoth's network stack.
See SummerOfCodeProposal Billynux for more information.

ctrlfreak - Improve WML debugging support

I plan to modify the debugging code to contain clearer error messages which pinpoint the exact location and line number where the errors occur. I also intend to improve the infrastructure for errors to make it more modularized and easily extendable/externally accessible.
See SummerOfCodeProposal ctrlfreak for more information.

Dakmor - Porting Wesnoth input framework.

TODO: Add a description of my proposal.
See SummerOfCodeProposal Dakmor for more information.

Darkas - Extend Wesnoth Lua AI Support and write a "defend" AI

The first part of the proposal is described at SoC_Ideas_Lua_AI. So if the AI is exposed to lua and works, the AI should get 2 more features: defend effectively (shield wounded units, line up to get less attacks if there are more enemies, etc.), and decide when it's time to defend (this is per unit, so if there's a group of units that gets attacked, they'll be defenders now, but other unit may remain attacker). If that's done, the AI should also be able to do some missions better, if they should protect something for example, then they'll defend this special place or unit, instead of attacking the others and hoping they won't get there.
See SummerOfCodeProposal Darkas for more information.

fakedrake - WML Debugging

I am most interested in patching the code to output accurate line numbers along with the errors and improving the error messages themselves. After that i most probably will have time to make a schema system.
See GSoC-WMLDebugingSupport fakedrake for more information.

Kahowell - Making the Wesnoth Input Framework More Flexible

This would involve learning about the current state of the Wesnoth input system, and creating an input layer which is highly portable between different sorts of devices. Since Wesnoth already uses SDL, this project would mainly involve creating a subsytem to enumerate input devices and create a default configuration. I will look into different ways of identifying input devices (hopefully cross-platform), and perhaps create a database of default configurations (most likely just a collection of files). This project would also involve creating a dialog for input configuration.
See SummerOfCodeProposal Kahowell for more information.

Luca Moller - Make the c++ AI functions avaiable through the lua engine

Working with lua and C++ bindings and with the already existing core functions, the idea of the project is to expose the remaining AI functions avaiable in C++. Everything that can be seen by the AI through C++ should also be seen by an AI implemented through a lua script. The final result would also include higher level AI functions to make it easier to scenario developers to set how they want the units in the scenario to act.
See SummerOfCodeProposal LucaMoller for more information.

Orfest - Rewriting network stack

gna.org : orfest
irc : orfest

I am really interested in rewriting network stack using boost::asio. This task will not only improve the current network stack implementation but will also bring new features such as proxy support, configurable timeout values for connections, connection multiplexing on the client.

Please see more details on my page.
See SummerofCode Orfest for more information.

Truongan - extend wesnoth lua ai support

Extend Wesnoth Lua AI Support
See SummerOfCodeProposal Truongan for more information.

This page was last edited on 28 March 2010, at 13:29.
Cookies help us deliver our services. By using our services, you agree to our use of cookies.