Opened 15 years ago
Last modified 14 years ago
#334 closed enhancement
Improve Console Commands — at Initial Version
Reported by: | rgrieder | Owned by: | nobody |
---|---|---|---|
Priority: | critical | Milestone: | |
Component: | GeneralFramework | Version: | 0.0.3 |
Keywords: | console command | Cc: | |
Referenced By: | References: |
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:
- Activity: Console commands should have the possibility to be active/inactive
- Lifetime: Console commands should be destructible and therefore more dynamic
- Accessibility: Console commands should have access permissions.
- 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.
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.
Note: See
TracTickets for help on using
tickets.