We have covered a LOT of territory the last couple of days, so I think we
are due for a summary to date:
Phase 1
1. Server implementation to be integrated with the current FG code
a. --fgspeer= protocol module with HUD updates
b. --fgsserv= protocol module and basic reflector server
c. --headless option for standalone server operation
d. --webserv= remote config/status module
e. --commserv= community server publishing url
2. Protocol design and implementation
a. TCP streaming protocol
b. message packing/unpacking classes
c. message base class
3. Initial Radio Message set definition
a. Tower ATC messages
b. Regional ATC messages
c. Ground Traffic Control
4. Basic Community Server
a. PHP based
b. Mysql database backend if needed
c. Netscape and IE launcher integration
allows a link to start FG with correct settings
primary goal: multiplayer flight
Phase 2
1. weapons stores with FDM integration
2. dynamic shared library system for weapons behaviors
3. server extensions for ordinance instance management
4. scenario system design and initial implementation
5. web-based scenario builder design and prototype
6. community server enhancements
primary goal: shoot and record hits (no damage)
secondary goal: Red Flag scenarios
Phase 3
1. damage system integration
2. incremental system damage effects
3. FDM damage effects
4. AI surface to air weapons (AA, SAM, etc)
5. dynamic shared library system for AI pilots
6. server extensions for AI aircraft instances
7. web based scenario builder functional for current features
primary goal: blow them outa the sky !!
There is a lot more to cover, but this should be more than enough to keep us
busy for a while :)
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
