Google Summer of Code: 2015
(Created page with "== Small functionality tweaks/additions == These are small tasks to get a student or potential contributor familiar with the inner-workings of ENIGMA. They are minor tasks which ...")
Newer edit →
Revision as of 22:09, 7 February 2015
Small functionality tweaks/additions
These are small tasks to get a student or potential contributor familiar with the inner-workings of ENIGMA. They are minor tasks which would take less time for a mentor to implement than explain, but they have actually not been done yet, and so are good candidates for introductory tasks.
- Rename resources whose names are not valid identifiers. Right now, ENIGMA will let you name a sprite "while" or "if" or "Mario's Cap" or "string." These resources can cause name conflicts and should be assigned a different name, or no name at all.
- Sound system improvements. The current implementations of
sound_volumeis not working, and
- Particle system features. The current particle system is missing attractors, and in general offers plenty of room for improvement.
API Extension Tasks
These are large, modular tasks which would require elevated interest in a topic. They are potentially the most fun and the most useful.
- Add support for Scalable Vector Graphics. ENIGMA currently supports only pre-rasterized graphics resources. This task would involve adding a method to rasterize vector graphics. After that, at the student's option, this task could be extended to render vector graphics live in-game. Prior experience with OpenVG is a plus. Prior experience with OpenGL is strongly encouraged.
- Further Box2D support. FEATURE REQUEST: ELABORATION REQUIRED
- A polygon editor. Used primarily for designing polygon collision masks. Work points include a marching-squares algorithm (or the like) for bitmap tracing, and a point editor.
- Texture groups. Add support for generating texture atlases to the IDE, then support writing them in the backend (compiler).
These tasks would be useful to the project, but require special skills or equipment. They are listed in case a student has a deep interest in a subject, coupled with existing skills. Mentors will be less able to assist with these tasks.
- Support for virtual reality displays, such as Oculus Rift. Design and implement a simple-to-use API for virtual reality development in existing games. This would require a VR device for testing, and the team does not presently have any experience with these APIs.
- Recode LateralGM frontend using JavaFX. This is a large, UI-intensive task. Mentors would be able to assist, but the magnitude of work and learning curve seems too high for a GSoC task for an inexperienced student. Mentors would potentially not suffice.