SummerOfCodeProposal Kahowell

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 student page

Description

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

IRC

kahowell

Questionnaire

1) Basics 1.1) Write a small introduction to yourself. My name is Kevin Howell. I'm a computer science student (third year) at a liberal arts university in the United States. I'm interested in game programming as a hobby. 1.2) State your preferred email address. kevin.adam.howell (at) gmail (dot) com 1.3) If you have chosen a nick for IRC and Wesnoth forums, what is it? kahowell 1.4) Why do you want to participate in summer of code? I'm looking for a way to start participating in FOSS. 1.5) What are you studying, subject, level and school? I am an undergraduate student at the College of William & Mary in the city of Williamsburg, VA. I'm a 3rd year computer science major. I have taken many classes including (but not limited to) Computer Graphics Data Structures Web Programming Programming Languages Systems Programming Algorithms Theory of Computation Software Development 1.6) What country are you from, at what time are you most likely to be able to join IRC? I am from the United States. I would most likely be able to join IRC at around 4PM EDT (-5 GMT) until 11PM EDT. 1.7) Do you have other commitments for the summer period ? Do you plan to take any vacations ? If yes, when. I do not currently have any commitments for the summer. 2) Experience 2.1) What programs/software have you worked on before? I do not have any experience in working with production software, though my school projects have included a raytracer in C++ from scratch. 2.2) Have you developed software in a team environment before? (As opposed to hacking on something on your own) In college, I have done some pair programming. 2.3) Have you participated to the Google Summer of Code before? As a mentor or a student? In what project? Were you successful? If not, why? I have not participated. 2.4) Are you already involved with any open source development projects? If yes, please describe the project and the scope of your involvement. I am not yet involved with any. 2.5) Gaming experience - Are you a gamer? Yes, I play computer and video games. 2.5.1) What type of gamer are you? I play games for leisure. 2.5.2) What type of games? I tend to enjoy Japanese-style strategy/tactical RPGs (ex. Disgaea, Final Fantasy Tactics). 2.5.3) What type of opponents do you prefer? I prefer to play against friends. 2.5.4) Are you more interested in story or gameplay? I am generally more interested in story, though I would say that there needs to be a balance. 2.5.5) Have you played Wesnoth? If so, tell us roughly for how long and whether you lean towards single player or multiplayer.We do not plan to favor Wesnoth players as such, but some particular projects require a good feeling for the game which is hard to get without having played intensively. I have played Wesnoth, though only the first couple of single player missions. 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. 3) Communication skills 3.1) Though most of our developers are not native English speakers, English is the project's working language.  Describe your fluency level in written English.3.2) What spoken languages are you fluent in? I am a native (American) English speaker. I speak some Japanese (and have taken 5 semesters of Japanese classes). 3.3) Are you good at interacting with other players? Our developer community is friendly, but the player community can be a bit rough. In general I take a pacifistic/avoidant attitude when dealing with aggression. (I tend to ignore agression). 3.4) Do you give constructive advice? Yes. 3.5) Do you receive advice well? Yes, as long as the advice is understandable; otherwise, I'll ask for clarification. 3.6) Are you good at sorting useful criticisms from useless ones? Yes, I can tell when someone is simply being picky and when they have legitimate criticisms. 3.7) How autonomous are you when developing? Would you rather discuss intensively changes and not start coding until you know what you want to do or would you rather code a proof of concept to "see how it turn out", taking the risk of having it thrown away if it doesn't match what the project want? I tend to spend more time in design than in coding, because more time in design generally leads to a better end product. So I would probably spend a good portion of time designing, maybe sending psuedo-code or diagrams to my mentor periodically to confirm validity. 4) Project 4.1) Did you select a project from our list? If that is the case, what project did you select? What do you want to especially concentrate on? I selected the input framework rewrite. I want to concentrate on designed a menu to allow changes to the input configuration as well as logic to create a sane default configuration. 4.2) If you have invented your own project, please describe the project and the scope. 4.3) Why did you choose this project? I chose this project because I am familiar with SDL and feel that this is the best area I can contribute to. 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". Before May 24: Reading through source of Wesnoth May 24 - June 10: Reading through source and brainstorm on design June 11 - July 12: Coding of idea, lots of discussion with mentor and others on the IRC channel. July 12 - August 9 : More Coding. August 9 - August 20: Bug fixing 4.5) Include as much technical detail about your implementation as you can Please see my actual application for this info (or email me). 4.6) What do you expect to gain from this project? I expect to gain experience in working with developers in the FOSS community. 4.7) What would make you stay in the Wesnoth community after the conclusion of SOC? I would be likely to stay in the community if I felt I could make regular, meaningful contributions to Wesnoth. 5) Practical considerations 5.1) Are you familiar with any of the following tools or languages? Subversion (used for all commits) - Yes C++ (language used for all the normal source code) - Yes STL - Yes Boost - No Sdl - Yes Python (optional, mainly used for tools) - Yes build environments (eg cmake/autotools/scons) - No, but I am very familiar with make. WML (the wesnoth specific scenario language) - No Lua (used in combination with WML to create scenarios) - No 5.2) Which tools do you normally use for development? Why do you use them? I tend to use Netbeans or KDevelop. I like Netbeans because it is cross-platform, but I like the code browsing in KDevelop. For quick programs, I'll just use KATE sometimes. 5.3) What programming languages are you fluent in? I am proficient in C, C++, Java, Python, PHP. I am also familiar with bash scripting, awk, sed, and perl. 5.4) Would you mind talking with your mentor on telephone / internet phone? We would like to have a backup way for communications for the case that somehow emails and IRC do fail. If you are willing to do so, please do list a phone number (including international code) so that we are able to contact you. You should probably *only* add this number in the application for you submit to google since the info in the wiki is available in public. We will *not* make any use of your number unless some case of "there is no way to contact you" does arise! I would be happy to speak to them. (See my actual application)