Heh, I'm not surprised I lost you, we're revisiting this issue and so
it hasn't been re-presented on the list in the most coherent fashion.
So, the way I think about update history is that 'Send as' is just 1
of the entries in the update history...For example, if we could defy
the laws of 2-D computer screen physics, we could try and display the
entire log history in the detail view, which would look something like:
+ Created by xxx on xxx
+ Addressed and Sending as xxx
+ Sent by xxx on xxx
+ Being edited and updating as xxx
+ Updated by xxx on xxx
Since we don't have unlimited space, we're only showing the last
entry in the log history at a time. Sometimes, the entry describes
something has already happend (e.g. Created, Edited, Updated)
Sometimes, the entry describes something is in the processing of
happening: (e.g. Sending as, Updating as).
However, after all that, I can also see how you could separate update
history from the 'Send as' address:
Edited by xxx on xxx
Update as | select email account |v|
For now, we're optimizing for space and mushing those two together.
Does that make more sense?
Mimi
On Nov 16, 2006, at 11:44 PM, Davor Cubranic wrote:
Mimi Yin wrote:
Hi Jeremy,
Good question: Yes that's the idea behind the 'Send as' field.
It's not really the 'Send as' field. I think the best name for it
is probably *byline*. But the idea is that it dynamically updates
to display whatever happened last.
You lost me here. I thought the only reason for "send as" was to
have someone else's name appear as the creator but so that I
receive and handle all the updates (and is only relevant when using
email as the transport?). It seems a completely orthogonal concept
to update history, i.e., who last changed the item.
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
