Talking about theme, I just want to say that I like the Glamour theme very much.
Alexandre
On May 14, 2013, at 3:59 PM, Tudor Girba wrote:
> Hi,
>
> I was rather thinking of having the theme be a composable factory:
> - for each morph, we would have a factory that would know how to work with
Hello
2013/5/15 stephane ducasse
> > Hi,
> >
> > I was rather thinking of having the theme be a composable factory:
> > - for each morph, we would have a factory that would know how to work
> with that morph. In essence for the GroupBoxMorph, we would have the method
> below in a GroupBoxFactory
Hi,
On May 14, 2013, at 10:18 PM, stephane ducasse wrote:
>
>> Hi,
>>
>> I was rather thinking of having the theme be a composable factory:
>> - for each morph, we would have a factory that would know how to work with
>> that morph. In essence for the GroupBoxMorph, we would have the method b
> Hi,
>
> I was rather thinking of having the theme be a composable factory:
> - for each morph, we would have a factory that would know how to work with
> that morph. In essence for the GroupBoxMorph, we would have the method below
> in a GroupBoxFactory.
Why a factory and not just the morph?
StandardWindow>>defaultColor
"Answer the default color/fill style for the receiver"
^self theme windowColor
to me I would put windowColor as a variable of the window.
Stef
On May 14, 2013, at 4:55 PM, Stéphane Ducasse wrote:
> esteban
>
> I discussed with damien and
- Original Message -
> From: Benjamin
> To: Discusses Development of Pharo
> Sent: Tuesday, May 14, 2013 4:22 PM
> Subject: Re: [Pharo-dev] about theme and friends
>
> Ok, my bad :)
>
> This is a massive refactoring, but indeed, it may be cool :)
> Ben
>
> On M
On May 14, 2013, at 10:03 PM, Dennis Groves wrote:
> How do I get off this list? I never subscribed - so I don't have a login. :(
Ask nicely :)
We never added you so someone should have done it.
We will remove you.
>
>
> --
> [Dennis Groves](http://about.me/dennis.groves), MSc
> [Email me]
On May 14, 2013, at 10:04 PM, "Dennis Groves" wrote:
> How do I get off this list? I never subscribed - so I don't have a login. :(
>
I will remove you.
But it's strange. I took all email addresses that where in the old
pharo-project list and added
them here. So the other list did send mails
How do I get off this list? I never subscribed - so I don't have a
login. :(
--
[Dennis Groves](http://about.me/dennis.groves), MSc
[Email me](mailto:dennis.gro...@owasp.org) or [schedule a
meeting](http://goo.gl/8sPIy).
"Unless someone like you...cares a whole awful lot...nothing is going
Hi,
I was rather thinking of having the theme be a composable factory:
- for each morph, we would have a factory that would know how to work with that
morph. In essence for the GroupBoxMorph, we would have the method below in a
GroupBoxFactory.
- the UITheme simply stores all these factories, an
Looking at the code I have the impression that many UITheme methods should be
moved to the their classes
Example:
UITheme>>newGroupboxIn: aThemedMorph label: aString
"Answer a groupbox with the given label."
^GroupboxMorph new
font: self labelFont;
14, 2013 4:22 PM
Subject: Re: [Pharo-dev] about theme and friends
Ok, my bad :)
This is a massive refactoring, but indeed, it may be cool :)
Ben
On May 14, 2013, at 5:18 PM, stephane ducasse
wrote:
On May 14, 2013, at 5:13 PM, Benjamin
wrote:
The problem is the
Ok, my bad :)
This is a massive refactoring, but indeed, it may be cool :)
Ben
On May 14, 2013, at 5:18 PM, stephane ducasse wrote:
>
> On May 14, 2013, at 5:13 PM, Benjamin
> wrote:
>
>> The problem is the overlapping.
>> For settings, different project do not define the same settings.
>>
On May 14, 2013, at 5:13 PM, Benjamin
wrote:
> The problem is the overlapping.
> For settings, different project do not define the same settings.
>
> But for tools, it's different
> By example, Browser, and Nautilus will try to register to default browser.
I'm not talking about this level.
No
The problem is the overlapping.
For settings, different project do not define the same settings.
But for tools, it's different
By example, Browser, and Nautilus will try to register to default browser.
Ben
On May 14, 2013, at 4:55 PM, Stéphane Ducasse wrote:
> esteban
>
> I discussed with dam
esteban
I discussed with damien and I think that now I got the solution. In fact the
architecture should be the same than the
one of settings.
Every widget should have custom hooks and setter, getter and default values.
The hooks should be annotated or registered seomwhere.
Then the widget code
16 matches
Mail list logo
