So far I extracted these workarounds from the Zero framework:
Font management - ATM FIFE uses the gui lib for font handling, even for non-gui related fonts (e.g. fonts that are used via the GenericRenderer). I recommend we add a proper fontmanager (e.g. like the new image manager) and make fonts resources (like sounds, images etc) instead of gui elements. Personally, I´d say this has a high priority as the current solution is a hack.
Video support. ATM FIFE has no video support; therefore we scripted a Intro-Video (*click*
) by using the renderer directly (think timers & a lot of work). It would be nice to just give FIFE a video file instead and place it either within (special) gui elements and/or have the ability to let FIFE play videos if no gui is present.
Sound management - already described by prock here: http://forums.fifengine.net/index.php?topic=490.msg2233;boardseen#new
Like font management, I´d say this is mandatory as a good sound support is important for games (just being able to play a sound is not enough). Also, current sound implementation has some issues, like bad performance (sound file access introduces lags, especially noticeable if animations are played). We wrote a simple soundmanager for Zero, mainly to handle all registered soundfiles AND for providing different sound channels (video, music, sound fx ...). The channels can be controlled via sliders in the options screen (*click*
) to allow the player to e.g. mute ambient music and set special fx volume to desired values (etc.).
I´ll keep digging, I bet there are some more workarounds we use