Document Actions
#6 — Console plugins to add commands
| State | Rejected |
|---|---|
| Release: | |
| Area | Core Software |
| Issue type | Feature |
| Severity | Medium |
| Submitted by | sirloon |
| Submitted on | 2006-11-29 |
| Responsible | Sébastien Lelong |
| Target release: |
Last modified on
2007-03-03
by
Sébastien Lelong
The SirBot console commands could be enriched by others commands, more specific to the bot being
handled... This is closed from some console plugins.
Ex: a bot is able to take measure. A command 'draw', added to the known console commands, would draw
and display a picture of the bot's environment. As 'draw' is very specific to this bot, this command
definition would be as a console plugins.
handled... This is closed from some console plugins.
Ex: a bot is able to take measure. A command 'draw', added to the known console commands, would draw
and display a picture of the bot's environment. As 'draw' is very specific to this bot, this command
definition would be as a console plugins.
Added by
Sébastien Lelong
on
2007-03-02 20:39
Issue state:
new → unconfirmed
Responsible manager:
sirloon → admin
Added by
Sébastien Lelong
on
2007-03-03 10:27
Issue state:
unconfirmed → rejected
Target release:
0.1 → 0.2
Mpfff... Since the big-rewrite, those console plugins are just python functions. Maybe there could be a way to easily define them. For now, the user would have to do it from scratch. Back to the "draw" example, that's just a method of the SirBot Ranger. Nothing to do with console plugins. The idea of console plugins was a inevitable feature *before* the big-rewrite, because adding such a "draw" functionality within an XML file (protocol file), would have been to painful (would need to re-invent a language). Now things are getting simpler, so... trash this PR.
