Active Topics
-
Firefox with Leste (10)
to Maemo 7 / Leste by teroyk - 3 days, 6 hrs ago - more...
|
2011-03-19
, 02:59
|
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#332
|
Originally Posted by epage
Steal away! But before you think it does more than it actually does:
Yeah, some people had previously looked at this but I didn't see anything come of that. I look forward to stealing this
This feature does not mean that qgvdial is now a fully independent dialer. It only indicates that it's calling back into the browser based GV plugin is possible. You still need gmail open on your desktop.
I'm hoping that the next step in this direction is possible. If it is, it will be *the* killer feature: qgvdial should be able to use the inbuilt web browser plugins capability to initiate a callback into the gmail interface and completely bypass all sip/skype/phone requirements.
Naturally, this would work only on desktop machines at the moment.
Later, if I can figure out what the plugin actually does, I can attempt recreating that so that it works even on Maemo and Symbian.
Aah the possibilities are endless!
Now all I need is a time turner and a ton of money so I can quit my day job and hack at it. If wishes were horses, then this beggar would ride!
Originally Posted by epage
I start the download of all inbox items and stop the moment I get something that is older than the newest entry that I have.
I don't think I've gotten your new build yet so I'll hold off on comments till then except the following
I've not dug through too much of your code but it looks like you always download all inbox items. The contacts it looks like you do partial updates on. From scraps I've seen it looks like a downside to your contacts approach though is handling of the separate login requirements of regular google. That sound correct?
Regarding contacts: yes, I get the contacts from the regular Google contacts - because of a few reasons:
1. the regular Google contacts API actually is an API unlike GV.
2. I can ask the server for all updates since a given time. Much better than what I'm doing for the Inbox items. gcontacts api also provides what has been deleted
3. All this means much less processing on my side, implying less CPU time, implying more battery life.
__________________
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.
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.
|
|
2011-03-19
, 03:06
|
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#333
|
@epage: Just noticed your edit and wanted to note that the plugin is not just Windows, it works on Linux as well and from what I hear, on Mac as well.
__________________
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.
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.
 |
