Bug 5453 - Add google as a source for contact information (feature request)
: Add google as a source for contact information (feature request)
Status: NEW
Product: Hermes
General
: unspecified
: All Linux
: Low enhancement with 18 votes (vote)
: ---
Assigned To: unassigned
: general
:
:
:
:
  Show dependency tree
 
Reported: 2009-10-14 22:38 UTC by Zach Goldberg
Modified: 2011-02-28 06:41 UTC (History)
5 users (show)

See Also:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description Zach Goldberg (reporter) 2009-10-14 22:38:02 UTC
This is a feature request to add google as a source for user data (in addition
to twitter and facebook) to hermes.
Comment 1 Andrew Flegg maemo.org 2009-10-14 23:49:27 UTC
How would you imagine it working? Are you talking about Google Contacts? If so,
doe "Mail for Exchange" not work well? (I don't know, I don't really use Google
Contacts)
Comment 2 Zach Goldberg (reporter) 2009-10-14 23:51:49 UTC
Contacts does (sort've... but thats another story) work with Mail for Exchange,
however things like avatar/image don't seem to get downloaded through that.
Comment 3 Andrew Flegg maemo.org 2009-10-15 11:51:09 UTC
(In reply to comment #2)
> Contacts does (sort've... but thats another story) work with Mail for Exchange,
> however things like avatar/image don't seem to get downloaded through that.

Ah, OK. Hopefully there's a Google Contacts API which can be used to retrieve
photos for contacts.
Comment 4 John Rudd 2009-11-18 07:23:28 UTC
I would also like to see more support for Google Contacts.  Not just name,
email address, and image/avatar, but most importantly to me (now that Maemo is
a phone OS) are the contact's _PHONE_ numbers.
Comment 5 hex 2009-12-02 11:27:05 UTC
I was surprised this wasn't in the release. This is almost a common
expectation.

MfE is not really an option unless you change MfE to support multiple accounts.
MfE should be for work (Google only recently put EAS client support in beta).

They have very good APIs and yes they do pull over every field and contact
photos.

A couple suggestions:

1) Allow native support for contacts (calendar would be a natural complement,
but that belongs in a different request) that doesn't require using MfE.

2) Support unlimited fields (e.g. email addresses, phones, IMs, web sites) and
ensure notes synch (doesn't work on MfE). Support this and you then have the
ability of unlimited flexibility and won't really have to touch again for any
other service.

3) Add feature (this may go elsewhere) to send contact directly to VM.

4) Allow marking of default number and sorting.

5) Allow ability to mark favorite that sorts to top of list in phone book, or
better, creates a tab (prevents us from filling up desk real estate with those
we need to dial often - esp. when driving the bus you're riding in :-)

The storage for contacts is so minimal that this shouldn't cause any issue even
for those rare people with a couple thousand.
Comment 6 Andrew Flegg maemo.org 2009-12-02 16:00:38 UTC
(In reply to comment #5)
> I was surprised this wasn't in the release. This is almost a common
> expectation.

This bug report is talking about Hermes, a third-party appliction:

     http://hermes.garage.maemo.org/

> 1) Allow native support for contacts (calendar would be a natural complement,
> but that belongs in a different request) that doesn't require using MfE.

Hermes doesn't use MfE.

> 2) Support unlimited fields (e.g. email addresses, phones, IMs, web sites) and
> ensure notes synch (doesn't work on MfE). Support this and you then have the
> ability of unlimited flexibility and won't really have to touch again for any
> other service.

I don't quite understand what you mean, perhaps this is because what you've
written above doesn't apply to Hermes. If it does, I apologise.

> 3) Add feature (this may go elsewhere) to send contact directly to VM.

VM?

> 4) Allow marking of default number and sorting.
> 5) Allow ability to mark favorite that sorts to top of list in phone book, or
> better, creates a tab (prevents us from filling up desk real estate with those
> we need to dial often - esp. when driving the bus you're riding in :-)

These almost certainly don't apply to Hermes. However, a tip for future don't
combine multiple requests/bugs into a single issue as it'll hinder fixing.
Comment 7 hex 2009-12-02 16:19:38 UTC
Apologies - was late for me and saw the comment on using mfe so thought this
was talking about contacts in general, not hermes.
Comment 8 Jack Tanner 2010-02-26 22:40:15 UTC
To clarify, the reason that it'd be great if Hermes could support Google
Contacts is that it could use Google's native gdata protocols.

http://code.google.com/apis/contacts/docs/3.0/developers_guide.html

This means that it could get at more of the data than MfE. (MfE is a red
herring, it has nothing to do with this request, and it doesn't officially
support Google anyway.)