Active Topics
-
Firefox with Leste (10)
to Maemo 7 / Leste by teroyk - 3 days, 3 hrs ago - more...
|
2011-03-10
, 23:41
|
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#322
|
I'm on fire today: new build!
-> QML now starts off with a width,height that matches the platform.
-> If the mq server is invalid, don't crash.
-> Timer delay in deleting the NwCfg object.
I'm promoting this one to testing. Vote for it!
Links: Extras-testing armel and i386.
-> QML now starts off with a width,height that matches the platform.
-> If the mq server is invalid, don't crash.
-> Timer delay in deleting the NwCfg object.
I'm promoting this one to testing. Vote for it!
Links: Extras-testing armel and i386.
__________________
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-11
, 03:28
|
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#323
|
I think I've finally figured out the reason why qgvdial was chewing up the CPU. It was my mis-interpretation of the mosquitto api.
I have fixed it and a new build is in the repositories.
Enjoy the battery life not eaten by qgvdial
I have fixed it and a new build is in the repositories.
Enjoy the battery life not eaten by qgvdial
__________________
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-11
, 06:27
|
|
Posts: 61 |
Thanked: 27 times |
Joined on Jul 2010
|
#324
|
I have another suggestion....
I have always valued new features above mere cosmetics; so I'm quite embarrassed to make yet another request that is totally cosmetic.
Your new layout for the INBOX-list has fixed my problems in navigating through the inbox. [many thanks!!!]
But I also started thinking about making it easier to visually scan through the inbox list as you are scrolling it. This is a mock up of what I came up with:
I was trying to make the icons totally different from each other; so you could recognize them even while scrolling.
But I think I over did it (and made it look a bit goofy).
I looked through your code to see how difficult this would be.
The following is what I came up with [warning: I do not know how to program QML, so this is only a guess]:
memo: The icons came from "Clker.com - the royalty free clip art", and some playing in GIMP.
The icons are now 190X100 (as the orignals were 92X100).
Let me know if you want the icons.
I have always valued new features above mere cosmetics; so I'm quite embarrassed to make yet another request that is totally cosmetic.
Your new layout for the INBOX-list has fixed my problems in navigating through the inbox. [many thanks!!!]
But I also started thinking about making it easier to visually scan through the inbox list as you are scrolling it. This is a mock up of what I came up with:
I was trying to make the icons totally different from each other; so you could recognize them even while scrolling.
But I think I over did it (and made it look a bit goofy).
I looked through your code to see how difficult this would be.
The following is what I came up with [warning: I do not know how to program QML, so this is only a guess]:
Code:
// ---- InboxModel.cpp (export shortTime and shortDate to InboxList.qml)
int daysTo = dt.daysTo (QDateTime::currentDateTime ());
shortTime = dt.toString ("hh:mm");
switch (daysTo) {
case 0: shortDate = "today"; break;
case 1: shortDate = "yesterday"; break;
case 2:
case 3:
case 4:
case 5:
case 6: shortDate = dt.toString ("dddd"); break;
default: shortDate = dt.toString ("dd-MMM");
}
Code:
// ---- InboxList.qml [line 262...]
Text { // display call date and time:
id: textName
anchors {
verticalCenter: parent.verticalCenter
right: parent.right; rightMargin: 5
}
text: shortDate + "\n" + shortTime; color: "white"
font.pointSize: (Code.btnFontPoint () / 12)
}
row { // display call-type icon and caller's name:
anchors {
verticalCenter: parent.verticalCenter
left: parent.left; leftMargin: 5
}
// leave some room for date & time. [50 is a complete guess]
width: parent.width - 50
spacing: 2
Image {
source: type + ".png"
fillMode: Image.PreserveAspectFit
}
Text {
text: name; color: "gold"
font.pointSize: (Code.btnFontPoint () / 8)
}
}
The icons are now 190X100 (as the orignals were 92X100).
Let me know if you want the icons.
| The Following User Says Thank You to kbyork For This Useful Post: | ||
|
|
2011-03-11
, 07:47
|
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#325
|
@kbyork: qgvdial is always in need of UI improvements because I'm aesthetically challenged.
Thanks for the visual, it seems reasonable and quite doable.
However, this one will take some time and I'd like to get back to it after getting through with the other things in my queue - at least one of which is another one of your suggestions.
Please add this one there so that I can keep track.
I will need the icons once I start working on this.
For the moment, I'm trying to enter a competition and not completely suck.
Thanks for the visual, it seems reasonable and quite doable.
However, this one will take some time and I'd like to get back to it after getting through with the other things in my queue - at least one of which is another one of your suggestions.
Please add this one there so that I can keep track.
I will need the icons once I start working on this.
For the moment, I'm trying to enter a competition and not completely suck.
__________________
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-17
, 00:30
|
|
Posts: 1,684 |
Thanked: 1,562 times |
Joined on Jun 2008
@ Austin, TX
|
#326
|
I thought I would give qgvdial a try for once.
The entry fields aren't too obvious. I thought they were just labels at first. Once I realized they weren't I wasnt too sure of my clicks were working and I could start editing. Part of that is that the sizing is unclear.
It might reduce clutter on the main screen if the settings were all on one screen. From that screen is probably where I would put the debug link.
There should either be in-app help or a link about setting up mosquitto in the mosquitto settings screen.
Dismiss window, status, and app name should probably all be on the same line in landscape. In portrait status would then flow onto another line.
How do I actually view the inbox or make calls within qgvdial? It just sits at the screen I've been talking about with no obvious button to go to an inbox or dialpad or anything.
EDIT: All on 0.2.422 (just pulled from extras-testing) on n900
The entry fields aren't too obvious. I thought they were just labels at first. Once I realized they weren't I wasnt too sure of my clicks were working and I could start editing. Part of that is that the sizing is unclear.
It might reduce clutter on the main screen if the settings were all on one screen. From that screen is probably where I would put the debug link.
There should either be in-app help or a link about setting up mosquitto in the mosquitto settings screen.
Dismiss window, status, and app name should probably all be on the same line in landscape. In portrait status would then flow onto another line.
How do I actually view the inbox or make calls within qgvdial? It just sits at the screen I've been talking about with no obvious button to go to an inbox or dialpad or anything.
EDIT: All on 0.2.422 (just pulled from extras-testing) on n900
__________________
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
| The Following User Says Thank You to epage For This Useful Post: | ||
|
|
2011-03-17
, 03:59
|
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#327
|
Originally Posted by epage
Yay! Finally!
I thought I would give qgvdial a try for once.
Originally Posted by epage
Quite a few users seem to be confused about what to do once qgvdial starts the first time. I've tried to make it self explanatory, and I think I need to set up something like tooltips for the first run.
The entry fields aren't too obvious. I thought they were just labels at first. Once I realized they weren't I wasnt too sure of my clicks were working and I could start editing. Part of that is that the sizing is unclear.
Maybe the About page needs to link to some form of helpful help.
Originally Posted by epage
I'm not sure I follow you here... Most of the settings *are* on one screen.
It might reduce clutter on the main screen if the settings were all on one screen. From that screen is probably where I would put the debug link.
The debug link is on that screen.
It's the same screen as the login/logout button and mosquitto and all that.
Originally Posted by epage
That helpful help link is beginning to sound like a good idea now.
There should either be in-app help or a link about setting up mosquitto in the mosquitto settings screen.
Originally Posted by epage
I think the "back" button needs to be clarified: It's the top bar that says "qgvdial". I've made a fix in devel that changes the text from qgvdial to the equivalent of "back". Hopefully that should clear up things.
How do I actually view the inbox or make calls within qgvdial? It just sits at the screen I've been talking about with no obvious button to go to an inbox or dialpad or anything.
Btw: New build!
I've mostly been working on the Symbian side of things and most of the changes in this build are to ensure that none of the Symbian changes crap out on Maemo5 (or Linux or Windows).
There are obviously some fixes that actually help - such as the "back" fix mentioned above. Plus there's the usual slew of bugfixes.
Not a lot has changed functionality wise. Just made some things look better and more cross-platform.
__________________
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-17
, 11:11
|
|
Posts: 1,684 |
Thanked: 1,562 times |
Joined on Jun 2008
@ Austin, TX
|
#328
|
Originally Posted by uvatbc
Changing the visual look of the text fields to actually look like text fields is all you need to do, no documentation required.
Quite a few users seem to be confused about what to do once qgvdial starts the first time. I've tried to make it self explanatory, and I think I need to set up something like tooltips for the first run.
Maybe the About page needs to link to some form of helpful help.
Originally Posted by uvatbc
Now that I realize that entire screen was "settings". Closing the UI is not a setting. There should be a persistent button for that (and for just minimizing qgvdial) much like some of the other fullscreen maemo apps.
I'm not sure I follow you here... Most of the settings *are* on one screen.
The debug link is on that screen.
It's the same screen as the login/logout button and mosquitto and all that.
Putting the proxy settings and mosquitto settings all on that main settings page would probably be good.
All of the buttons could use some spacing on all screens, especially "logout" so one doesn't accidentally click that while doing something else.
Refresh and about aren't really related to settings. I would suggest finding a different way to represent them. One would be refresh buttons like I recently did in Dialcentral. Also, refresh I take refreshes everything? Usually I find I only want to refresh missed calls or voicemail or texts and waiting for a full refresh seems wasteful.
Wow, a contact has a "close" button and the "back" button. Oddly enough "close" goes back one level" while "back" goes to the main screen.
On the dialpad when selecting a call method, it isn't clear that some are call-in and some are call-out, I had to think about that for a bit "oh, this is downloaded from gv while that is from my telepathy".
When I call a contact, what call method is used? What I configured on the dialpad? That then sounds like a settings that belongs right below the login buttons or it should be available wherever one may call.
On "inbox" the category touch selector isn't too obvious at being a touch selector.
On voicemails I didn't notice it was downloading and got two play dialogs. And for some reason it wasn't playing for me. Any reason you don't show the voicemail text? Odd that I only show text while you only allow playback
For sms, you only seem to be showing the last message the person sent rather than the whole conversation.
This is probably from the mixture of qwidget with qml but closing of the text writing window should automatically go back to the main window rather than using the task switcher. Is there not a way for one to be a subwindow of the other?
Originally Posted by uvatbc
For the most part, with some good UI you won't except for how do I setup a mosquitto server since that is unrelated to direct use of the application.
That helpful help link is beginning to sound like a good idea now.
Originally Posted by uvatbc
I tried clicking that. The click target is unclear and kind of small. Only knowing that yes that is what I need to click did I actually click it. Also knowing that on the first screen that I need to go "back" is confusing as I saw nothing to go "back" to. Maybe popping up the main screen and then sliding to the login screen would help with that.
I think the "back" button needs to be clarified: It's the top bar that says "qgvdial". I've made a fix in devel that changes the text from qgvdial to the equivalent of "back". Hopefully that should clear up things.
__________________
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
| The Following User Says Thank You to epage For This Useful Post: | ||
|
|
2011-03-18
, 03:33
|
|
Posts: 61 |
Thanked: 27 times |
Joined on Jul 2010
|
#329
|
(comment from the cheap seats: )
Since you can make GVDial calls from the phone's CONTACTS or PHONE screen; then the only-time that I use GVDial's UI is to play my voicemail.
While I can't disagree with epage's assessment of the UI;
it is the calling features and functionality that I value ...nay... that I need!
the cosmetics are like icing, and should be done last. (....including my own cosmetics requests...)
Since you can make GVDial calls from the phone's CONTACTS or PHONE screen; then the only-time that I use GVDial's UI is to play my voicemail.
While I can't disagree with epage's assessment of the UI;
it is the calling features and functionality that I value ...nay... that I need!
the cosmetics are like icing, and should be done last. (....including my own cosmetics requests...)
| The Following User Says Thank You to kbyork For This Useful Post: | ||
|
|
2011-03-19
, 01:20
|
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#330
|
New build! And a surprising new feature:
qgvdial is now able to dial back into the Gmail GV interface.
What this means is that if you select the "Google Talk" entry in the list of registered phones and make a call, then the callback will be in the Gmail interface.
Why surprising? Because I was surprised at how quickly I managed to make it work.
But you're right. This needs to be fixed.
There's a bunch of other UI improvements as well.
Right now its in devel, but it should soon be in testing.
qgvdial is now able to dial back into the Gmail GV interface.
What this means is that if you select the "Google Talk" entry in the list of registered phones and make a call, then the callback will be in the Gmail interface.
Why surprising? Because I was surprised at how quickly I managed to make it work.
Originally Posted by epage
Done.
Changing the visual look of the text fields to actually look like text fields is all you need to do, no documentation required.
Originally Posted by epage
The persistent button is the top bar.
Now that I realize that entire screen was "settings". Closing the UI is not a setting. There should be a persistent button for that (and for just minimizing qgvdial) much like some of the other fullscreen maemo apps.
Originally Posted by epage
Button sizes increased.
Putting the proxy settings and mosquitto settings all on that main settings page would probably be good.
All of the buttons could use some spacing on all screens, especially "logout" so one doesn't accidentally click that while doing something else.
Originally Posted by epage
True... I'll have to look into this...
Refresh and about aren't really related to settings. I would suggest finding a different way to represent them. One would be refresh buttons like I recently did in Dialcentral.
Originally Posted by epage
This could require a UI re-design. Also, the inbox and contacts update are optimized so that only the data since the last modified time is picked up and no more... Unless of course you long-press Refresh - in that case, it does a no-hold-barred full refresh.
Also, refresh I take refreshes everything? Usually I find I only want to refresh missed calls or voicemail or texts and waiting for a full refresh seems wasteful.
Originally Posted by epage
True. The top bar is obvious, but the individual entries need to be updated.
Wow, a contact has a "close" button and the "back" button. Oddly enough "close" goes back one level" while "back" goes to the main screen.
On the dialpad when selecting a call method, it isn't clear that some are call-in and some are call-out, I had to think about that for a bit "oh, this is downloaded from gv while that is from my telepathy".
Originally Posted by epage
I've followed the approximate scheme of keeping the dial method on the dialpad - just like the default phone app.
When I call a contact, what call method is used? What I configured on the dialpad? That then sounds like a settings that belongs right below the login buttons or it should be available wherever one may call.
Originally Posted by epage
True. Needs to be fixed. Will do.
On "inbox" the category touch selector isn't too obvious at being a touch selector.
Originally Posted by epage
Heh. That's partly because I've almost never had a voicemail that's been transcribed meaningfully. Blame it on the accent.
On voicemails I didn't notice it was downloading and got two play dialogs. And for some reason it wasn't playing for me. Any reason you don't show the voicemail text? Odd that I only show text while you only allow playback
But you're right. This needs to be fixed.
Originally Posted by epage
I need to look into this.
For sms, you only seem to be showing the last message the person sent rather than the whole conversation.
Originally Posted by epage
This is a remnant of the non-QML days. I'll get to this soon.
This is probably from the mixture of qwidget with qml but closing of the text writing window should automatically go back to the main window rather than using the task switcher. Is there not a way for one to be a subwindow of the other?
Originally Posted by epage
I've made some changes to the text fields so that they look distinctly different from labels.
For the most part, with some good UI you won't except for how do I setup a mosquitto server since that is unrelated to direct use of the application.
I tried clicking that. The click target is unclear and kind of small. Only knowing that yes that is what I need to click did I actually click it. Also knowing that on the first screen that I need to go "back" is confusing as I saw nothing to go "back" to. Maybe popping up the main screen and then sliding to the login screen would help with that.
There's a bunch of other UI improvements as well.
Right now its in devel, but it should soon be in testing.
__________________
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.
| The Following User Says Thank You to uvatbc For This Useful Post: | ||
I've been facing intermittent high CPU load. This build is one of those where I try to figure out if it fixes the problem because I haven't quite understood why qgvdial would ever eat that much CPU - I don't have ANY tight loops.
With this build I haven't faced a CPU spike because of qgvdial for about 2 days of straight running and monitoring.
Also: For the (unlikely) Symbian users who frequent this thread, be prepared for qgvdial to hit the Ovi store soon.
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.