[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   |  
------------------------------+---------------------------------------------
Old description:

> There are currently some issues and missing feature with console
> commands. I would like to compile a list here that can be discussed and
> modified:
>  1. Activity: Console commands should have the possibility to be
> active/inactive
>  1. Lifetime: Console commands should be destructible and therefore more
> dynamic
>  1. Accessibility: Console commands should have access permissions.
>  1. Dispatching: What about console commands that can be applied not to
> one single static function but to all objects of a member function? It
> would be almost like the config values but with 5 possible different
> arguments and no ini-file entry.
>  1. Preconditions: Is it really necessary that all classes using CC must
> derive from OrxonoxClass? It is of course mandatory for 4.
>
> There is already some basic construct to realise accessibility but it is
> not yet implemented. I think this might be quite important because
> sometimes these console commands ease programming by magnitudes if you
> want to avoid some singleton-hacking or so.
>
> Btw: I assigned the severity of the ticket "critical" because we
> currently have memory leaks due to console commands.

New description:

 There are currently some issues and missing feature with console commands.
 I would like to compile a list here that can be discussed and modified:
  1. Activity: Console commands should have the possibility to be
 active/inactive
  1. Lifetime: Console commands should be more dynamic so you can create
 and destroy one at will (and avoid memory leaks).
  1. Accessibility: Console commands should have access permissions.
  1. Dispatching: What about console commands that can be applied not to
 one single static function but to all objects of a member function? It
 would be almost like the config values but with 5 possible different
 arguments and no ini-file entry.
  1. Preconditions: Is it really necessary that all classes using CC must
 derive from OrxonoxClass? It is of course mandatory for 4.

 There is already some basic construct to realise accessibility but it is
 not yet implemented. I think this might be quite important because
 sometimes these console commands ease programming by magnitudes if you
 want to avoid some singleton-hacking or so.

 Btw: I assigned the severity of the ticket "critical" because we currently
 have memory leaks due to console commands.

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