GSoC Engine resource abstraction - Revision history

Abma at 17:54, 2 March 2012

2012-03-02T17:54:59Z

← Older revision		Revision as of 18:54, 2 March 2012
Line 22:		Line 22:
	* Hardcoded assumptions such as cost-based targeting should be removed completely and replaced with something better		* Hardcoded assumptions such as cost-based targeting should be removed completely and replaced with something better

	~~== Possible Mentor(s) ==~~		[[Category:GSoC]]

	~~{{GSoC2010_bottom}}~~

2010-03-13T17:17:02Z

backlink and category via template

2010-03-12T16:04:34Z

Protected "GSoC Engine resource abstraction": protecting during application period [edit=sysop:move=sysop] (expires 22:00, 10 April 2010 (UTC))

← Older revision	Revision as of 17:04, 12 March 2010
(No difference)

2010-03-12T15:48:00Z

Possible Mentor(s)

← Older revision		Revision as of 16:48, 12 March 2010
Line 23:		Line 23:

	== Possible Mentor(s) ==		== Possible Mentor(s) ==

	~~[http://www.example.com FORUMLINK]~~

	[[Google_Summer_of_Code_2010]]		[[Google_Summer_of_Code_2010]]

2010-03-12T15:47:52Z

Technical details

← Older revision		Revision as of 16:47, 12 March 2010
Line 20:		Line 20:
	* The new system should completely supersede the current		* The new system should completely supersede the current
	* Sync check should be adapted to hash the new resource system		* Sync check should be adapted to hash the new resource system
	* Hardcoded assumptions such as cost-based targeting should be removed completely		* Hardcoded assumptions such as cost-based targeting should be removed completely and replaced with something better

	== Possible Mentor(s) ==		== Possible Mentor(s) ==

2010-03-12T15:23:31Z

What

← Older revision		Revision as of 16:23, 12 March 2010
Line 5:		Line 5:

	== What ==		== What ==
	The Spring engine has its roots in being a Total Annihilation clone. While this intent has been dropped quite some time ago, the TA resource system is largely present in the codebase being hardcoded in a lot of critical places.

	The old system needs to be replaced, the new one should be flexible enough to reproduce everything that the old system did and be able to imitate the behaviour of most common RTS game titles.		The old system needs to be replaced, the new one should be flexible enough to reproduce everything that the old system did and be able to imitate the behaviour of most common RTS game titles.

2010-03-12T15:23:08Z

Why

← Older revision		Revision as of 16:23, 12 March 2010
Line 2:		Line 2:

	== Why ==		== Why ==
	~~So game designers can reuse engine~~ resource system and ~~avoid all weird behaviours caused by the hardcoded assumptions all over the place~~.		Current hardcoded resource system generates defects and can produce effects which are hard to workaround for game designers which aren't willing to use it.

	== What ==		== What ==

2010-03-12T15:13:33Z

← Older revision		Revision as of 16:13, 12 March 2010
Line 4:		Line 4:
	So game designers can reuse engine resource system and avoid all weird behaviours caused by the hardcoded assumptions all over the place.		So game designers can reuse engine resource system and avoid all weird behaviours caused by the hardcoded assumptions all over the place.

	== ~~Background~~ ==		== What ==
	The Spring engine has its roots in being a Total Annihilation clone. While this intent has been dropped quite some time ago, the TA resource system is largely present in the codebase being hardcoded in a lot of critical places.		The Spring engine has its roots in being a Total Annihilation clone. While this intent has been dropped quite some time ago, the TA resource system is largely present in the codebase being hardcoded in a lot of critical places.

Line 17:		Line 17:
	== Difficulty ==		== Difficulty ==
	Estimated: medium to hard		Estimated: medium to hard

			== Technical details ==

	* The new system should completely supersede the current		* The new system should completely supersede the current

2010-03-12T15:04:02Z

standardized requirements

← Older revision		Revision as of 16:04, 12 March 2010
Line 12:		Line 12:

	== Required skills ==		== Required skills ==
	* C++		* Knowledge of C++
	* Lua		* Knowledge of Lua/C API bindings
	* OpenGL skills to adapt the engine gui (optional)

	== Difficulty ==		== Difficulty ==

2010-03-11T21:20:09Z

Background

← Older revision		Revision as of 22:20, 11 March 2010
Line 5:		Line 5:

	== Background ==		== Background ==
	The Spring engine has its roots in being a Total Annihilation clone~~; even if such~~ intent has been dropped ~~since~~ quite some time, the TA resource system is largely present in the codebase being hardcoded in a lot of critical places.		The Spring engine has its roots in being a Total Annihilation clone. While this intent has been dropped quite some time ago, the TA resource system is largely present in the codebase being hardcoded in a lot of critical places.

	The old system needs to be replaced, the new one should be enough ~~flexible~~ to reproduce everything that the old system did and be able to imitate the behaviour of most common RTS game titles.		The old system needs to be replaced, the new one should be flexible enough to reproduce everything that the old system did and be able to imitate the behaviour of most common RTS game titles.

	The engine's Lua API to fetch resources will have to be adapted to the new system, and new calls will have to be added to modify ~~it's~~ state.		The engine's Lua API to fetch resources will have to be adapted to the new system and new calls will have to be added to modify its state.

	== Required skills ==		== Required skills ==