add GemStone-Interactions package: provide a mechanism that allows both OmniBrowser and tODE to customize interactions
tODE expects MCDictionaryRepository>>allVersionNames to exist
GsInteractions explicitly signalled (to allow for conditionally specifying a defaultActionBlock ... add GsInteractionHandler class a utility class for customizing actions for all GsInteractions ... one stop shopping ... Object>>confirm:, Object>>inform:, and Warning>>defaultAction converted to use GsInteractions ... tODE is already using GsInteractionRequest, so add logic for OmniBrowser to use GsInteractionRequest as well ... OB-Tools saved again now that the obwolete classes ExecutableBlock and ComplexBlock are no longer present in the image
fix GsInteraction defaultActions....
getting static handler for GsInteractionRequest to work in GemStone2.x
GsInteraction>>interactWith: must return the result of interaction ... another tweak to OBGemStonePlatform class>>registerInteractionRequest ... arrange to call OBGemStonePlatform class>>registerInteractionRequest when choice/inform clientForwarder is registered
straighten out selectors in GsConfirmInteraction (#cancel was overloaded)
Object>>confirm:, Object>>inform:, and Warning>>defaultAction converted to use GsInteractions ... the GemStone 2.4.x edition
take care of sent but not implemented for 2.4 and get tests to pass for 3.0
Merge branch 'dev'