Andreas Raab a écrit :
On 4/28/2010 11:32 PM, Stéphane Ducasse wrote:
Good but what is your point?
Compatibility and simplicity.
Come on Andreas, "simple" is not so much more precise than "cool"
and I don't think that having:
------------------
Editor class>>blinkingCursor
^ BlinkingCursor ifNil: [ true ]
EditorSetting class>>editorSettingsOn: aBuilder
<systemsettings>
(aBuilder setting: #blinkingCursor)
label:'Blinking Text Cursor')
parent: #Morphic;
target: Editor;
description: 'When true, the text cursor will blink.'
-------------------
is so much more "complicated" than
-------------------
Editor class>>blinkingCursor
<preference: 'Blinking Text Cursor'
category: 'Morphic'
description: 'When true, the text cursor will blink.'
type: #Boolean>
^ BlinkingCursor ifNil: [ true ]
-------------------
You prefer UI+domain mixing, we prefer UI separated from domain.
And yes, the SettingBrowser implementation could be improved.
I know, but I'm happy because it can be removed or remade
without any other consequence.
And compare it to the PreferenceBrowser ...
Cheers
Alain
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
