todo

#todo As aspen has been in development for a long while, we would really like to release a public stable version. The below list is a to-do list (milestones) of each item that needs to be handled before a public release can in fact be made.

At this point, no extra features should be added (unless noted here) and care should be taken to clean up, polish and complete work on the items listed. This includes bugfixes and assurance that the base is stable.

When each of these items has been checked off and tested, we may continue adding new features to Aspen under a development branch.

##Networking

• Clean up telnet and make sure it works on most common clients (this means you, MCCP).

internals

• Minimize memory usage.
• Separate some logic out from world, making World hold only pointers to individual objects as possible.
• Convert the base to use more smart pointers for better memory management.
• Code cleanup following styling guidelines.
• Add properties which can be exposed to OLC. (mostly done).
• Make OLC cleaner to use.
• Add help administration (editing, creating etc).
• Clean up components.
• Finish exposing Aspen to scripting.
• Create a configuration system which can be used to load mud data.
• Clean up the logging system.
• Clean up enums so that they are easily extendable. (This means switching to use #defines so that they can be extended. Most important for things like message types, etc).
• Add functionality to login to allow for adding extra prompts.
• Create callout groups and a mechenism by which systems can be timed, tracked and profiled; should show stats for callout execution (especially specific groups), command execution, etc.
• Extend mud configuration and document defines which will enable or disable code.

##Asthetics

• Basic code review.
• Document code using Doxygen so that API documentation can be generated. (Much progress has been mae here)
• Write tutorials and documentation on core Aspen concepts (ComponentMeta, StaticObjects, etc). These should be placed in wiki.
• Clean up code so that methods in source directly match the order of methods in header files.
• Clean up includes.
• Create developer and builder documentation as well as help files.
• Create style guidelines for contributors to follow (Naming conventions, comments, formatting, unit tests, etc). (work started on wiki)