Editing Google Summer of Code/2009

Jump to: navigation, search

Warning: The database has been locked for maintenance, so you will not be able to save your edits right now. You may wish to copy and paste your text into a text file and save it for later.

The administrator who locked it offered this explanation: Server migration

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
The 2009 Google Summer of Code was announced in February, 2009.  BZFlag is once again participating as a mentoring organization.  Given our enormously successful participation in the program in 2007 and 2008, we are very excited to be participating again.  We accepted 4 student project proposals for 2009.
+
The 2009 Google Summer of Code was announced in February, 2009.  BZFlag is once again participating as a mentoring organization.  Given our enormously successful participation in the program in 2007 and 2008, we are very excited to be participating again.  We are accepting student project proposals from March 23 until April 3.  Hints and tips on [[Google_Summer_of_Code|getting started, preparing a submission, and the application process]] are available.
 +
 
 +
Note that for 2009, we're expecting to only accept two or three new students so that we can focus our time and attention on those individuals and our upcoming major release.  That means you're really encouraged to talk with us early on and make an outstanding project proposal.  The best way to get our attention at this time is to make bug fixes.  We look forward to working with you!
 +
 
 +
 
 +
= Promotion Flyers =
 +
 
 +
We're now soliciting designs for our 2009 GSoC promotional flyer. If you are interested in providing a design, please contact us!
  
 
= Proposal Ideas =
 
= Proposal Ideas =
Line 131: Line 138:
  
 
=== Finish server-side players ===
 
=== Finish server-side players ===
BZFlag includes players that can be run and managed from the server through a server-side plug-in.  Unlike the client-side BZRobots project, server-side robots have entirely different issues that they have to account for and information that they have access to.  This project would entail taking the work that has already been started to completion.  As this is a continuation, please do contact the developers before proposing this idea to determine the current status and work required.
+
BZFlag includes players that can be run and managed from the server through a server-side plugin.  Unlike the client-side BZRobots project, server-side robots have entirely different issues that they have to account for and information that they have access to.  This project would entail taking the work that has already been started to completion.  As this is a continuation, please do contact the developers before proposing this idea to determine the current status and work required.
  
 
'''Requirements''':
 
'''Requirements''':
Line 162: Line 169:
  
 
=== Multiple display support===
 
=== Multiple display support===
Add the ability to effectively manage multiple display environments from within the game allowing for the detection, alignment/orientation specification, and resolution parameters for each display via menu options as well as proper full-screen and/or windowed support. An additional feature could involve allowing the user to dedicate a display to the various primary GUI elements (the 3-D environment, the radar, and the chat console). BZFlag's current context management is mostly handled by SDL or other platform-specific modules, so this could be taken into consideration. There's also the possibility of our move to an integrated graphics engine would similarly impact how multidisplay contexts are created and managed.
+
Add the ability to effectively manage multiple display environments from within the game allowing for the detection, alignment/orientation specification, and resolution parameters for each display via menu options as well as proper full-screen and/or windowed support. An additional feature could involve allowing the user to dedicate a display to the various primary gui elements (the 3D environment, the radar, and the chat console). BZFlag's current context management is mostly handled by SDL or other platform-specific modules, so this could be taken into consideration. There's also the possibility of our move to an integrated graphics engine would similarly impact how multidisplay contexts are created and managed.
  
 
'''Requirements''':
 
'''Requirements''':
Line 169: Line 176:
  
 
'''Difficulty''': low
 
'''Difficulty''': low
 +
  
 
=== Cross-server communications system ===
 
=== Cross-server communications system ===
Line 220: Line 228:
 
* Bernt Hansen (Thumper_)
 
* Bernt Hansen (Thumper_)
 
* Jeff Makey (BulletCatcher)
 
* Jeff Makey (BulletCatcher)
* Jørgen Pedersen Tjernø (jorgenpt)
 
* Joshua Bodine (Constitution)
 
  
 
[[Category: Development]]
 
[[Category: Development]]

Please note that all contributions to BZFlagWiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see BZFlagWiki:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel | Editing help (opens in new window)