Hi, most of issues with shrinking to the basic headless image are related to UserManager. Currently UserManager is subclass of DummyUserManager and I really think that we should change it to use the similar approach as the UIManager. UserManager (abstract class) - DummyUserManager (for no real users management) - KeyChainUserManager (or some other name, current UserManager class) The second option is to avoid the next strange "Dummy" class and make UserManager as concrete class with void functionality. It will be called using UserManager default or UserManager current instead of current Smalltalk tools userManager that makes unwelcome dependency of the kernel on tools. BTW I think that the message #current would be much better for UIManager too because it should be possible to use multiple UIs for the same image at once (e.g. Morphic and web-based UI) What do you think? Cheers, -- Pavel
On 18 Jun 2014, at 14:43, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
Hi,
most of issues with shrinking to the basic headless image are related to UserManager. Currently UserManager is subclass of DummyUserManager and I really think that we should change it to use the similar approach as the UIManager.
UserManager (abstract class) - DummyUserManager (for no real users management) - KeyChainUserManager (or some other name, current UserManager class)
The second option is to avoid the next strange "Dummy" class and make UserManager as concrete class with void functionality.
It will be called using UserManager default or UserManager current instead of current Smalltalk tools userManager that makes unwelcome dependency of the kernel on tools. BTW I think that the message #current would be much better for UIManager too because it should be possible to use multiple UIs for the same image at once (e.g. Morphic and web-based UI)
What do you think?
Yes, sounds good. The "Smalltalk tools userManagerâ is really not good as it is not a tool in the sense of âSmalltalk toolsâ. Marcus
participants (2)
-
Marcus Denker -
Pavel Krivanek