User:Vaulttech: Difference between revisions

From The Battle for Wesnoth Wiki
Vaulttech (talk | contribs)
Created a page with my information
 
Vaulttech (talk | contribs)
Line 7: Line 7:


In a 4 months based approach, a very preliminar cronogram shall be:
In a 4 months based approach, a very preliminar cronogram shall be:
1 - integrate the mapbuilder and the validator - 2 months
* integrate the mapbuilder and the validator - 2 months
2 - test, bugfix and document the changes - 2 month
* test, bugfix and document the changes - 2 month


Initially, I can't give have a better cronogram.
Initially, I can't give have a better cronogram.

Revision as of 20:54, 26 March 2012


This page is related to Summer of Code 2012
See the list of Summer of Code 2012 Ideas



This is a Summer of Code 2012 student page


Description

John Gamboa - Whiteboard: Refactor the backend

There is a lack of optimization and consistency between the mapbuilder and the validator. These two classes big "entities" are intended to be integrated in one only mapbuilder-validator. Since the validator asks for the information available in the mapbuilder frequently, this should provide more efficience and solve the consistency problems.

In a 4 months based approach, a very preliminar cronogram shall be:

  • integrate the mapbuilder and the validator - 2 months
  • test, bugfix and document the changes - 2 month

Initially, I can't give have a better cronogram.

IRC

vaulttech

Questionnaire

TODO: fill out this questionnaire SoC_Information_for_Google#Does your organization have an application template you would like to see students use?

This page was last edited on 26 March 2012, at 20:54.
Cookies help us deliver our services. By using our services, you agree to our use of cookies.