|
2010-08-11
, 17:13
|
|
Posts: 1,684 |
Thanked: 1,562 times |
Joined on Jun 2008
@ Austin, TX
|
#82
|
One of the "best" features of the n900 for me is the ability to "merge" contacts. If we just implement new "backends" one for each contact engine we will loose that. Every new "client" application will have to know how to deal with more than one backend at a time and store on a "client specific" place any "merging information".
My concern is that for the contacts api to be really useful to write client applications you don't want to have each client application to have to deal with this complexity.
|
2010-08-11
, 17:55
|
|
Posts: 722 |
Thanked: 1,223 times |
Joined on Apr 2010
@ USA
|
#83
|
Brought this up with the Qt people?
I actually wonder if we could put a wrapper around QtMobility contacts that is a drop in API that handles merging....
|
2010-08-11
, 19:19
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#84
|
I was curious if this discussion has led anyone else to start writing a Google QtMobility Contacts Engine?
If not, I think I'll start working on one. There is already another contact engine I want to write so it could be a good learning experience for me (C++ developer but never done Qt in C++ before). Maybe when QtMobility 1.1 comes out I'll also write a Google calendar engine (since I also have another calendar engine I want to write).
|
2010-08-11
, 19:21
|
|
Posts: 722 |
Thanked: 1,223 times |
Joined on Apr 2010
@ USA
|
#85
|
I actually wonder if we could put a wrapper around QtMobility contacts that is a drop in API that handles merging....
|
2010-08-14
, 22:41
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#86
|
|
2010-08-24
, 00:58
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#87
|
|
2010-08-28
, 18:02
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#88
|
|
2010-08-28
, 18:15
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#89
|
|
2010-08-28
, 18:20
|
|
Posts: 1,359 |
Thanked: 717 times |
Joined on May 2009
@ ...standing right behind you...
|
#90
|
My concern is that for the contacts api to be really useful to write client applications you don't want to have each client application to have to deal with this complexity.
My maemo work:
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
For Harmattan:
GeePS - native UI around google maps - GApp - access to optimized mobile "google apps".
Shutdown - shutdown and reboot with one click - QuickCall - one click call, skypeout and google voice integration using dial tones.
WakeOnLan - wake computers on your local network.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
For Maemo/N900:
GApp - access to optimized mobile "google apps". - MobWebMail: browser optimized to access multiple gmail accounts
MyContacts: 75 Contacts on your desktop, ring tones per group and more - GeePS: native front-end for google maps
Macuco2 : web browser to access web sites optimized for the iphone - WakeOnLan: wake up computers on your local network
dbBrowser: Simple application to browse sqlite databases