Matthew Fulmer a écrit :
> On Fri, Mar 06, 2009 at 10:36:13AM +0100, Alain Plantec wrote:
>
>> themePreference
>> <preference>
>> ^ ThemePreference
>> ifNil: [ThemePreference := MultiplePreferenceValue
>> name: 'UITheme'
>> description: 'The theme to use for UI look and feel'
>> parent: #uiPreferenceNode
>> type: #UITheme
>> default: UIThemeWatery2
>> values: {
>> FixedPreferenceValue
>> name: 'Standard Squeak'
>> description: 'Standard Squeak style'
>> type: #UITheme
>>
>> value: UIThemeStandardSqueak.
>> FixedPreferenceValue
>> name: 'Watery 2'
>> description: 'Similar to a nice OS'
>> type: #UITheme
>> value: UIThemeWatery2}]
>>
>
>
Hi Matthew,
> You're really just inventing a half-baked Magritte now.
Surely, but, for now, Magritte is not in the base system.
Maybe you can send some advices or ideas about how we can improve
the preference system.
And the <preference:ziag:zig:> way is still a solution we can adopt back
if the pharo community prefers it.
> Do
> yourself a favor and use the real thing. Magritte is far more
> descriptive and far less verbose than anything you have yet
> presented. Magritte also already knows how to automatically create both
> seaside and morphic forms out of a field description. It also
> knows more ways to look up a field than just selector and block.
>
Anyway, it seems very interesting and I would like to learn a bit about
Magritte even it is not possible to use it for preferences.
As an example, could you explain how you specify the themePreference
with Magritte ?
Maybe it can help us to improve our implementation.
Thanks
alain
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
