On 6 Mar, 2007, at 15:28, Mimi Yin wrote:
Sorry this got filed into my dev folder.
Morgen, I'm fine with prompting users with a name. But I wonder if
it's clutter to have
Created by Morgen Sagen on xxx for every item in your Chandler if
you don't share or send any email?
Possibly, though we could just shorten "Morgen Sagen" to "Me" in this
case.
I think the idea was that if the user wasn't doing any of these
'Reach out and touch someone outside of your personal Chandler
repository' things, then we'd only display date info in the byline.
That's possible ... We will have to deal with that case already (no
lastModifiedBy) for items that have been edited on the server
anonymously (i.e. ticketed Cosmo UI users).
Cosmo uses the email address to do the whole receive an email
confirmation and then verify the new account.
Sure, but I'm not sure how that applies here ... i.e. in the ticketed
case, there's no account to confirm?
--Grant
On Mar 2, 2007, at 4:33 PM, Morgen Sagen wrote:
On Mar 2, 2007, at 4:13 PM, Mimi Yin wrote:
Would it be easier to add the email address field into the
Sharing account form?
That's certainly an option, although it still doesn't deal with
the situation where the Chandler user has no accounts at all.
We require one when signing up for Chandler Hub account on osaf.us.
Actually, I was wondering if Cosmo actually uses that email
address for anything.
Morgen, what happens if the user has no account information at all?
What do you want to happen? :-) I guess under the hood we would
just not have a value for the item's lastModifiedBy attribute (or
have an None/empty value), and this state might be reprsented as
"anonymous" in the byline. (?)
Actually, the more I think about it, the more I like the idea of
just having some string that identifies the user. We could prompt
them for their name the first time they launch Chandler, and they
could type in whatever they want: just a first name, first+last,
an email address, nickname, whatever. That string would be used
for the byline whenever the user modified an item, and other
people would see that string if they received an item from the
user (either via email or Cosmo).
Under the hood we'd perhaps create a Contact item to store that
user identifier. When an item arrives via email or Cosmo we would
create a new Contact to store the other user's identifier.
~morgen
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
