SoC2011 Student Page Aethaeryn - Revision history

Egallager: link cleanup

2023-04-24T02:38:53Z

link cleanup

Esr: Hide historical references to Subversion from the wiki search function

2013-03-21T02:59:14Z

Hide historical references to Subversion from the wiki search function

Esr: Hide historical references to Subversion from the wiki search function

2013-03-21T01:46:42Z

Hide historical references to Subversion from the wiki search function

Aethaeryn: /* The Implementation: Timeline */ slight revision, more to come

2011-04-17T16:40:16Z

‎The Implementation: Timeline: slight revision, more to come

Aethaeryn: /* IRC */ adding one of my alternate nicks now that it's running on a remote server irssi

2011-04-17T05:32:48Z

‎IRC: adding one of my alternate nicks now that it's running on a remote server irssi

Aethaeryn: /* gui_message{} */ removing comment on a Lua code line

2011-04-16T23:25:57Z

‎gui_message{}: removing comment on a Lua code line

Aethaeryn: /* gui_message{} */ the function will now directly show since it takes a table as its sole input

2011-04-16T21:04:44Z

‎gui_message{}: the function will now directly show since it takes a table as its sole input

Aethaeryn: /* Sample Syntax */ slight change in syntax

2011-04-16T21:04:08Z

‎Sample Syntax: slight change in syntax

Aethaeryn: /* The Implementation: Timeline */ note

2011-04-16T18:31:22Z

‎The Implementation: Timeline: note

Aethaeryn: /* Phase 1: Complex Interface Changes */ note

2011-04-16T18:30:28Z

‎Phase 1: Complex Interface Changes: note

@@ Line 41: / Line 41: @@
 * Implement improved Lua access to the in-scenario GUI stuff, again without WML table hacks.
