ndk

http://www.sendspace.com/file/q88fu6

ready (look first port)

latest version is 7. now my server is temporary down.

new version (at first post): +show subtitles settings in the gameplay options ~cleanup sources

work not completed. so not urgent. forum engine insert space between "." and "zip"?

since that time i learned a little more about engine. something is simplified. added rudimentary support for displaying multiple subtitles. maybe not the best solution but i not so much know gui scripts. perhaps listDef is better solution. first post is updated. P.S. time to show subtitles is set to 20 sec. for testing

oops, i forgot remove unnecessary file "subtitles_producer.h". updated.

reworked. url at first post. no new features.

it's not convenient for third party. sounds can be split into two categories: TDM sounds and FM sounds. as you see there is need to support more than one files. different events. look HL2 for example. time codes not so critical. must be support many files: [subtitles]x[language]x[FM]. in summary all my arguments are reduced to the DIP. we have a particular solution of particular problems (def, lang and so). i will write new parser but ideologically it is not good. http://en.wikipedia.org/wiki/Dependency_inversion_principle

mandatory requirement for the key name. Doom[CC] source is ugly.

idLangDict imposes restrictions on key. because subtitles required support colors, style, time code. why not?

xml has some benefits: 1) arbitrarily nesting level of structs 2) flexible modifying 3) IMHO, strategically good to move from home-made data formats (even if we are talking about ID Software) to well known technology. 4) authors of mods is not so often engaged in editing descriptions of missions. it does not cause pain and suffering. small inconvenience exchanged to strongly typed data. it's good for support new features.

as you see TDM do not uses own common parser. ID's parser too hard to use. may be it's time for implemention? i suggest again to choise format based on xml.

no such class (1.02)

in future we can take into consideration distance between player and sound source.