Active Topics

 



Notices


Reply
Thread Tools
epage's Avatar
Posts: 1,684 | Thanked: 1,562 times | Joined on Jun 2008 @ Austin, TX
#61
Originally Posted by uvatbc View Post
Alrite this one is for fcrochik and thanks to fcrochik:

This build introduces a dbus server made so that fcrochik's MyContacts can call out using Google voice..
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?
__________________
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
 
Posts: 1,048 | Thanked: 979 times | Joined on Mar 2008 @ SF Bay Area
#62
Originally Posted by epage View Post
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?
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.
__________________
qgvdial: Google Voice client. All downloads
qgvtp: Phone integration for the n900 that dials out and sends texts using qgvdial.
mosquitto: message broker that implements the MQ Telemetry Transport protocol version 3.
qgvnotify: Google voice and contacts notifier for diablo and maemo.

If you want to thank me, click the Thanks button.
If you'd like to thank my applications, vote to move them to extras.
 
epage's Avatar
Posts: 1,684 | Thanked: 1,562 times | Joined on Jun 2008 @ Austin, TX
#63
Originally Posted by uvatbc View Post
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.
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
__________________
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
 
Posts: 1,048 | Thanked: 979 times | Joined on Mar 2008 @ SF Bay Area
#64
Originally Posted by epage View Post
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
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.
__________________
qgvdial: Google Voice client. All downloads
qgvtp: Phone integration for the n900 that dials out and sends texts using qgvdial.
mosquitto: message broker that implements the MQ Telemetry Transport protocol version 3.
qgvnotify: Google voice and contacts notifier for diablo and maemo.

If you want to thank me, click the Thanks button.
If you'd like to thank my applications, vote to move them to extras.
 
epage's Avatar
Posts: 1,684 | Thanked: 1,562 times | Joined on Jun 2008 @ Austin, TX
#65
Originally Posted by uvatbc View Post
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.
I wish the telepathy folks and others very familiar with maintaining dbus interfaces would write some best practices. The best I remember is some blogpost on p.g.o.
__________________
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
 

The Following User Says Thank You to epage For This Useful Post:
fcrochik's Avatar
Posts: 722 | Thanked: 1,223 times | Joined on Apr 2010 @ USA
#66
I assume this dbus api discussion is becuase of the new dbus api created to allow, among others, mycontacts to start a gv call using qgvdial. Once I suggested epage and uvatbc this I would like to give my 2ct:

Telepathy is great and the more I work with it the more I like the idea. epage's TOR has given us telepathy support for gv. I remember reading somewhere epage explaining the difference between his two gv implementations and why having a dialer had its benefits in some scenarios. I think the standalone dialer and the "connected" telepathy implementations serve different scenarios and/or wishes.

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.

Another reason why I suggested the api is because the dialer needs to allow the user to select a contact from the phone's contact database and instead of having uvatbc create another contact browser he could just use mycontacts to select the contact.
__________________

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
 

The Following User Says Thank You to fcrochik For This Useful Post:
epage's Avatar
Posts: 1,684 | Thanked: 1,562 times | Joined on Jun 2008 @ Austin, TX
#67
Originally Posted by fcrochik View Post
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..
I've not seen it so I can't say. I would be impressed if there are not demands for additional or more complex features. That is why I hesitate implementing a feature unless I'm wiling to go the whole way with it. Having my day job be to work on a 10 year old software stack w/ a fully-backwards compatible public API (including unpublished internal APIs that might have a chance at being abused publicly) that is used in mission critical military/energy/physics/medical systems might color my perspective a little

Another approach that a non-telepathy api could take (besides being simple) is exposing a lot more GV-specific nobs that are hard to express in Telepathy. I've actually contemplated moving the GV communication out of DC/TOR into a dbus service. The downside to this is it couples the API to the current design of GV, either for features or performance considerations.
__________________
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
 
fcrochik's Avatar
Posts: 722 | Thanked: 1,223 times | Joined on Apr 2010 @ USA
#68
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.
__________________

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
 

The Following User Says Thank You to fcrochik For This Useful Post:
Posts: 1,048 | Thanked: 979 times | Joined on Mar 2008 @ SF Bay Area
#69
Originally Posted by fcrochik View Post
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.
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?
__________________
qgvdial: Google Voice client. All downloads
qgvtp: Phone integration for the n900 that dials out and sends texts using qgvdial.
mosquitto: message broker that implements the MQ Telemetry Transport protocol version 3.
qgvnotify: Google voice and contacts notifier for diablo and maemo.

If you want to thank me, click the Thanks button.
If you'd like to thank my applications, vote to move them to extras.
 
epage's Avatar
Posts: 1,684 | Thanked: 1,562 times | Joined on Jun 2008 @ Austin, TX
#70
Originally Posted by uvatbc View Post
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?
Something I look forward to is QtMobility is going to have support for pluggable contact engines. This expands the Maemo5 behavior of pulling contacts from eds and telepathy. I imagine it would be easier to write contact engines rather than sync engines but maybe I haven't research sync enough.

Sadly when I looked at the product support Symbian was supported but not Harmattan. I am unsure when n900-like meego devices will have it.
__________________
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
 
Reply


 
Forum Jump


All times are GMT. The time now is 17:28.