-** This includes improving the syntax and implementation of the [http://wiki.wesnoth.org/LuaWML:Display#wesnoth.show_dialog dialog Lua].
+** This includes improving the syntax and implementation of the [[LuaWML:Display#wesnoth.show_dialog|dialog Lua]].
 * A way to take in text commands in a way similar to debug mode's :lua, but only using specific commands to do specific actions as defined by Lua code in the add-on.
@@ Line 318: / Line 318: @@
 '''2.6) If you have contributed any patches to Wesnoth, please list them below. You can also list patches that have been submitted but not committed yet and patches that have not been specifically written for GSoC. If you have gained commit access to our S&shy;&shy;V&shy;&shy;N (during the evaluation period or earlier) please state so.'''
-I will not be able to submit a patch by the application deadline, but they will be [http://wiki.wesnoth.org/SoC2011_Student_Page_Aethaeryn#Patches here] when I have the time.
+I will not be able to submit a patch by the application deadline, but they will be [[SoC2011_Student_Page_Aethaeryn#Patches|here]] when I have the time.
 |-
@@ Line 372: / Line 372: @@
 '''4.4) Include an estimated timeline for your work on the project. Don't forget to mention special things like "I booked holidays between A and B" and "I got an exam at ABC and won't be doing much then".'''
-[http://wiki.wesnoth.org/SoC2011_Student_Page_Aethaeryn#The_Implementation:_Timeline See here for the timeline.]
+[[SoC2011_Student_Page_Aethaeryn#The_Implementation:_Timeline|See here for the timeline.]]
 '''4.5) Include as much technical detail about your implementation as you can'''

@@ Line 397: / Line 397: @@
 '''5.1) Are you familiar with any of the following tools or languages?'''
-* Subversion (used for all commits)
+* Sub&shy;&shy;version (used for all commits)
 ** Yes, I've used it for both wesnoth (updates only) and wesnoth-umc-dev (updates and commits) for several years.
 * C++ (language used for all the normal source code)

@@ Line 256: / Line 256: @@
 ===Experience===
-My primary strength in terms of experience is that I've been with the Wesnoth project, doing almost everything possible except developing for the game engine itself over the course of almost four years. I know the Lua because I've made add-ons in Lua and will continue to port my active add-ons to Lua as time goes on. I know the community because I am part of it. I know the IRC channels because I've regularly been in many of the channels for years. I've even been using SVN as my means of downloading/updating/playing Wesnoth for at least two years now (for stable, development, and trunk).
+My primary strength in terms of experience is that I've been with the Wesnoth project, doing almost everything possible except developing for the game engine itself over the course of almost four years. I know the Lua because I've made add-ons in Lua and will continue to port my active add-ons to Lua as time goes on. I know the community because I am part of it. I know the IRC channels because I've regularly been in many of the channels for years. I've even been using S&shy;&shy;V&shy;&shy;N as my means of downloading/updating/playing Wesnoth for at least two years now (for stable, development, and trunk).
 '''2.1) What programs/software have you worked on before?'''
@@ Line 287: / Line 287: @@
 * add-ons (since 2007; published since 1.3.x)
 * unofficial Wesnoth-style sprite art (since 2008)
-* wesnoth-umc-dev SVN repository (since 2009)
+* wesnoth-umc-dev S&shy;&shy;V&shy;&shy;N repository (since 2009)
 * wiki moderator (since 2009)
 * Latin translator (since 2009)
@@ Line 316: / Line 316: @@
 Almost four years experience, mostly MP but also a significant amount of SP, especially when I first started playing Wesnoth. I've been playing since the 1.2/1.3 versions.
-'''2.6) If you have contributed any patches to Wesnoth, please list them below. You can also list patches that have been submitted but not committed yet and patches that have not been specifically written for GSoC. If you have gained commit access to our SVN (during the evaluation period or earlier) please state so.'''
+'''2.6) If you have contributed any patches to Wesnoth, please list them below. You can also list patches that have been submitted but not committed yet and patches that have not been specifically written for GSoC. If you have gained commit access to our S&shy;&shy;V&shy;&shy;N (during the evaluation period or earlier) please state so.'''
 I will not be able to submit a patch by the application deadline, but they will be [http://wiki.wesnoth.org/SoC2011_Student_Page_Aethaeryn#Patches here] when I have the time.

@@ Line 173: / Line 173: @@
 {| border="1"
 | now || April&nbsp;08&nbsp;-&nbsp;April&nbsp;22&nbsp;&nbsp; || <h4>Pre-Summer I</h4>
-Discuss details of the implementation with various developers in order to finalize most of the project's design.
+Finalize design.
-Work on basic patches, especially in the early areas of Phase 0, so that commit access can be granted before the designated GSOC period.
+Get most of Phase 0 working.
 |-
 | || April 23 - May 08 ||
-Continue to familiarize myself with the project and its code by doing more of Phase 0.
+Finish Phase 0.
 |-
 | || May 09 - May 18 || '''Spring semester ends.''' Availability may be limited during this period.
 |-
 | || May 19 - May 30 || <h4>Summer I</h4>
-'''Phase 0 ends; Phase 1 beings.''' My schedule is be ''entirely'' free in this time span.
+'''Phase 1 beings.''' (My schedule is be ''entirely'' free in this time span.)
 |-
 | || May 31 - June 30 || <h4>Summer II</h4>
-The entire month of June will be spent on Phase 1. I will balance my time with a summer semester, but should have Fridays through Sundays entirely free.
+My summer semester starts. I should still have Fridays through Sundays entirely free.
 |-
 | || July 4 - July 8 || Expected busy week as my one summer course wraps up.

@@ Line 8: / Line 8: @@
 ==IRC==
-Aethaeryn
+Aethaeryn, Aeth
 ==Introduction==

@@ Line 85: / Line 85: @@
   gui_message {
      message     = string,
-     speaker     = string, -- "narrator", "unit" or "second_unit"
+     speaker     = string,
      side_for    = integer, -- or a table with a set of integers
      image       = string,

← Older revision		Revision as of 21:04, 16 April 2011
Line 97:		Line 97:

	The best part about this is that the core function (excluding the options and text_input tables) can be easily converted into a form recognizable by WML and handled using the same function that handles the existing [message] code. Complexity and a difference from the WML definition only really enter when implementing [option] and [text_input].		The best part about this is that the core function (excluding the options and text_input tables) can be easily converted into a form recognizable by WML and handled using the same function that handles the existing [message] code. Complexity and a difference from the WML definition only really enter when implementing [option] and [text_input].
−
−	Calling the function does not actually display the message. Instead, one does "variable = gui_message{ ... }" and then variable.show <!-- or is it variable.show()? --> when one wants the message to trigger.

	The alternative form of gui_message{} is gui_message(table) where table is a table with keys that match the definition of gui_message{}.		The alternative form of gui_message{} is gui_message(table) where table is a table with keys that match the definition of gui_message{}.

@@ Line 56: / Line 56: @@
 ====Sample Syntax====
-  local msg = gui_message{
+  -- The function can be triggered directly by defining the table in the function call to gui_message{}.
      message  = "Hello world!",
      speaker = "narrator",
@@ Line 66: / Line 67: @@
+  }
-  local msg2 = gui_message{
+  -- The function can be used indirectly by setting it to a table first, and then using the table's
      message = "What's your name?",
-     -- no "settings =" makes it set reasonable defaults
+     -- if the tag is not there, reasonable defaults are set
      -- text_input takes either a table containing the information, or a table of tables that are all valid text_input
      text_input = {variable = "foo", label = "Name: ", max_length = 42}
+  }
   function foobar()
-     msg2.show
+     gui_message(msg)
 ====gui_message{}====

@@ Line 38: / Line 38: @@
 ===Phase 1: Complex Interface Changes===
 <!-- fixme: rewrite in the style of the two phases and expand -->
 * Implement improved Lua access to the in-scenario GUI stuff, again without WML table hacks.