update docs a bit
Issue #28: getting started on menu implementation
Issue #28: checkpoint ...
Issue #28: rename actionSpec to menuActionSpec
Issue #28: handle submenus
Issue #28: continue menuActionSpec theme...define standard submenus
Issue #28: checkpoint ... defining menuActionSpecs for all of the windows ... will implement the menuActionSpecs next ...
add `mc fileout` and `gs fileout` commands ... aimed at providing fileout support that is compatible with saving source as .gs files
Issue #28: defined #menuActionSpec for all subclasses of TDClientListElementBuilder ... covers all keyboard shortcuts ... time to define the menuActionBlocks
Issue #28: start defining `menu actions` ... starting in TDClientListElementBuilder ..
Issue #28: finish initial foray into menus for tODE ... now that we've got menus, there are plenty of oppotunities to expand the menu items (and/or reorganize).... still need to do text window menus ..

Issue #33: continue/restart menu items available in debugger
create `mm fileout` command for doing a fileout of a full configuration .... `gs fileout` command finished up for this round:

  - one file per class (will change this to allow for alternate groupings)
  - extension methods overrideds changed in place in existing files new
    methods added to end
  - hard-wired class to filename map (will make this an option)
pull filename map out as arg to `mc filout` API which filters over to changes in the `fs fileout` API.
add variant of `mc fileout`/`gs fileout` API that writes class defs to one file and class methods to another file ... this is the one I will use for deploying Indexing changes for GemStone 3.2.
`mc fileout` will now file out source to files (classes and methods) or a single file.. make the `gs fileout` command compatible with the gemstone filein process (entails building our own versions of the class-based fileout methods)
checkpoint scripts
Fix TDFileSystemLeafNode, so you can save files to disk...
create gemstone install script
add pharo2.0 compat package and methods
add support for working with classes "imported" from another GemStone user's symbolList. A TDDefinition may have a `username` specified and if so the definition will use the symbolList of the given user for resolving class/global names. Trying to propogate the username as far as possible forced me (in a good way) to use class definitions EVERYWHERE instead of direct class refs and it follows that the class definition does the lookup and so on ... touch a fair amount of code across a bunch of element builder classes, so there still might be glitches ... added `inspect builder` to window menu ....