On 24/7/14 13:37, Pavel Krivanek wrote:

Hi,

in latest update we integrated several patches needed for proper working of ConfiguratonOfMorphicCore. This simple configuration loads Morphic-Core package into the minimal image and initializes it so the result is a small standalone Morphic subset.

But some issues that I would like to discuss with the community left:

SystemWindows support
============================
SystemWindow is quite complex morph that requires many of other morph classes including text morphs, theming support etc. But in several situations the system windows play special role and the Morphic core classes need to be aware of them. So we have several options:

- (current) do not have SystemWindow & co. in the image but let basic support of them. That will produce some unimplemented calls

- create very simple SystemWindow superclass that will be part of the Morphic-Core but will not have look and possibilities of real SystemWindow

- include SystemWindow and supporting classes

I had the same questions than you:
� � - I have the impression that systemWindow is really linked to widgets.

Tools
============================
The current image generated by this configuraton will crash as soon as you try to press some keyboard button. The reason is in the method Morph>>#handleKeystroke. This method contains this code to support Keymapping

Smalltalk tools shortcuts handleKeystroke: anEvent inMorph: self.

I think that keymapping should not be a tool but the default way to change and control shortcuts.
Do you have a take on this?