Hi,
I am not sure I understand, so let's get more specific. We talk about one
package which contains one Morph.
I thought the purpose of UITheme is to encapsulate all decisions related to how
a morph gets rendered. It's like a strategy.
For example, we have UITheme>>plainGroupPanelBorderStyleFor: and this is called
by the PlainGroupboxMorph.
In the same style, I have:
UITheme>>growlLabelColorFor: aGrowlMorph
^ Color white
GrowlMorph>>labelColor
^ self theme growlLabelColorFor: self
Is this not the intended way?
Doru
On 15 Feb 2012, at 18:04, Igor Stasenko wrote:
> On 15 February 2012 17:02, Stéphane Ducasse <stephane.duca...@inria.fr> wrote:
>>
>> On Feb 15, 2012, at 1:58 PM, Tudor Girba wrote:
>>
>>> Hi,
>>>
>>> It's not UIManager, but UITheme. I made it dependent on the UITheme in
>>> the sense that I moved all the rendering code as an extension. I
>>> thought this is the official way to get things working with Polymorph.
>>> Did I get it wrong?
>>
>> I do not know. I'm still confused by the responsibility of UITheme vs
>> UIManager vs…
>> Now you do not want that every tools add method to UITheme because imagine
>> that we do that
>> then how each theme can be modular?
>>
>
> Imo, it is simple: the right to use ui theme should have only those
> object, which actually
> responsible for ui: widgets and perhaps ui builders.
> The rest of world should assume UITheme not exists.
>
>
>> so far I do not have the right answer.
>> Now GrowlMorph should have setting and get initialized from the UITheme
>> settings
>>
>>
>>
>>>
>>> Cheers,
>>> Doru
>>>
>>>
>>> On Wed, Feb 15, 2012 at 1:54 PM, Stéphane Ducasse
>>> <stephane.duca...@inria.fr> wrote:
>>>>
>>>> On Feb 15, 2012, at 1:47 PM, Tudor Girba wrote:
>>>>
>>>>> Indeed, this is a project that is since too long on my to do list.
>>>>>
>>>>> I worked on Growl a bit as well, but we need to bring it further. I
>>>>> just pushed the to do towards the top of the list :) I would be happy
>>>>> to collaborate on this issue.
>>>>
>>>> Would be good.
>>>> Doru could you fix the fact that if I remember correctly you make it
>>>> dependent on the UIManager?
>>>> or something like that?
>>>> But we could really add it to the image so that we have vanishing messages
>>>> :)
>>>>
>>>>>
>>>>> Cheers,
>>>>> Doru
>>>>>
>>>>>
>>>>> On Wed, Feb 15, 2012 at 1:38 PM, Stéphane Ducasse
>>>>> <stephane.duca...@inria.fr> wrote:
>>>>>> There is a Growl in Pharo. I improved it :)
>>>>>>
>>>>>> Stef
>>>>>>
>>>>>> On Feb 15, 2012, at 12:42 PM, Camillo Bruni wrote:
>>>>>>
>>>>>>> gargl....
>>>>>>>
>>>>>>> we should have some non-interactive inform: like Growl on Mac.
>>>>>>> The popups should just open but not block the interaction IMO.
>>>>>>>
>>>>>>>
>>>>>>> On 2012-02-14, at 23:50, Igor Stasenko wrote:
>>>>>>>
>>>>>>>> i started tests and leaved image for a while, but when i went back
>>>>>>>> hoping that it already finished, i discovered that it waiting for me
>>>>>>>> to press ok
>>>>>>>> and did not ran even 20% of all tests.
>>>>>>>>
>>>>>>>> Somewhere in GoferOperationTest>>testMerge
>>>>>>>> it says 'No changes' and waits for the user to press 'ok'
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Best regards,
>>>>>>>> Igor Stasenko.
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> www.tudorgirba.com
>>>>>
>>>>> "Every thing has its own flow"
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> www.tudorgirba.com
>>>
>>> "Every thing has its own flow"
>>>
>>
>>
>
>
>
> --
> Best regards,
> Igor Stasenko.
>
--
www.tudorgirba.com
Innovation comes in least expected form.
That is, if it is expected, it already happened.
