Hi, As I explain on my most recent weekly report, my goal next week is to implement command management for the admin stuff in tpserver-cpp.
Here are some points of my current plan, please comment: - Commands will be categorized (as currently) for namespacing, useful for modules such as rulesets which may add their own commands. - There will be a "category" field alongside the "name" field to command-related frames, and allow clients to use them as they wish. - I am planning to reuse libtprl/console code for the CLI client; it will handle commands/categories locally, but the action function will send a command frame. - A single object somewhat analogous to OrderManager will maintain the list of commands and process command frames from AdminConnection. - The commands themselves will be subclasses of a new Command class, each containing custom action functions and information accessible from the base class. - I'm thinking command type IDs would be dynamically allocated. A possible exception would be some basic important commands used in non-interactive situations like the single-player wizard, but even without that the client could find them by category/name. All feedback is appreciated! Thanks. -- Aaron Mavrinac www.mavrinac.com PGP Public Key: http://www.mavrinac.com/pgp.asc _______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