|
2011-03-19
, 03:20
|
|
Posts: 1,684 |
Thanked: 1,562 times |
Joined on Jun 2008
@ Austin, TX
|
#334
|
Originally Posted by uvatbc
1. At one point I grabbed the source of the GV chrome extension (can't remember how) and it made a request for a json resource with all sorts of information. In this same request I grab the _rnr, callback numbers, and contacts. More is available but I just ignore it for now. This seems like it should be amply efficient though maybe my contact list isn't big enough.
I start the download of all inbox items and stop the moment I get something that is older than the newest entry that I have.
Regarding contacts: yes, I get the contacts from the regular Google contacts - because of a few reasons:
1. the regular Google contacts API actually is an API unlike GV.
2. I can ask the server for all updates since a given time. Much better than what I'm doing for the Inbox items. gcontacts api also provides what has been deleted
3. All this means much less processing on my side, implying less CPU time, implying more battery life.
2. Ok, I missed the the auto-killing during pagination processing. I don't bother with pagination, just get the most X recent items. Since I'm not a heavy phone user this provides months of data. So far no one has complained. In a local branch I've even made it so if you are only looking at mised calls or voicemails and cause a refresh, it will only refresh those.
__________________
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
|
|
2011-03-19
, 04:43
|
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#335
|
Originally Posted by epage
I started off like that as well - but what forced me off that path was the fact that I have over 1000 contacts, 600 of which have phone numbers. Parsing this took so much time and CPU at every refresh, that I had to find a better way.
1. At one point I grabbed the source of the GV chrome extension (can't remember how) and it made a request for a json resource with all sorts of information. In this same request I grab the _rnr, callback numbers, and contacts. More is available but I just ignore it for now. This seems like it should be amply efficient though maybe my contact list isn't big enough.
Also: As a result of moving to the gcontacts api and using mosquitto, I can get near instantaneous updates - just like Android.
This is particularly impressive because whenever I update contacts from gmail, those changes are propagated to qgvdial within 20 seconds or less. I don't sacrifice battery life for this either.
When I eventually get time, I plan to use these features to create the contacts sync utility.
__________________
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.
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.
|
|
2011-03-19
, 11:14
|
|
Posts: 1,684 |
Thanked: 1,562 times |
Joined on Jun 2008
@ Austin, TX
|
#336
|
Originally Posted by uvatbc
This sounds somewhat parallel to a discussion I saw on meego-dev about programmers being the worst for defining performance requirements for contact applications because usually they have no where near the number of contacts as other people (like those in sales).
I started off like that as well - but what forced me off that path was the fact that I have over 1000 contacts, 600 of which have phone numbers. Parsing this took so much time and CPU at every refresh, that I had to find a better way.
Also: As a result of moving to the gcontacts api and using mosquitto, I can get near instantaneous updates - just like Android.
This is particularly impressive because whenever I update contacts from gmail, those changes are propagated to qgvdial within 20 seconds or less. I don't sacrifice battery life for this either.
Originally Posted by uvatbc
Doesn't help on Maemo 5 and not sure if it is used yet in Meego, but a project I find interesting is libfolks. Rather than syncing contacts, you gather them from multiple sources and merge them. I'm one who doesn't trust what a sync application might or might not due to my contacts on the server.
When I eventually get time, I plan to use these features to create the contacts sync utility.
__________________
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
|
|
2011-03-26
, 08:45
|
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#337
|
New build!
Some UI improvements based on epage's observations.
Also: First attempt at a satisfying an interesting feature request: Show only those dial out methods that are enabled.
Specific use case was for SIP accounts - user has more than one SIP account and enables / disables SIP accounts based on the country he/she is in.
Hopefully you'll now see only those that are enabled. Not just that, when you _do_ enable your SIP account (or disable), those changes should be recognized by qgvdial and the list updated automatically.
Some UI improvements based on epage's observations.
Also: First attempt at a satisfying an interesting feature request: Show only those dial out methods that are enabled.
Specific use case was for SIP accounts - user has more than one SIP account and enables / disables SIP accounts based on the country he/she is in.
Hopefully you'll now see only those that are enabled. Not just that, when you _do_ enable your SIP account (or disable), those changes should be recognized by qgvdial and the list updated automatically.
__________________
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.
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.
|
|
2011-03-31
, 03:46
|
|
Posts: 356 |
Thanked: 123 times |
Joined on Dec 2008
|
#338
|
I just updated to the most recent version in extras-devel. Whenever I restart the program (when my phone restarts, or I quit the program using cntrl-q) the dial out method resets. This should stay the same even when I restart the program.
|
|
2011-04-02
, 06:42
|
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#339
|
New build!
I was experimenting a bit with the voicemail functionality in the devel build. I toyed with the idea of making qgvdial dependent on libqtm-11 but then gave up on that once I realized that libqtm-11 is not going to hit extras proper.
The voice mail UI has changed a bit. There is no longer a separate window for the voicemail, it's all integrated into the QML.
This was in part to keep it working well in the Symbian version.
Specifically, did you enable/disable SIP/skype accounts or stuff like that?
I was experimenting a bit with the voicemail functionality in the devel build. I toyed with the idea of making qgvdial dependent on libqtm-11 but then gave up on that once I realized that libqtm-11 is not going to hit extras proper.
The voice mail UI has changed a bit. There is no longer a separate window for the voicemail, it's all integrated into the QML.
This was in part to keep it working well in the Symbian version.
Originally Posted by xur17
I tried this out several times, but I couldn't reproduce it. Can you tell me more about this bug?
I just updated to the most recent version in extras-devel. Whenever I restart the program (when my phone restarts, or I quit the program using cntrl-q) the dial out method resets. This should stay the same even when I restart the program.
Specifically, did you enable/disable SIP/skype accounts or stuff like that?
__________________
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.
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.
|
|
2011-04-02
, 23:00
|
|
Posts: 61 |
Thanked: 27 times |
Joined on Jul 2010
|
#340
|
Originally Posted by uvatbc
I too have noticed this. Actually for the past 3-4 revisions.
New build!
I tried this out several times, but I couldn't reproduce it. Can you tell me more about this bug?Originally Posted by xur17 View Post
I just updated to the most recent version in extras-devel. Whenever I restart the program (when my phone restarts, or I quit the program using cntrl-q) the dial out method resets. This should stay the same even when I restart the program.
Specifically, did you enable/disable SIP/skype accounts or stuff like that?
It seems quite repeatable to me. When QVDIAL is restarted (either via reboot or Ctrl-Q), the CALL-TYPE is reset to "Dial back: Google Talk".
memo: You added several string substitutions to make the CALL-TYPE more readable. But you left the "sofiasip" (and possibly "spirit").
I don't think I've gotten your new build yet so I'll hold off on comments till then except the following
EDIT: That's right, this still requires the use of a special windows-only plugin, right?
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
Last edited by epage; 2011-03-19 at 02:48.