[chandler-users] [d/f] Assorted Usage Notes

[Andre Mueninghoff]

I like that better, 'Notify'. However, in the user behavior department,
I'm realizing that I have been clicking the Update button in part,
because it appears at all. Changing the label to Notify may not reduce
that initial impulse. Even though I trust the sync to Cosmo/Hub,
clicking the Update button evokes Done or Commit. Is Update/Notify
perhaps really intended for propagating changes to non-Chandler users?
If so, maybe the label or tool-tip could clarify/amplify that intended
purpose. If I'm missing the point, I apologize. Wanted to give you my
candid impulse response without peeking first at the spec.

Please let me know if you have any questions.
Thanks, Andre


Mimi Yin wrote:
> Hi Andre,
> 
> Currently, if you don't hit Update, your changes are sent to the server
> and all subscribers will see them without receiving an email. Perhaps
> renaming Update to something like 'Notify' would make that clearer?
> 
> Mimi
> 
> On Jun 22, 2007, at 8:45 PM, Andre Mueninghoff wrote:
> 
>> - It seems to me there would be value in a counterpart to the "Apply
>> Changes" functionality, that is, a "Send Changes" function that would
>> permit the selective sending of field-level changes, or minimally, a
>> Don't Send Updates option at the item level. (I think this may well
>> have been covered in the specs and on the lists, but I have not read
>> all of the traffic, so sending this anyway.)
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
Url : http://lists.osafoundation.org/pipermail/chandler-users/attachments/20070625/10beed3e/signature.pgp