[sugar] Obtaining Buddy objects as contacts are encountered
Fri May 11 17:24:49 EDT 2007
On Fri, 2007-05-11 at 19:25 +0100, Simon McVittie wrote:
> On Fri, 11 May 2007 at 13:52:12 -0400, Ivan Krsti? wrote:
> > Simon McVittie wrote:
> > > 15:33 < smcv> dcbw: hmm, do we support buddies changing colour/nick/avatar at
> > > will?
> > > 15:33 < dcbw> smcv: yes, we do
> > > 15:33 < smcv> dcbw: if so, any spoofing protection is essentially worthless
> > > since they can freely change how they appear in the UI
> > When first introduced to a buddy, you store his key and name (as given)
> > as immutable, and color/nick/avatar as mutable.
> The code only seems to have 'nick', which is set to the name you enter
> when you first switch on a new OLPC. Is your position that there should
> be separate attributes, 'nick' which you can change, and 'name' which
> you can't? Is there any design in which this is documented? In the
> absence of any particular reference, I'd been assuming the code
> implements the design.
Yeah, we should do this. I assume that Vcard supports First/Last name?
Note that we also get into issues then with ordering/localization,
because some locales (Hungary, for example) use family name _first_.
But that's a problem for sugar, really.
If Vcard supports this, it should be trivial to add into the PS.
> > We must never depend on
> > just color/nick/avatar in the UI to identify people; their name, as we
> > have it stored, must always be displayed alongside their mutable
> > identifier.
> So something like, the tooltip when you hover over an XO shows you their
> nick, avatar and stored name?
> | SMcV | <-- nick chosen by user
> | Simon McVittie | <-- not present in the current implementation
> | AAAAA |
> | AAAAA | <-- AAAA = avatar
> | AAAAA |
> | (+) Add as friend |
> Sugar mailing list
> Sugar at laptop.org
More information about the Sugar-devel