Re: [Sum] Contacts Design

Oops, I should have been clearer. The use case I had in mind was more  
along the lines of wanting to save the contents of an email as a  
contact:

Hey, here are the directions to the 'Best Restaurant in Town'
38 Spaghetti Loop
Town, State, Zip

Directions: xxx

It's really a contact-note that someone sent to you or maybe you sent  
to yourself from another email client.

I agree that saving email addresses from emails shouldn't be modeled  
as stamping.

Mimi

On Jul 12, 2007, at 11:10 PM, Davor Cubranic wrote:

> On Thursday 12 July 2007 11:03:51 you wrote:
>>
>> Stamping Contacts
>> + I think we're in agreement that Stamping Contacts to add them to
>> the Task list / Calendar and vice versa is not particularly
>> compelling, although Ted said he would use that feature. (I still
>> feel we should leave this functionality in place for now and figure
>> out how to deal with these modeling issues through some usage.)
>>
>> + I believe we're also in agreement that jotting down a Note and
>> saving an Email as a Contact *are* compelling use cases.
>
> I don't think the email use case is that compelling. The reason for  
> this
> is that the email headers shown in DV could be used to *create* a
> Contact, just the way in KMail while reading a message I can
> right-click on an address in the header pane and choose "add to  
> address
> book". Similarly, Thunderbird automatically creates a contact instance
> with just the email address filled in (and name, if it can be  
> extracted
> from the address) for every email I send, IIRC. Other mailers might
> have similar functionality, and so this kind of workflow should be
> reasonably familiar to a new user.
>
> Davor
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Design" mailing list
> http://lists.osafoundation.org/mailman/listinfo/design

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design