>I don't particularly like the naming.
+1
Especially I dislike the "Morphic" in the name.
When I implement a custom window I want to react on simple events/
announcements like Activated, MouseHover, WindowClosing, WindowClosed,
SizeChanged, ... independent of the current UI frameworks name.
I think WinForms (.NET) and Java UI builders are a good template to
find appropriate names and events that should be supported at a minimum.
This also reduces the changes when switching/porting/adapting code
to a different/refactored UI framework in a possible "life after morphic" (TM) time.
It will also allow for better naming of the event handler methods
#onWindowClosed handling WindowClosed vs.
#onMorphicCreationWindowAnnouncementAnnounced ;)
just my 2 cents
bye
T.
--
Preisknaller: GMX DSL Flatrate für nur 16,99 Euro/mtl.!
http://portal.gmx.net/de/go/dsl02_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Locked
