1,510
edits
Difference between revisions of "OpenTasks"
Return back CinE task. Add CruisE task
(Removed some obsolete / boring tasks) |
(Return back CinE task. Add CruisE task) |
||
| Line 169: | Line 169: | ||
This shouldn't require any deeper knowledge of the game engine. The renderer appears to be fairly well separated from the rest of the engine already. | This shouldn't require any deeper knowledge of the game engine. The renderer appears to be fairly well separated from the rest of the engine already. | ||
=== Objectify CinE engine === | |||
''Technical Contact'': [[User:Sev|Eugene Sandulenko]] | |||
''Background:'' | |||
The cinE engine started out as an external project started by [[User:Yazoo|Yaz0r]]. Originally it was written in plain C. | |||
ScummVM is a C++ project, so we need to objectify this engine without changing/breaking its behavior. | |||
The engine itself is well-structured, hence many functions / variables which might be good candidates for being grouped together into a C++ class are already grouped by files. | |||
No deep knowledge of the engine internals is required, but in any case the Engine is not that big, and thus | |||
it should be possible to learn enough about it to start working in a relatively short amount of time. | |||
We have previously "objectified" several other engines, namely SAGA, Gob and AGI, so one can learn a lot about various approaches how to do this by tracing through our SVN repository. | |||
As a bonus you may consider finishing support for Operation Stealth game, but this task has much higher complexity. | |||
=== Objectify CruisE engine === | |||
''Technical Contact'': [[User:Sev|Eugene Sandulenko]] | |||
''Background:'' | |||
The cruisE engine also started out as an external project started by [[User:Yazoo|Yaz0r]]. Originally it was written in plain C. | |||
ScummVM is a C++ project, so we need to objectify this engine without changing/breaking its behavior. The engine is fairy complete, but also suffers from portability problems, that is it works correctly only under little-endian, alignment-agnostic CPUs. | |||
The engine itself is well-structured, hence many functions / variables which might be good candidates for being grouped together into a C++ class are already grouped by files. | |||
No deep knowledge of the engine internals is required too. | |||
We have previously "objectified" several other engines, namely SAGA, Gob and AGI, so one can learn a lot about various approaches how to do this by tracing through our SVN repository. | |||
=== Add 16bit graphics support to SCUMM engine === | === Add 16bit graphics support to SCUMM engine === | ||