[Tickets] [Orxonox] #334: Improve Console Commands

[Orxonox]

#334: Improve Console Commands
------------------------------+---------------------------------------------
 Reporter:  rgrieder          |        Owner:  nobody
     Type:  enhancement       |       Status:  new   
 Priority:  high              |    Milestone:        
Component:  GeneralFramework  |      Version:  0.0.3 
 Severity:  critical          |   Resolution:        
 Keywords:  console command   |  
------------------------------+---------------------------------------------
Comment (by rgrieder):

 I've got a proposition on how to implement points 1, 2 and 4:
 Every Console Command must be declared statically (resolves language
 issues), but can be declared in a way that makes it dynamic. The CC could
 then be activated with something like activateConsoleCommand() or
 activateConsoleCommand(this). The latter could be called more than once
 for multiple instances of a class.
 deactiveConsoleCommand([this]) would deactivate it (for this instance).

 Point 2 (Lifetime) would inevitable drop out because all commands get
 statically handled anyway. And there I also propose to store all commands
 in the CommandExecutor instead of the identifier (which only keeps a
 reference to it). This is mainly for consistency because CCs without
 corresponding class have to be stored there anyway.

-- 
Ticket URL: <http://www.orxonox.net/ticket/334#comment:3>
Orxonox <http://www.orxonox.net>
Orxonox Open Source game