EM 1.0.0 plan 1.3.2007 ---------------------- library: * remove eiffel forum license and relicense under MIT [DONE] * occlusion / frustum culling * improve 3D collision detection * animated 3D Objects * level of detail for 3D objects * antworld example, update other examples * use multiplayer framework for antworld example - no need for player finder * document all new API and also external things like md2 modelling howto links and links to tools * fix the obsolete-finder related problems * maintain dependencies list in getting started installation doc * TODO's * mixer example is buggy (calls on void target - fixed now? Test this.) * using the borland compiler on windows it is not possible to debug EM applications that call 3D API without copying the lib files to the applications directory - this should be fixed for 1.0.0 installer: * veryfy usage of libpng13.dll - it might be that the SDL.dll we're using relies on libpng12.dll * When using the bcb-installer for em 0.9.0 there are two issues: 1. The ecf-files that are delivered for the examples have the em_c_eiffel_glue_library_ise_msc.lib instead of the one for bcb hardcoded. 2. The C-Compilation of the examples fails with "Unable to open file 'GLUT32.lib'". doc: * publish class diagram of our 3D infrastructure - basically draw Matthias' picture with a tool rather than by hand, and explain it of course EM general things ----------------- * only checkin what compiles * all examples have to work always * stick to styleguides coding: * add platform independance contracts wherever a path or a file is used * add case consitency contracts across operating systems * add contracts to allow only the use of '/' in paths doc: * please correct bugs in the doc when you realize something is not correct project management: * have one person responsible for design and a seperate one for management * management should follow the project more closely: * check deadlines of projectplans regularly * check styleguides regularly * build regularly * try to maintain a clear information policy: Who communicats what and when? * version updates of dependencies should be clearly announced * have sprints * have presentation in front students * project manager needs to start first, two weeks before others disposal of objects: * dispose from MEMORY should alway first call Precursor {MEMORY} * Then no dereferencing should happen in the call - only expanded types like BOOLEAN or POINTER etc. can be used. As the valididty of references inside the call to dispose is not guarateed by the garbage collector. last change $Date$