[Pharo-project] Usability with too many Deprecation Warnings dialogs (Settings framework)
I'm using latest Pharo-Core with OmniBrowser and it's unusable with so many warning dialogs raising all the time in every operation : Opening an OB browser for example requires 6 Proceed clicks from an user with messages like this one: "The method Preferences class standardButtonFont has been deprecated. now accessible via the new setting framework " To modify this setting you could change the default to false in Deprecation initialize: Preferences addBooleanPreference: #raiseDeprecatedWarnings category: #general "programming?" default: false balloonHelp: 'If enabled, use of a deprecated API raises a Deprecated warning.'. but this would modify the Deprecation behavior for all deprecations (not just those related with the Preferences-Settings migration). To me it sounds like one should to consider two kinds of deprecations: -Those which need to raise a dialogs -Those which doesn't want to because it would affect usability (like right now in Pharo with OB). I've just attached a specific message for deprecations requiring active interaction for the user (#deprecatedWithPopUp). This addition doesn't require to modify all the current #deprecated: senders, but you should explicit modify with the #deprecatedWithPopUp variant in those places you consider of enough importance to keep the user informed. The Transcript notification behavior keeps intact. Feel free to change it anyway you want :) Cheers, Hernán
Hi hernan 1.1 is under work. Alain told me that he will kill all the call to deprecated methods soon. I was planning that too. Good idea for the PopUp Stef On Dec 6, 2009, at 5:46 AM, Hernán Morales Durand wrote:
I'm using latest Pharo-Core with OmniBrowser and it's unusable with so many warning dialogs raising all the time in every operation : Opening an OB browser for example requires 6 Proceed clicks from an user with messages like this one:
"The method Preferences class standardButtonFont has been deprecated. now accessible via the new setting framework "
To modify this setting you could change the default to false in Deprecation initialize:
Preferences addBooleanPreference: #raiseDeprecatedWarnings category: #general "programming?" default: false balloonHelp: 'If enabled, use of a deprecated API raises a Deprecated warning.'.
but this would modify the Deprecation behavior for all deprecations (not just those related with the Preferences-Settings migration).
To me it sounds like one should to consider two kinds of deprecations: -Those which need to raise a dialogs -Those which doesn't want to because it would affect usability (like right now in Pharo with OB).
I've just attached a specific message for deprecations requiring active interaction for the user (#deprecatedWithPopUp). This addition doesn't require to modify all the current #deprecated: senders, but you should explicit modify with the #deprecatedWithPopUp variant in those places you consider of enough importance to keep the user informed. The Transcript notification behavior keeps intact. Feel free to change it anyway you want :) Cheers,
Hernán <Deprecation.st><Object-deprecatedWithPopUp.st>_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Stéphane Ducasse a écrit :
Hi hernan
1.1 is under work. Alain told me that he will kill all the call to deprecated methods soon
yes but only inside the core. I will also change deprecation messages. They have to give the new equivalent method if any (current message is stupid) but, i will not check external packages...
no stress alain. We really appreciate all the work you do :) Stef On Dec 6, 2009, at 11:02 AM, Alain Plantec wrote:
Stéphane Ducasse a écrit :
Hi hernan
1.1 is under work. Alain told me that he will kill all the call to deprecated methods soon
yes but only inside the core. I will also change deprecation messages. They have to give the new equivalent method if any (current message is stupid) but, i will not check external packages...
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Hi all, Sorry, sorry, sorry, I'm the author. But please consider two things, it's the alpha 1.1 and that package maintainers must be warned. Anyway, you can already avoid having deprecation popup and redirect deprecation warning to the Transcript with the help of two existing preferences: #raiseDeprecatedWarning #showDeprecationWarning (accessible with the old preference browser). Sorry again. cheers Alain Hernán Morales Durand a écrit :
I'm using latest Pharo-Core with OmniBrowser and it's unusable with so many warning dialogs raising all the time in every operation : Opening an OB browser for example requires 6 Proceed clicks from an user with messages like this one:
"The method Preferences class standardButtonFont has been deprecated. now accessible via the new setting framework "
To modify this setting you could change the default to false in Deprecation initialize:
Preferences addBooleanPreference: #raiseDeprecatedWarnings category: #general "programming?" default: false balloonHelp: 'If enabled, use of a deprecated API raises a Deprecated warning.'.
but this would modify the Deprecation behavior for all deprecations (not just those related with the Preferences-Settings migration).
To me it sounds like one should to consider two kinds of deprecations: -Those which need to raise a dialogs -Those which doesn't want to because it would affect usability (like right now in Pharo with OB).
I've just attached a specific message for deprecations requiring active interaction for the user (#deprecatedWithPopUp). This addition doesn't require to modify all the current #deprecated: senders, but you should explicit modify with the #deprecatedWithPopUp variant in those places you consider of enough importance to keep the user informed. The Transcript notification behavior keeps intact. Feel free to change it anyway you want :) Cheers,
Hernán
------------------------------------------------------------------------
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
participants (3)
-
Alain Plantec -
Hernán Morales Durand -
Stéphane Ducasse