Allow individual applications to define their own shortcut mapping When a system wants to translate a shortcut into a logical action key, it asks a view to it's keyboard map which porivdes such translations. Histrically, there was only one such map kept in window device. To allow per-application customization, each view by default returns its parent's view map. The top level window then asks its underlaying application model for a map. This way, each application may provide its own shortcut mappings or override / inhibit global ones. Keyboard mappings may be chained to from a hiearchy: if a mapping is not found in given keyboard map, it's parent map (if any) is asked for the mapping. Usually a device's keyboard map is at the top of the hiearchy (but not necessarily)

#TUNING by cg class: Image changed: #fromImage:photometric: rgba->rgb speedup

#REFACTORING by cg class: Image changed: #fromScreen (send #getScreenBounds: instead of #screenBounds:)

#BUGFIX by cg class: Image changed: #fromScreen hack for OSX, which does not include the dock's height in the dimension returned by XQuartz

#DOCUMENTATION by cg class: XWorkstation comment/format in: #usableHeightAt:

#REFACTORING by stefan class: Color changed: #allocateColorsIn:on:

ResourcePack: print show full stack trace in case of error when reading ...the pack. The code still uses `Transcript show:...` - this should later be rewritten to use `Logger`

#TUNING by cg class: Image changed: #fromScreen:on:grab: fast image readout on OSX

#FEATURE by cg class: Image added: #drawEllipse:withColor:lineWidth: #drawEllipse:withValue:lineWidth: changed: #drawEllipse:withColor: #drawEllipse:withValue: line width

#DOCUMENTATION by cg class: Image comment/format in: #photometric: