|
2010-08-08
, 02:36
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#62
|
Will you be publishing the interfaces on w.m.o or somewhere else so others would use it?
What level of backwards compatibility will you be offering in the interfaces?
|
2010-08-08
, 02:43
|
|
Posts: 1,684 |
Thanked: 1,562 times |
Joined on Jun 2008
@ Austin, TX
|
#63
|
w.m.o. = wiki? Never occurred to me, but I can do that.
I didn't understand backwards compatibility - this app can only run on platforms that have qt >4.6.2 and qtmobility. I have no way to provide backwards compatibility to n8x0 or older.
|
2010-08-08
, 03:02
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#64
|
I mean keeping your interfaces backwards compatible. A user could update this application while not updating a couple others. If you changed your DBus interfaces then the apps will break.
That plus the fact that an dbus api already exists (telepathy) is why I pushed back on the idea of a dbus api
|
2010-08-08
, 03:07
|
|
Posts: 1,684 |
Thanked: 1,562 times |
Joined on Jun 2008
@ Austin, TX
|
#65
|
I agree about the backwards compatibility and also know that telepathy would be the ideal interface.
I guess providing any external interface would entail making sure that interface does not change in any future releases.
Versioning that interface is what I think I will need to do and that would need a handshake and more...
This might turn out to be much more than I had intended.
The Following User Says Thank You to epage For This Useful Post: | ||
|
2010-08-08
, 03:40
|
|
Posts: 722 |
Thanked: 1,223 times |
Joined on Apr 2010
@ USA
|
#66
|
The Following User Says Thank You to fcrochik For This Useful Post: | ||
|
2010-08-08
, 03:56
|
|
Posts: 1,684 |
Thanked: 1,562 times |
Joined on Jun 2008
@ Austin, TX
|
#67
|
The non-telepathy api only makes sense if it is really simple and right now it is - just a call with one argument. Anything more than that and I think uvatbc should just create another telepathy implementation just for the sake of it (just kidding) - there is no point on trying to create another framework.
I can't imagine why this particular api would ever have to change but if does we will have to deal with it..
|
2010-08-09
, 21:14
|
|
Posts: 722 |
Thanked: 1,223 times |
Joined on Apr 2010
@ USA
|
#68
|
The Following User Says Thank You to fcrochik For This Useful Post: | ||
|
2010-08-09
, 21:48
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#69
|
A new version of MyContacts has just been uploaded to extras-devel.
This new version can place a google voice call using qgvdial.
MyContacts as now can initiate google voice calls 3 different ways: using TOR (telepathy), using qgvdial and calling your google voice number and sending the DTMF tones for you.
Note: as now qgvdial must be running in the background and the user logged in for the integration to work.
|
2010-08-09
, 21:58
|
|
Posts: 1,684 |
Thanked: 1,562 times |
Joined on Jun 2008
@ Austin, TX
|
#70
|
Thanks!
Is there any way I can pull my google contacts into the phone without using MfE? Or do I have to write that app myself?
What level of backwards compatibility will you be offering in the interfaces?
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog