The Battle for Wesnoth Wiki - User contributions [en]

SpellingMistakes

2008-10-06T05:08:54Z

Xonev: /* Under the Burning Suns */

This page is meant to be a list for mistakes in campaigns and other texts in the en_US version of the game.

==An Orcish Incursion==

==Descent into Darkness==

==Eastern Invasion==

==Heir to the Throne==

==Liberty==

==Northern Rebirth==

==Sceptre of Fire==

==Son of the Black Eye==

==The Hammer of Thursagan==

==The Rise of Wesnoth==

==The South Guard==

==Two Brothers==

==Under the Burning Suns==
In the 6865th line:
"Give me until tomorrow night, then I'll tell you everything."

*This is a 'comma splice' - attempting to join together two independent clauses using a comma (''then'' is not a conjunction).
*It should be: "Give me until tomorrow night, and then I'll you everything" or "Give me until tomorrow night; then I'll tell you everything."

==Editor==

==Tutorial==

At the beginning of part II it reads "Right click on the tile south of you and recall <Name>". The problem is that the tile south is a road an no unit can be recalled there. The blue hint text "RECALL <Name>" is correctly placed at the north-east.
Same problem when recalling the second unit, the text says south-east and the blue hint is directly east.

':1376' BBeware of the Orc leader: he can do 36 hitpoints of damage at night! Attack with many units at once during the day.

BBeware->Beware

==Manual==

==1.4 Announcement==
#: ../template.html:111
"New maps and multiplayer campaigns: <cite> Auction-X, Dark Forecast Hamlets, "
"Mokena Prairie, The Manzivan Traps, Xanthe Chaos, </cite>. Revised maps: "
"<cite>Alirok Marsh</cite> (formerly <cite>Triple Blitz</cite>),<cite> "
"Amohsad Caldera, Blue Water Province, Castle Hopping Isle, Caves of the "
"Basilisk</cite> (formerly <cite>Blitz</cite>), <cite> Crossing, Crusaders "
"Fields, Cynsaun Battlefield, Den of Onis, Fallenstar Lake</cite> (formerly "
"<cite>Meteor Lake</cite>), <cite> Forest of Fear, Freelands</cite> (formerly "
"<cite>Charge</cite>),<cite> Hexcake, Hornshark Island, Island of the "
"Horatii, King of the Hill, Lagoon, Loris River, Merkwuerdigliebe, Morituri, "
"Paths of Daggers, Sablestone Delta, Siege Castles, Silverhead, Sulla's "
"Ruins, Waterloo Sunset, Wesbowl</cite>."
#Extra useless spaces in many places
#Missing comma before Hamlets
#Should be no comma and space after Xanthe Chaos
#Missing "Weldyn Channel" before </cite> (formerly <cite>Blitz</cite>)
#Missing "Siverhead" before Crossing

==Other (ingame help, ...)==

==Translation code bugs==

==Unofficial campaigns==

===Invasion from the unknown===

“King Asthorgar
Yes. The Scourt dwarf that went...
”

Maybe Scout?

[[Category:Troubleshooting and Bugs]]

SpellingMistakes

2008-10-06T05:07:40Z

Xonev:

This page is meant to be a list for mistakes in campaigns and other texts in the en_US version of the game.

==An Orcish Incursion==

==Descent into Darkness==

==Eastern Invasion==

==Heir to the Throne==

==Liberty==

==Northern Rebirth==

==Sceptre of Fire==

==Son of the Black Eye==

==The Hammer of Thursagan==

==The Rise of Wesnoth==

==The South Guard==

==Two Brothers==

==Under the Burning Suns==
In the 6865th line:
"Give me until tomorrow night, then I'll tell you everything."
This is a 'comma splice' - attempting to join together two independent clauses using a comma (''then'' is not a conjunction). It should be: "Give me until tomorrow night, and then I'll you everything" or "Give me until tomorrow night; then I'll tell you everything."

==Editor==

==Tutorial==

At the beginning of part II it reads "Right click on the tile south of you and recall <Name>". The problem is that the tile south is a road an no unit can be recalled there. The blue hint text "RECALL <Name>" is correctly placed at the north-east.
Same problem when recalling the second unit, the text says south-east and the blue hint is directly east.

':1376' BBeware of the Orc leader: he can do 36 hitpoints of damage at night! Attack with many units at once during the day.

BBeware->Beware

==Manual==

==1.4 Announcement==
#: ../template.html:111
"New maps and multiplayer campaigns: <cite> Auction-X, Dark Forecast Hamlets, "
"Mokena Prairie, The Manzivan Traps, Xanthe Chaos, </cite>. Revised maps: "
"<cite>Alirok Marsh</cite> (formerly <cite>Triple Blitz</cite>),<cite> "
"Amohsad Caldera, Blue Water Province, Castle Hopping Isle, Caves of the "
"Basilisk</cite> (formerly <cite>Blitz</cite>), <cite> Crossing, Crusaders "
"Fields, Cynsaun Battlefield, Den of Onis, Fallenstar Lake</cite> (formerly "
"<cite>Meteor Lake</cite>), <cite> Forest of Fear, Freelands</cite> (formerly "
"<cite>Charge</cite>),<cite> Hexcake, Hornshark Island, Island of the "
"Horatii, King of the Hill, Lagoon, Loris River, Merkwuerdigliebe, Morituri, "
"Paths of Daggers, Sablestone Delta, Siege Castles, Silverhead, Sulla's "
"Ruins, Waterloo Sunset, Wesbowl</cite>."
#Extra useless spaces in many places
#Missing comma before Hamlets
#Should be no comma and space after Xanthe Chaos
#Missing "Weldyn Channel" before </cite> (formerly <cite>Blitz</cite>)
#Missing "Siverhead" before Crossing

==Other (ingame help, ...)==

==Translation code bugs==

==Unofficial campaigns==

===Invasion from the unknown===

“King Asthorgar
Yes. The Scourt dwarf that went...
”

Maybe Scout?

[[Category:Troubleshooting and Bugs]]

User talk:Pintercsabi

2008-10-06T05:05:44Z

Xonev: Discussion of typo in SpellingMistakes

I have edited your typo notification from [[SpellingMistakes]]:

In the 6865th line: "Give me until tomorrow night, then I'll tell you everything."
What are they have to give to Kaleh? I think 'time' word is missing.

This is not correct English, but only because it is a comma splice. In other words, this an attempt to join together two independent clauses with a comma. What it needs is a coordinating conjunction.

EasyCoding

2008-05-14T02:05:24Z

Xonev: /* Make [removeitem] able to only remove a specific image */

== Foreword ==
This page is here to document easy to do coding tasks. It is not here to double the feature request database, and should only be filled by people that know the code well enough to judge the difficulty of a given task.

If you are such a person, you should feel free to edit this page.

If you're not, you should post a feature request and discuss your idea on the forum or IRC. A coder with better knowledge of the code might give you the green light to add your feature here.

Anybody should feel free to add "clues" to any tasks, that is entry points, traps to avoid, person to contact to discuss and so on.

If you plan to work on a feature, write your name at the bottom of the feature, with the date. Note that if you are too long at working on a feature I'll "free" it back (that is if you're not working on it. If you have problems implementing it, just tell us....)

--[[User:Boucman|Boucman]] 20:48, 3 October 2006 (CEST)

Since bugs are sometimes a good opportunity to get a first idea of the code, i will add some here that are easy to fix as soon as i stumble upon them (the one i had in mind is fixed already ;-).

--Yogi Bear, 28 February 2008

== MP related features ==

=== Add TTL to wesnothd bans ===
As per FR #3638 [https://gna.org/bugs/?3638]

''Working on it:'' Lao

=== Use different font for in-game chat ===
Since commas and dots are apparently hard to tell apart. As per FR #7470 [https://gna.org/bugs/?7470]

=== Allow lists for /ignore and similar ===
As per FR #7492 [https://gna.org/bugs/?7492]

== WML related features ==

=== Make [removeitem] able to only remove a specific image ===
Currently a [removeitem] always removes all images on the given hex. It should be made to support an image= key which, if given, would make it only remove that image. If not specified, then all images would be removed just like now.

--[[User:xonev|xonev]] 13 May 2008 - Patch submitted

=== WML configurable village income / upkeep ===
Preferably as a [scenario], [side] or [campaign] keys. As per FR #6301 [https://gna.org/bugs/?6301]

=== Add support of [if] for [scenario] ===
As per FR #4539 [https://gna.org/bugs/?4539]

=== Make [have_unit] optionaly use full SUF ===
[have_unit] by default uses SUF but does not apply it to recall list. Introduce an optional key that will allow to lift that limitation.

=== Side-specific results ===
Giving result=defeat or result=victory for specific sides. ([http://gna.org/bugs/index.php?4960 FR #4960]) -- [[User:dlr365|dlr365]] -- patch submitted [https://gna.org/bugs/index.php?4960]

=== Enabling checking of damage dealt in WML ===
A WML variable should be set when triggering some combat-related events, allowing WML to know the amount of damage being dealt. ([http://gna.org/bugs/index.php?7673 FR #7673])

=== Support for leaderless multiplayergames ===
Add support for the WML key victory_when_enemies_defeated= in the scenario tag during multiplayergames. ([https://gna.org/bugs/index.php?8106 FR #8106])

=== Allow a single [clear_variable] to clear multiple variables ===
Currently the name= key of [clear_variable] only takes a single variable name. However it'd be very handy to be able to clear multiple variables at the same time, so name= should also be made to also understand a comma-separated list:

[clear_variable]
name=var1,var2,var3
[/clear_variable]

Commas don't need to be valid characters in variable names, so the fact that it's ambiguous whether "name=var1,var2,var3" refers to three variables or just one variable named "var1,var2,var3" shouldn't cause any problems.

=== Other Ideas ===
See [[FutureWML]]; some ideas there are easier than others.

== Improvements to FormulaAI ==

Add new formula functions, or minor improvements to the formula language. Make it easier to debug the formula language.

== GUI related features ==
=== Change map paths from dots to dashes ===
Or even better allow dashes and allow choice between the two. As per FR #5522 [https://gna.org/bugs/?5522]

-------------------

Note at the moment Mordante is working on a new GUI system, these
changes will probably affect the way these items need to be implemented.
Contact Mordante on IRC before starting to work on these.

--[[User:SkeletonCrew|SkeletonCrew]] 14:04, 9 March 2008 (EDT)

=== Theme Changes ===

* show number of owned villages/total villages (FR: #3135) (--[[User:Alink|alink]] done but must update help, doc, tooltip...)
* allow custom themes to display values of WML variables ([http://gna.org/bugs/index.php?6209 FR #6209])
* hide the hourglass item from the statusbar when there is no timer

=== Widget Changes ===
* show side number, name and team association information in the status table
* make games sortable in the lobby (open slots, total number of players, era, XP modifier, gold per village, fog/shroud)
* input history (chat, commands, ..) - note: rujasu is working on this feature

== Miscellaneous ==

=== More powerful village naming ===
'''Adding mountain names and other features to village names, having a second random name in village names'''

Currently the village naming engine has a very good structure that could allow
more powerfull names to be generated.
Understanding how it works should be quite easy, and a few usefull improvements could be added.

* Currently villages can use lake names and river names, this should be extended to other features like bridges, swamps, mountains etc...
* It would be nice to have a separate list of "first sylabus" and "last sylabus" for naming. That's not really needed in english, but some translations could use it
* Again, it is common to have villages with more than one "random" word in them. having a $name2 variable would be nice

ACardboardRobot 2/2/07

=== Debug Mode ===
* New debug command functionality (setting additional status.variables, possibly terrain)

=== Add minimal regexp to friend list ===

Lots of people use multiple nicks, usually postfixed with a number... it would be nice to have minimal regexp support in friend list to easily get who's there...

== Bugs ==

== See Also ==

[[NotSoEasyCoding]]

[[Category:Development]]
[[Category:Future]]

EasyCoding

2008-05-13T02:45:33Z

Xonev: /* Make [removeitem] able to only remove a specific image */

== Foreword ==
This page is here to document easy to do coding tasks. It is not here to double the feature request database, and should only be filled by people that know the code well enough to judge the difficulty of a given task.

If you are such a person, you should feel free to edit this page.

If you're not, you should post a feature request and discuss your idea on the forum or IRC. A coder with better knowledge of the code might give you the green light to add your feature here.

Anybody should feel free to add "clues" to any tasks, that is entry points, traps to avoid, person to contact to discuss and so on.

If you plan to work on a feature, write your name at the bottom of the feature, with the date. Note that if you are too long at working on a feature I'll "free" it back (that is if you're not working on it. If you have problems implementing it, just tell us....)

--[[User:Boucman|Boucman]] 20:48, 3 October 2006 (CEST)

Since bugs are sometimes a good opportunity to get a first idea of the code, i will add some here that are easy to fix as soon as i stumble upon them (the one i had in mind is fixed already ;-).

--Yogi Bear, 28 February 2008

== MP related features ==

=== Add TTL to wesnothd bans ===
As per FR #3638 [https://gna.org/bugs/?3638]

''Working on it:'' Lao

=== Use different font for in-game chat ===
Since commas and dots are apparently hard to tell apart. As per FR #7470 [https://gna.org/bugs/?7470]

=== Allow lists for /ignore and similar ===
As per FR #7492 [https://gna.org/bugs/?7492]

== WML related features ==

=== Make [removeitem] able to only remove a specific image ===
Currently a [removeitem] always removes all images on the given hex. It should be made to support an image= key which, if given, would make it only remove that image. If not specified, then all images would be removed just like now.

--[[User:xonev|xonev]] 12 May 2008 - Almost have a patch ready

=== WML configurable village income / upkeep ===
Preferably as a [scenario], [side] or [campaign] keys. As per FR #6301 [https://gna.org/bugs/?6301]

=== Add support of [if] for [scenario] ===
As per FR #4539 [https://gna.org/bugs/?4539]

=== Make [have_unit] optionaly use full SUF ===
[have_unit] by default uses SUF but does not apply it to recall list. Introduce an optional key that will allow to lift that limitation.

=== Side-specific results ===
Giving result=defeat or result=victory for specific sides. ([http://gna.org/bugs/index.php?4960 FR #4960]) -- [[User:dlr365|dlr365]] -- patch submitted [https://gna.org/bugs/index.php?4960]

=== Enabling checking of damage dealt in WML ===
A WML variable should be set when triggering some combat-related events, allowing WML to know the amount of damage being dealt. ([http://gna.org/bugs/index.php?7673 FR #7673])

=== Support for leaderless multiplayergames ===
Add support for the WML key victory_when_enemies_defeated= in the scenario tag during multiplayergames. ([https://gna.org/bugs/index.php?8106 FR #8106])

=== Allow a single [clear_variable] to clear multiple variables ===
Currently the name= key of [clear_variable] only takes a single variable name. However it'd be very handy to be able to clear multiple variables at the same time, so name= should also be made to also understand a comma-separated list:

[clear_variable]
name=var1,var2,var3
[/clear_variable]

Commas don't need to be valid characters in variable names, so the fact that it's ambiguous whether "name=var1,var2,var3" refers to three variables or just one variable named "var1,var2,var3" shouldn't cause any problems.

=== Other Ideas ===
See [[FutureWML]]; some ideas there are easier than others.

== Improvements to FormulaAI ==

Add new formula functions, or minor improvements to the formula language. Make it easier to debug the formula language.

== GUI related features ==
=== Change map paths from dots to dashes ===
Or even better allow dashes and allow choice between the two. As per FR #5522 [https://gna.org/bugs/?5522]

-------------------

Note at the moment Mordante is working on a new GUI system, these
changes will probably affect the way these items need to be implemented.
Contact Mordante on IRC before starting to work on these.

--[[User:SkeletonCrew|SkeletonCrew]] 14:04, 9 March 2008 (EDT)

=== Theme Changes ===

* show number of owned villages/total villages (FR: #3135) (--[[User:Alink|alink]] done but must update help, doc, tooltip...)
* allow custom themes to display values of WML variables ([http://gna.org/bugs/index.php?6209 FR #6209])
* hide the hourglass item from the statusbar when there is no timer

=== Widget Changes ===
* show side number, name and team association information in the status table
* make games sortable in the lobby (open slots, total number of players, era, XP modifier, gold per village, fog/shroud)
* input history (chat, commands, ..) - note: rujasu is working on this feature

== Miscellaneous ==

=== More powerful village naming ===
'''Adding mountain names and other features to village names, having a second random name in village names'''

Currently the village naming engine has a very good structure that could allow
more powerfull names to be generated.
Understanding how it works should be quite easy, and a few usefull improvements could be added.

* Currently villages can use lake names and river names, this should be extended to other features like bridges, swamps, mountains etc...
* It would be nice to have a separate list of "first sylabus" and "last sylabus" for naming. That's not really needed in english, but some translations could use it
* Again, it is common to have villages with more than one "random" word in them. having a $name2 variable would be nice

ACardboardRobot 2/2/07

=== Debug Mode ===
* New debug command functionality (setting additional status.variables, possibly terrain)

=== Add minimal regexp to friend list ===

Lots of people use multiple nicks, usually postfixed with a number... it would be nice to have minimal regexp support in friend list to easily get who's there...

== Bugs ==

== See Also ==

[[NotSoEasyCoding]]

[[Category:Development]]
[[Category:Future]]

ConventionsWML

2008-03-25T17:48:15Z

Xonev: /* Naming files */

The purpose of this page is to list conventions of WML --
that is, things that make WML more readable and flexible.

== Use wmlscope, wmllint, and wmlindent ==

The WML [[Maintenance_tools|maintenance tools]] will help you ensure that your WML is clean, up-to-date, and correct. Use them early and often; they will save you a lot of trouble later by catching entire classes of WML bugs before a user can ever see them.

== Macros ==

Using macros is useful for decreasing the size of a file,
and for making it clear that you are doing the same thing several times.
It is economical to use '''[http://www.wesnoth.org/macro-reference.xhtml macros from the standard library]''' rather than writing your own whenever you can, but don't hesitate to write your own when the standard library does not do what you need.

A good rule for when to write a macro is to use them whenever information or code is being duplicated and all the duplications might have to be changed in the same way later. For information on how to create and use macros, see [[PreprocessorRef]].

Conventionally, your macro definitions should live in one or more files within a directory called utils under your main campaign directory. Be sure to
include that directory in your _main.cfg.

== Indentation ==

We used to have complicated recommendations for indentation. Now we have a WML indenting program and much simpler rules.

Be aware that no matter how you indent your WML, if it's accepted into mainline we are going to run <tt>wmlindent</tt> on it and smash it into the house style. We do this so our WML maintainers won't have to cope with lots of idiosyncratic indentation variants. You can make your WML more readable by writing in the house style to begin with.

# Indent each level with '''4 spaces'''.
# Indent attributes a level deeper than their parent tag.
# Indent macros as though the <tt>#define/#enddef</tt> are an outermost level; that is, the macro body starts with one level of indenting.
# Don't indent <tt>#ifdef</tt>/<tt>#else</tt>/<tt>#endif</tt> at all
# Indent comments at the same level as the text they go with.

When in doubt, run <tt>wmlindent</tt> on your code. See [[Maintenance tools]] for more description of this program.

Note: Please do '''not''' insert tabs in WML code! Editor and viewer programs do not handle tabs in a uniform way; it has been found by experience, especially in the land of Python, that this leads to all manner of annoyances for maintainers further down the road.

== Naming files ==

First of all, don't put spaces in filenames;
this causes errors on some systems.
Use underscores('''_''') instead.

If the IDs of your scenarios are different from their names,
name the files after the IDs, not the names.
That way it is easier to tell which scenario is next.

Use the scenario number and an underscore as a name prefix of your scenario files, and if you have more than 9 of these put 0 at the beginning of single-digit numbers. This will make them list in order, which is convenient for people trying to read your campaign.

While many campaigns use the same sort of number prefixing for their map files, it's better not to if (as sometimes happens) your campaign needs to use the same map twice.

== WML variables ==

(For information about what WML variables are, see [[VariablesWML]].)
These shouldn't be used except when necessary.
[have_unit] tags can often be used instead.
Also, make sure that your scenarios
clear meaningless variables using [clear_variable].

For variable values, use 'yes' and 'no' for boolean values
rather than 1 and 0.
It's clearer to people who don't know programming.

== See Also ==
* [[ReferenceWML]]

[[Category:WML Reference]]

ConventionsWML

2008-03-25T17:00:23Z

Xonev: /* Use wmlscope, wmllint, and wmlindent */

The purpose of this page is to list conventions of WML --
that is, things that make WML more readable and flexible.

== Use wmlscope, wmllint, and wmlindent ==

The WML [[Maintenance_tools|maintenance tools]] will help you ensure that your WML is clean, up-to-date, and correct. Use them early and often; they will save you a lot of trouble later by catching entire classes of WML bugs before a user can ever see them.

== Macros ==

Using macros is useful for decreasing the size of a file,
and for making it clear that you are doing the same thing several times.
It is economical to use '''[http://www.wesnoth.org/macro-reference.xhtml macros from the standard library]''' rather than writing your own whenever you can, but don't hesitate to write your own when the standard library does not do what you need.

A good rule for when to write a macro is to use them whenever information or code is being duplicated and all the duplications might have to be changed in the same way later. For information on how to create and use macros, see [[PreprocessorRef]].

Conventionally, your macro definitions should live in one or more files within a directory called utils under your main campaign directory. Be sure to
include that directory in your _main.cfg.

== Indentation ==

We used to have complicated recommendations for indentation. Now we have a WML indenting program and much simpler rules.

Be aware that no matter how you indent your WML, if it's accepted into mainline we are going to run <tt>wmlindent</tt> on it and smash it into the house style. We do this so our WML maintainers won't have to cope with lots of idiosyncratic indentation variants. You can make your WML more readable by writing in the house style to begin with.

# Indent each level with '''4 spaces'''.
# Indent attributes a level deeper than their parent tag.
# Indent macros as though the <tt>#define/#enddef</tt> are an outermost level; that is, the macro body starts with one level of indenting.
# Don't indent <tt>#ifdef</tt>/<tt>#else</tt>/<tt>#endif</tt> at all
# Indent comments at the same level as the text they go with.

When in doubt, run <tt>wmlindent</tt> on your code. See [[Maintenance tools]] for more description of this program.

Note: Please do '''not''' insert tabs in WML code! Editor and viewer programs do not handle tabs in a uniform way; it has been found by experience, especially in the land of Python, that this leads to all manner of annoyances for maintainers further down the road.

== Naming files ==

First of all, don't put spaces in filenames;
this causes errors on some systems.
Use underscores('''_''') instead.

If the IDs of your scenarios are different from their names,
name the files after the IDs, not the names.
That way it is easier to tell which scenario is next.

Use the scenario number and an underscore as a name prefix of your scenario files, and if you have more than 9 of these put 0 at the beginning of single-digit numbers. This will make them list in order, which is convenient for people trying to read your campaign.

While many campaigns use the same sort of number prefixing for their map files, it's better not to if (as somethimes happens) your campaign needs to use the same map twice.

== WML variables ==

(For information about what WML variables are, see [[VariablesWML]].)
These shouldn't be used except when necessary.
[have_unit] tags can often be used instead.
Also, make sure that your scenarios
clear meaningless variables using [clear_variable].

For variable values, use 'yes' and 'no' for boolean values
rather than 1 and 0.
It's clearer to people who don't know programming.

== See Also ==
* [[ReferenceWML]]

[[Category:WML Reference]]

SummerOfCodeIdeas

2008-03-25T02:55:16Z

Xonev: /* EvolutionaryMapEditor (xonev) */

This is a compilation of ideas from ML. Needs to be refined (more detailed description, deliverables, workload estimation?):

== 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
* Create an account on gna.org
* Create an account on the wesnoth forum
* 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 learnt to know during the selection process
* Contact one of our SummerOfCode people (Ivanovic, Sirp, Boucman, Mordante) to have your forum nick marked as a Summer of code student

* Start a wiki page about your idea, add a link on the bottom of this page and add this information on it:
** List your account names (gna, forum, irc nick) so that we can recognize you
** Fill the questionnaire on this page: [[SoC_Information_for_Google#Does_your_organization_have_an_application_template_you_would_like_to_see_students_use.3F_If_so.2C_please_provide_it_now.| List of questions to answer]]
** Detail your idea as much as possible, look at other students pages, and please give milestones and studies you've done

* 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.

* Once you have everything done here and think your idea is okay, go to [http://groups.google.com/group/google-summer-of-code-announce/web/guide-to-the-gsoc-web-app-for-student-applicants to page at google] to submit your application. You have to submit it before '''Monday, March 31, 2008''' or you have no chance to get in!

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

Here is only a short description of possible Ideas we have, each has a page of its own with a more detailed version on it.

=== Writing an AI based on the formula AI ===

Wesnoth has always had a simple C++ based AI. David (our lead developer) has been working on a simple language to write AI in Wesnoth: [[FormulaAI]]

The Wesnoth AI is used as an opponent in most campaigns, and as such is an important piece of code for the Wesnoth project. Unfortunately, because the skills required to understand and modify it are rather arcane, it is also one of the most neglected parts of the Wesnoth code. This is a place where a lot of research and useful work could be done. But keep in mind that [[WhyWritingAWesnothAIIsHard|writing an AI for Wesnoth is difficult]].

[[SoC Ideas FormulaAI]] - Full version of the idea, with detailed information

=== Extending the Multiplayer server ===

Our multiplayer community is generally strong and healthy, but we believe its growth is limited by some problems in the interface of the multiplayer lobby.

[[SoC Ideas Multiplayer server]] - Full version of the idea, with detailed information

=== Scenario/Campaign editor ===

Currently, in order to create campaign or multiplayer scenarios, it is necessary to manually edit WML files - XML-like configuration files. The goal of this project would be to create a graphical editor to make the creative process easier.

[[SoC Ideas Scenario and Campaign Editor]] - Full version of the idea, with detailed information

=== Addon server ===
Wesnoth has an addon server which offers users to upload user
made content (UMC). This allows all other users of Wesnoth
to easily download and install this content. The server was
originally written for user-made campaigns but contains a lot
more types of addons nowadays. Both the server side and the
client side need to be improved.

[[SoC Ideas Addon Server]] - Full version of the idea, with detailed information

=== Map editor ===
The map editor in Wesnoth serves two goals, making it easy to create
a new map and helping the terrain artists to test their new terrains.

[[SoC_Ideas_Map_Editor]] - Full version of the idea, with detailed information

=== Other possible ideas to be fleshed out ===
A MapGenerator rewrite - better scalable for outdoor maps, plus the possibility to define areas (similar to the caverns in the cave generator) etc.

=== Make 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.

== 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]]

== GSoC Student Applicant Ideas ==

Every student interested to work on Wesnoth as part of Summer of Code should create a page of his own where several things should be listed. Here is a short list of what should be mentioned on the list (the more info for us, the better...):

* Who are you? Please list your IRC and forum nickname in here and describe yourself so that we get you to know.
* What do you want to work on? Please flesh out your personal ideas, so that we get to know what you plan to work on.
* If you already submitted patches, please list those so that we have a reference.

===[[SoC Ideas FormulaAI|Formula AI]]===
====[[FormulaAIandAdaptation]] (Alesis-Novik) ====
The new idea and aproach using strategic and inside game knowledge

==== [[FormulaAIandDynamicScripting]] (barbarianhero) ====
This project idea uses Formula AI and Dynamic Scripting to create a tunable and adaptive AI.

====[[FormulaAIBaseAI]] (Dragonking) ====
Developing smart and pluggable AI, which would be really easy tweakable by Scenario and Campaign Developers

===[[SoC Ideas Multiplayer server|Multiplayer Server]]===
====[[ExtendingMultiplayerServer]] (dudegaurav) ====
Under Construction ...

===[[SoC Ideas Scenario and Campaign Editor|Scenario/Campaign Editor]]===
====[[ExtensibleScenarioEditor]] (david.hilton) ====
On a conceptual level, this idea combines a finite state machine editor with a code generator to create scenarios.

====[[pyQTScenarioEditor]] (Malle) ====
That's me!

====[[RujasuScenarioEditor]] (rujasu) ====
Scenario editor that will coordinate with the look and feel of the Wesnoth game.

===[[SoC Ideas Addon Server|Addon Server]]===
====[[AddonServerSocial]] (lao) ====
Improving addon Server/Client by adding some social content.

====[[AddonServer]] (giebfried) ====
This project is to improve the server and client sides of the addon server, as suggested above.

===[[SoC Ideas Map Editor|Map Editor]]===
====[[EvolutionaryMapEditor]] (xonev) ====
An evolutionary approach to improving the map editor.

====[[VimzardMapEditor]] (vimzard) ====
A better random map generator, some essential features and a tie-in with the Scenario Editor.

====[[NewMapEditor]] (Cecen) ====
This is basically a rewrite of the current map editor with various added features and tweaks to both increase the versatility of the editor and make it easier for the user to create maps with.

===Map Generator===
====[[RandomCampaignGenerator]] (kartik thakore, refining idea) ====
Procedural map generation that will hope to give writers better control over the random map generator using an interface.

===Other===
====[[WesnothStatistics]] (radx) ====
Project related to Wesnoth statistics (campaign) submission, gathering and presentation.

[[Category:Summer of Code|*]]

EvolutionaryMapEditor

2008-03-25T02:52:54Z

Xonev:

==General Info==
My name is Steven Oxley. My preferred e-mail address is sajo at andrews dot edu, my nick on the forums and in irc is xonev.

I am a Junior computer science major at Andrews University. My main reason for becoming interested in Google Summer of Code is that I would really like some experience doing some actual coding outside of my classes or the odd project I do from time to time and I am eager to supplement all of the learning I have already gained from my classes.

I am a gamer. I play all kinds of games - I especially enjoy first person shooters, but rpgs and strategy games are also up there on the list. I am not a big fan of real-time strategy games as I find that I have trouble keeping a good balance between offense and development. I like a good balance between story and gameplay in my games, but my focus tends to tip towards gameplay. For instance, a game could have a horrible story and great gameplay and I would play it, but a game with a great story and horrible gameplay I would not play. I had not played Wesnoth before I looked it up in the GSoC listing, but I have now and I enjoy it a great deal. It's just the type of strategy game I like. I have not played the multiplayer yet, but I plan on it in the future.

==Experience==
Most of my experience with writing software has come in the academic environment. I have done some other web-programming work as a side project at my job (computer technician at Andrews), but nothing major professionally. I have never really contributed to an open source project before either although I have been looking for one to get involved with over the past month or so.

I have developed software in a team environment in my Software Engineering group project class. We created a database application to keep track of inventory. I turned out to be one of the key members of the group as I often had to keep the group focused and ended up doing a large amount of the programming. I also worked on an Android project with some of my friends - unfortunately, it pretty much died in the concept phase.

I have never participated in GSoC before, but am hoping to this year ;P

I am a firm believer in the evolutionary model of software development. I am also an advocate of not reinventing what is already available. This, I believe, will greatly influence my proposal as I will attempt not to rewrite the map editor from scratch, but instead work with what is already there and evolve it into something better.

==Communication Skills==
I am fluent in English - it is my mother tongue. I find that I get along well with everyone I interact with - even if they are not so friendly to begin with. I am usually able to see other people's side of things which greatly helps in communicating with them. I take advice and criticism seriously and usually manage not to get defensive. I think critically about all advice I am given.

==Project==
The basic overview for my plans at revamping the map editor is this: I want to take what is already there (because it is by no means useless) and improve it one bit at a time in an evolutionary manner. At every point, I want to have a working piece of software.

Some of the changes that I would like to make to the editor are as follows:
*Modularize everything (within reason).
**Many of the options in the editor that could be modularized are currently hardcoded - I want to change that. For example:
***Brush selection and terrain palette coordinates are hardcoded - these can be made theme-able.
***The tool-tips are all hardcoded in - these could be modularized as well.
***The random map generator currently only supports running one map generator, hard coded - I would look at adding functionality to run any generator config that the user would want to use.
*Generally improve/refactor existing code in the map editor.
**Obviously, this would involve becoming familiar with Wesnoth coding standards and the Wesnoth code itself (which I have already begun working on).
**There have been complaints about the copy function not working as expected sometimes.
**Make sure that everything is rendered exactly the same way as it is in an actual Wesnoth game.
*Add new features. For more information on this see http://www.wesnoth.org/forum/viewtopic.php?f=15&t=20506.
**Add handling of custom terrain - add functionality to use terrain other than what is loaded in the editor by default.
**Add ability to reload config files without reloading the editor so that users can edit the config files and be able to see the results without completely restarting the editor.
**If time for this summer allows (or after the summer if it does not) I would like to add the ability for the user to have more direct control over the aesthetics of the map from the map editor. From what I understand, this would require making some changes to the terrain generator engine.

To summarize, I would start with improving what is already there for two reasons - to bring the existing code up to par with the rest of the project and to become more familiar with what is already there. As the summer progressed, I would discuss new features that could be added with my mentor and the community and work towards implementing them. Two of the features which I could almost certainly complete this summer would be adding the ability to handle custom terrain and adding the ability to reload config files without restarting the editor.

Tentative Summer Time-line:
*Improve/refactor Existing Code (April 14 - July 7)
**Debug copy functionality.
*Add interfaces for additional random map generator config files (May 26 - June 17)
*Make brush-selection and terrain-palette coordinates theme-able (June 17 - June 27)
*Make tool-tips theme-able (June 27 - July 7)
*Add ability to use "custom terrain" (July 7 - July 24)
*Add ability to reload config files without reloading editor ( July 24 - August 11)

==Practical Considerations==
===Tools===
I am familiar with subversion and C++ - I have messed around with Python a very small amount a year ago or so.
The development tools I usually use are
*Visual C++ Express Edition for C++ - I use this because it's free and I usually develop in Windows.
*Notepad++ - I use this for any web-based projects I might be working on.
*phpMyAdmin - Again, I use this for web-based database stuff because it recognizes language syntax for all the languages I might need for web-based apps.
*ShaderDesigner - I use this one for writing OpenGL vertex and fragment shaders.
*RenderMonkey - I use this for writing shaders if I don't think I will have to mess around with any application code.
*Eclipse - I have used this for doing some Java stuff.
===Languages===
The Languages I'm fluent in:
====Programming Languages====
*C++ - I've used c/c++ a lot in several of my classes.
*PHP - I've probably used this the most.
*GLSL - For those who don't know, it's a gpu shader language.
*Several others I've done some basic stuff with - Java, Javascript, PERL, Python.

==== Spoken Languages====
*English - I think my English teacher used to nag me about having outline headings with only one point *shrug*

===Me (and why I would be a good choice)===
I am usually awake from 11 utc to 3 utc. I could probably adjust this just about however I wanted if I were to get the GSoC position. I would be perfectly comfortable talking to my mentor via voip, telephone, or whatever.

I would be a good choice for your project not because I am an expert at any one area. I do not claim to be a C++ master or anything of the sort. The reason I would be a good, no, great choice for your project is that I am a very highly motivated individual - I work very hard even when completely unsupervised and I have a superbly developed sense of responsibility for everything that I am expected to complete. I am also a quick learner, but when I have trouble with something I will stick with it until I get it (or find a better way to do it).

==Essay==
Why do I want to participate in Battle for Wesnoth for Google Summer of Code? My first reaction to this question would be a simple one: I want to get paid to work on a game that I have fun playing. This answer may appear rather shallow at first (and it really is), but my reason for wanting to work on this open source project runs much deeper than it being a fun-to-play game. In fact, when analyzed, it is clear that this question is two-fold. Why do I want to participate in Google Summer of Code? And furthermore, why did I choose Battle for Wesnoth?

There are a few reasons that I want to participate in Google Summer of Code. If I get the privilege of participating in Google Summer of Code I will get paid for doing something I love - programming. There are several aspects to my love of programming. The first aspect is my love of learning. I love finding out new things, discussing new concepts, and discovering better ways to do things - these are all inherent attributes of programming. The second aspect to my love of programming is my love of figuring stuff out. I enjoy employing my mind and skills in solving a tough problem. The third and probably most influential aspect of my love of programming is my desire to create things. Even if it is just something simple such as writing a new method, there is something intoxicating about creating new content that works. This love of creating things is what got me interested in programming in the first place and why I will continue programming throughout my career.

Another reason I desire to participate in Google Summer of Code is my belief in open source. I think that open source is a very important part of software development. I am not sure how I feel about the idea of open source being the best method of software development, but it is definitely a proven method. Much of the software I use is open source and I have been pleased with all that I have used so far. I think that open source leads to better maintained software since the people who write it are generally the people who use it, and anyone who uses it can contribute to it to make it better. This also leads to open source software being tailor made for the community that uses it. I believe that open source will become more and more popular as it becomes more well known and it is certainly something that I will be proud to be involved in.

The other reason that I wish to be a part of Google Summer of Code is my desire to put my knowledge to use. I have spent a lot of time looking through different projects on the sourceforge website for particularly this reason. I feel like I have learned a lot in my classes, but I do not think that I will really have what I need to survive in the software development industry without keeping my skills sharp by using them on real projects. This is probably my main reason for being interested in Google Summer of Code. I want to learn as much as I can while working on a worthwhile project (preferably while getting paid).

The other question that needs to be answered is why am I interested in Battle for Wesnoth? The answer to this question is actually quite simple. I was looking for a project that could use my skills and that was managed well. The first thing I was especially impressed with about Battle for Wesnoth was how much effort has been made to get Google Summer of Code potentials up to speed. It was not difficult at all for me to find exactly what would be expected from me and exactly what I would need to look at and learn about to submit a competent proposal and to get involved with the project in general. Not only that, but the documentation that I have read over so far has been well written and rather easily understandable. Also, the developers on IRC have been more than helpful whenever I have had a question to ask. I believe that all of these things point to the fact that Battle for Wesnoth is a well-developed, well-structured, well-managed, and well-maintained project. More evidence to the fact that Battle for Wesnoth is a well-done project is the quality of the game itself. It may not be the most complicated game, but it is very polished and well-presented. Battle for Wesnoth also seemed like a good fit for me because it is written mostly in C++ which is the programming language I am most interested in. Also, Battle for Wesnoth is a game, which is something I am quite familiar with, being a regular gamer.

In conclusion, my reasons for wanting to become involved with Battle for Wesnoth for Google Summer of Code are two-fold. First, I want to become involved with Google Summer of Code in general because I want to be able to spend the majority of my summer doing what I love - programming. Second, I want to get involved with Battle for Wesnoth because I feel that it is a well-done project and it is in a category of software that I have personally been a involved with for quite some time.

[[Category:Summer of Code]]

EvolutionaryMapEditor

2008-03-25T01:19:56Z

Xonev: /* Project */

EvolutionaryMapEditor

2008-03-24T17:53:08Z

Xonev: /* Project */

EvolutionaryMapEditor

2008-03-21T22:07:42Z

Xonev: /* Project */

EvolutionaryMapEditor

2008-03-21T07:21:57Z

Xonev: /* Project */

EvolutionaryMapEditor

2008-03-20T19:04:45Z

Xonev: /* Programming Languages */

SummerOfCodeIdeas

2008-03-20T16:40:01Z

Xonev:

This is a compilation of ideas from ML. Needs to be refined (more detailed description, deliverables, workload estimation?):

== 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
* Create an account on gna.org
* Create an account on the wesnoth forum
* 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 learnt to know during the selection process
* Contact one of our SummerOfCode people (Ivanovic, Sirp, Boucman, Mordante) to have your forum nick marked as a Summer of code student

* Start a wiki page about your idea, add a link on the bottom of this page and add this information on it:
** List your account names (gna, forum, irc nick) so that we can recognize you
** Fill the questionnaire on this page: [[SoC_Information_for_Google#Does_your_organization_have_an_application_template_you_would_like_to_see_students_use.3F_If_so.2C_please_provide_it_now.| List of questions to answer]]
** Detail your idea as much as possible, look at other students pages, and please give milestones and studies you've done

* 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.

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

Here is only a short description of possible Ideas we have, each has a page of its own with a more detailed version on it.

=== Writing an AI based on the formula AI ===

Wesnoth has always had a simple C++ based AI. David (our lead developer) has been working on a simple language to write AI in Wesnoth: [[FormulaAI]]

The Wesnoth AI is used as an opponent in most campaigns, and as such is an important piece of code for the Wesnoth project. Unfortunately, because the skills required to understand and modify it are rather arcane, it is also one of the most neglected parts of the Wesnoth code. This is a place where a lot of research and useful work could be done. But keep in mind that [[WhyWritingAWesnothAIIsHard|writing an AI for Wesnoth is difficult]].

[[SoC Ideas FormulaAI]] - Full version of the idea, with detailed information

=== Extending the Multiplayer server ===

Our multiplayer community is generally strong and healthy, but we believe its growth is limited by some problems in the interface of the multiplayer lobby.

[[SoC Ideas Multiplayer server]] - Full version of the idea, with detailed information

=== Scenario/Campaign editor ===

Currently, in order to create campaign or multiplayer scenarios, it is necessary to manually edit WML files - XML-like configuration files. The goal of this project would be to create a graphical editor to make the creative process easier.

[[SoC Ideas Scenario and Campaign Editor]] - Full version of the idea, with detailed information

=== Addon server ===
Wesnoth has an addon server which offers users to upload user
made content (UMC). This allows all other users of Wesnoth
to easily download and install this content. The server was
originally written for user-made campaigns but contains a lot
more types of addons nowadays. Both the server side and the
client side need to be improved.

[[SoC Ideas Addon Server]] - Full version of the idea, with detailed information

=== Map editor ===
The map editor in Wesnoth serves two goals, making it easy to create
a new map and helping the terrain artists to test their new terrains.

[[SoC_Ideas_Map_Editor]] - Full version of the idea, with detailed information

=== Other possible ideas to be fleshed out ===
A MapGenerator rewrite - better scalable for outdoor maps, plus the possibility to define areas (similar to the caverns in the cave generator) etc.

=== Make 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.

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

== 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]]

== GSoC Student Applicant Ideas ==

Every student interested to work on Wesnoth as part of Summer of Code should create a page of his own where several things should be listed. Here is a short list of what should be mentioned on the list (the more info for us, the better...):

* Who are you? Please list your IRC and forum nickname in here and describe yourself so that we get you to know.
* What do you want to work on? Please flesh out your personal ideas, so that we get to know what you plan to work on.
* If you already submitted patches, please list those so that we have a reference.

=== [[FormulaAIandDynamicScripting]] (barbarianhero) ===
This project idea uses Formula AI and Dynamic Scripting to create a tunable and adaptive AI.

===[[FormulaAIandThinkingAhead]] (Alesis-Novik) ===
This project idea uses methods to make the AI *think* ahead.

===[[ExtensibleScenarioEditor]] (david.hilton) ===
On a conceptual level, this idea combines a finite state machine editor with a code generator to create scenarios.

===[[RandomCampaignGenerator]] (kartik thakore) ===
Procedural Campaign generation that combines random map generation, story generation, and strategy generation.

===[[LaoSoCIdeas]] by lao ===
Under Construction...

===[[AddonServer]] (giebfried) ===
This project is to improve the server and client sides of the addon server, as suggested above.

===[[EvolutionaryMapEditor]] (xonev) ===
Under Construction
[[Category:Summer of Code|*]]

EvolutionaryMapEditor

2008-03-20T16:37:39Z

Xonev: /* Me */

EvolutionaryMapEditor

2008-03-20T15:58:37Z

Xonev: New page: =Me= My name is Steven Oxley. My preferred e-mail address is sajo at andrews dot edu, my nick on the forums and in irc is xonev. I am a Junior computer science major at Andrews Universit...

=Me=
My name is Steven Oxley. My preferred e-mail address is sajo at andrews dot edu, my nick on the forums and in irc is xonev.

I am a Junior computer science major at Andrews University. My main reason for becoming interested in Google Summer of Code is that I would really like some experience doing some actual coding outside of my classes or the odd project I do from time to time and I am eager to supplement all of the learning I have already gained from my classes.