Comentários (91)

1 localhost comentou às Link permanente

I like Option 2 as amended by Pierre.

2 localhost comentou às Link permanente

How to apply this setting to user preferences* Do not change the user's preference* Set initial value* Set and hide FROM preferences UI

3 localhost comentou às Link permanente

Gee, this is really a very specific question !

 
I' say :
 
* How to apply it to user preferences
 
* Do not change user's preference* Set initial value* Set and prevent changes* Set, prevent changes and hide from UI
 
/Pierre

4 localhost comentou às Link de Retorno

Pierre's right on the money on this one.

5 localhost comentou às Link permanente

I prefer option 2. I wouldnt hide the possible settings in the user interface. Just turn the color of the field grey and prevent changes.

6 localhost comentou às Link permanente

I'd go for Pierre's option.Seems nice to be able to let the user still see what preferences are available but not under his control or in some cases hide these option completely so they don't even know they exist.

7 localhost comentou às Link permanente

To me, the heading and options (esp. the first) should use similar wording. The current heading (which I think's fine) and your alternatives all start "How to apply" -- so IMHO, the first option should be "Do not apply [this setting, or whatever the phrasing becomes]".

 
I guess this means I disagree with the other responses, but I feel that first you pick clear wording, then you make the wording match up and that keeps the options clearest. If the question is phrased one way and the answer's phrased a different way...I believe that's not as clear as it could be.

8 localhost comentou às Link de Retorno

Our brains have difficulties processing negated statement (try on your little kids 'Stay here' vs. 'Don't run away'), so positive statements might be easier. 'Keep' instead 'Don't change'

 
How about:
 
* Keep the user's setting as they are* Provide default setting and allow change* Set and lock the setting
 
instead of 'setting' 'value' or 'preference' might be a good fit too.

9 localhost comentou às Link de Retorno

How about substituting "Save Changes" for "Set and Prevent Changes"

10 localhost comentou às Link permanente

I agree with Pierre on this one.And here's a little very specific request: Please let us use shortname in the email address and mailfilename when registering users through the administrator client. It's been an annoying little mishap until now... Thanks :-)

 
Cheers,Hans

11 localhost comentou às Link permanente

Hi, here is my opinion:

 
1. Accept user's prefernce2. Set as default and allow user's modifications3. Set and prevent user from modifying
 
I prefer a bit longer choice labels, but 100% clear as soon as you read them.

12 localhost comentou às Link permanente

I agree with Pierre as well.

13 localhost comentou às Link permanente

@Hans

 
I would recommend ‘ID Manager’ from http://www.helpsoft.com
 
It’s Profile driven, so you can use the shortname in the email address and mailfilename when registering users and is the only User Management Tool for Lotus Notes on the market with the ability to create a NOTES.INI and CONFIG.TXT file that can be used to perform a silent Lotus Notes Client set-up.

14 localhost comentou às Link permanente

My 2c.

 
Setting this Preference - Leave current preference setting - Set once - Set and lock
 
Another 3c or so:Since these options will be seen by about 1/1000th of the Notes user community (the admins), isn't just about anything else more important :-)
 
Luke

15 localhost comentou às Link permanente

Option 2 is my choice. Even I understood it :-)

 
Howard

Incluir um Comentário Incluir um Comentário