Begin forwarded message:
From: "Igor Stasenko" <siguctua@gmail.com> Date: December 5, 2008 9:37:30 AM CEST To: "Stéphane Ducasse" <stephane.ducasse@inria.fr> Subject: Fwd: [Pharo-project] UIMananger
i got strange error 'relay not permitted' when sending this mail to pharo list. So, i sending it to you.
---------- Forwarded message ---------- From: Igor Stasenko <siguctua@gmail.com> Date: 2008/12/4 Subject: Re: [Pharo-project] UIMananger To: pharo-project@gforge.inria.fr
2008/12/4 Stéphane Ducasse <stephane.ducasse@inria.fr>:
Igor
I was thinking about what you propose. I do not understand why a simple extension is not better.
I do not understand why we should involved Smalltalk
it can be different class playing as access point to tools registry. why its better - because your code does not rely on specific classes, which can be missing in image. The idead is, that to get a service (or tool) you need to send a message, without referring to specific class(es). Then any installed packages may add/remove/replace entries in registry and can be used directly by your code without any specific knownledge about who or what is standing behind it.
you write
Smalltalk tools UIManager
instead of UIManager default
or Smalltalk tools browser
instead of SystemBrowser default
it would be nice to see similar in UIManager, e.g.
manager registerTool: #colorPicker class: MyCoolColorPicker.
and then simply use:
manager colorPicker new openInWorl
I do not understand the gain of your approach.
Stef
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.