Difference between revisions of "CrystalSpace client"

From BZFlagWiki
Jump to: navigation, search
(Moved category to Development)
Line 1: Line 1:
[[Category:Client]]
 
 
An ongoing effort is to provide bzflag with a [http://crystalspace3d.org crystalspace]  client.  
 
An ongoing effort is to provide bzflag with a [http://crystalspace3d.org crystalspace]  client.  
  
Line 28: Line 27:
  
 
Any developer is invited to contribute, having time and wish. I just ask to coordinate the effort with me. (atupone)
 
Any developer is invited to contribute, having time and wish. I just ask to coordinate the effort with me. (atupone)
 +
 +
[[Category:Development]]

Revision as of 21:28, 19 February 2007

An ongoing effort is to provide bzflag with a crystalspace client.

The version is very experimental and it is compatible with the 2.0 version. It will be only available via CVS, you can get it using the branch v2_0_cs_branch.

In the current status, the client is playable, but has less functionalities than the stable release, so don't get it unless you want to help that development.

That is the plan on the development, subject to change without any prior notification:

  1. Integrate bzflag client in the Crystal-Space framework, particularly regarding the event handling nature of it. (done)
  2. Handle the command line interface a la Crystal-Space: (done)
    • Option values separated by '=' instead of ' '
    • Own handling of -help
    • Request of option on the command line using CS API
  3. Joystick handling done from Crystal Space (done) This is actually having less functionality of native porting, as the force feedback is missing. I'll think I'll revert the joystick change when the work will go further.
  4. Initialize the 2d renderer engine. Should be compatible with openGL, so sdl is not an available option
  5. Crystal-Space manages the mouse, as far as possible.
  6. Crystal-Space manages the keyboard, as far as possible.
  7. Remove all the opengl from bzflag and start to render the Tank using the CS API
  8. Build the world element using CS API
  9. Build the Menu selection using the Crazy Eddie GUI
  10. Rewrite the collision detection code using the ode plugin
  11. Ship it!

My idea is to have at any stage of development a working client, so we can see the product and change the direction of development at an early stage, if that is required, or abandon this idea at all.

Actual work on this project is off line the 2.2 release. If the integration succeed, and the performance indicators are ok, only then we can think this work is good for formal release on whatever version is available at the moment. As probably crystal space is not going to be supported on alien architectures, the goal is not to substitute the old client, but to provide an enhanced version of it. We'll see.

Any developer is invited to contribute, having time and wish. I just ask to coordinate the effort with me. (atupone)