+150 !!
UIManager is the Utilities of Morphic ^^
I sent an email about restructured it but I haven't got any answer.
I think that UIManager was a good idea at the beginning. It's a bag of
UI which can be used by every classes to avoid duplications. The maor
problem with that is that the implementations of methods are done with
too hight tool, and then there is tons of bad dependencies. Jannik and
I was discussing about create multiple polymorphic UIManager classes
implementd with different level of morphic tools. This way, yo can
plug and unplug PolyMorph or things like that.
ToolSet is pretty much the same about Tools but with the specificity
to inherits from AppRegistry which allow you to switch between classes
providing tools. But it's not used.
Ben
On Dec 3, 2010, at 10:52 PM, Francisco Ortiz Peñaloza wrote:
+2 :)
On Fri, Dec 3, 2010 at 6:41 PM, Esteban Lorenzano
<[email protected]> wrote:
+1
El 03/12/2010, a las 6:25p.m., Igor Stasenko escribió:
> On 3 December 2010 21:47, Stéphane Ducasse <[email protected]
> wrote:
>> I was reading the change of benjmain to deprecate
notifyWithLabel: aString from Object.
>> Yes!
>>
>> Now he was putting it on ToolSet and I thought that I would have
put it on UIManager.
>> Now the relationship and responsibility of this two classes are
not clear to me.
>> Does anybody a clear thought on that?
>>
>
> they are related but still a bit different.
> a toolset provides an access to standard system tools like browser,
> inspector debugger etc.
> while UI manager provides an access to things like inform:,
progress bars etc
>
> My proposal remains same as before. i proposed to unify this API and
> use idioms like:
>
> Smalltalk tools browser openOn: aClass
>
> as well as
>
> Smalltalk ui inform: 'you banned'
>
> so, then we don't need to have a distinct classes, but instead a
> roles, like 'tools' , 'ui', 'browser' which
> should support corresponding protocol.
>
>> Stef
>>
>
>
>
> --
> Best regards,
> Igor Stasenko AKA sig.
>
