[Chandler-dev] Restructuring Chandler Quick Entry code

[Phil Jones]

Hi,

I'm Phil Jones, Google Summer of Code student, and I am working on 
restructuring the Chandler quick entry code to be able to more easily 
add commands and functionality.

There are a couple of different approaches that JeffreyH and I have been 
discussing, and I am just looking for some feedback.

Also, if anyone has any good reasons why to use one approach over the 
other, please share your thoughts.

Approach 1:
Restructure the quick entry commands code into a parcel and persistently 
install into a known location in Chandler.
Extending would create a persistent command parcel and hook into this 
quick entry code.
Quick entry would iterate through the commands to determine what 
commands are available.

Approach 2:
Use a standard dictionary that is in a known location in Chandler to add 
new keys with a callback function.
Each of these additions can be performed in a parcel, and work similar 
to the first approach but are not stored using the same persistent 
mechanism.

Please let me know if you are confused as I am still relatively new to 
the Chandler project so I may be using the incorrect terminology or 
explaining in a way that does not make sense.

Thanks,
Phil Jones