Known To-dos of Web Command Prompt

At this stage, I still have a few things to do and make the command prompt useful.

• Is the current architecture good? I should use more delegates/callbacks and give more flexibility to third party users for integration.
• Hook up Command Parsing - This will register user's custom commands with their custom processing function. 80% done.
• Add Build-In Commands - In addition to "clear” and "cls",  "Man", "Help" should be part of the default commands set, this way, for starters, they can view a list of available commands and how to use them
• Add additional methods in ICommand Interface - force plug-in authors to provide "help" method implementation. This way when "help" is entered, we can quickly hit back plug-In author's help method and display their documentation appropriately.
• Integration with AjaxPro.Net - creates a few samples for testing purpose and sees what else I could add to the base class. One I can think of right now is to print "DataTable" to command prompt screen which is the default return type of AjaxPro.NET
• Finish Log4J implementation - This will enable users to debug their command plug-in with richer options. I will follow the standard convention of Log4J using Info, Debug, Warn, Error and etc.

Features half baked and still seeking technical solutions

• How to enable auto complete in a text area in Firefox? Got my div shown up correctly in IE, but firefox seems to lack such feature.
• How to resize a textarea?
• How to resize content of Prototype Window? Does prototype window provide a onDrag Event handler?

Backend framework I would like to sample with

• MS Log Parser - I know I can retrieve log data using MS Log Parser. Use AjaxPro.NET and build on top of that, display server stats back to command prompt.