

Chat & Messenging
Qt Components
I was waiting with the answer until I figure out several issues related to my latest changes in the codebase. Still, I'd love to say that the next release will be in 2 weeks, but I can't promise, since there are some regressions introduced by the new functionality, that I have to work on for a while. Anyway, I may do some pre-release in some time, you'll be informed by the automatic updates module :)
- Aug 20 2009
Yep, that's because there are no Maemo packages yet. It's compilable and runnable on Diablo, but packages aren't ready yet. I'm afraid that I wouldn't be able to deliver packages even for the next release, since I'm running out of time and probably won't have time to do sufficient testing on Maemo. Actually it's another guy that used to be maintaining qTwitter for Maemo but it seems that he's very busy at the moment. I could probably do something about it in the future, i.e. after my holiday. Please keep an eye on this page, I'll surely update it once I have something Maemo-related.
- Jul 05 2009
From what I see, you probably have previously compiled and installed qtwitter without OAuth support, and now trying to compile it with OAuth enabled. Prior to it, please uninstall the previous installation (sudo make uninstall in qtwitter's source directory should do the job). Then make distclean, and start again with qmake and make.
The problem is that while linking, linker refers to libtwitterapi installed in system (without OAuth support) and not the one just compiled. I repeated this scenarion in Jaunty and got the same errors, so I guess that's it. - Jul 01 2009
The problem is that while linking, linker refers to libtwitterapi installed in system (without OAuth support) and not the one just compiled. I repeated this scenarion in Jaunty and got the same errors, so I guess that's it. - Jul 01 2009
Are you sure you're compiling the most fresh code from github? It works for me on several distros, including Debian. If you like, you can report a bug http://ayoy.lighthouseapp.com/projects/27230-qtwitter/tickets?q=all, but please provide info on your host and qtwitter's version that you are building etc.
- Jun 30 2009
Well, afaik, LGPL is only the application's license. Debs are created under GPL, and rpms as well, I guess - they can't put any license restrictions on packages. Even if it was LGPL, everything would seem ok with repackaging. Anyway, I was packaging it, so go on with Alien as it's no problem for me :P after all, it's more or less like converting tar.gz to zip :)
- Jun 11 2009
Hey,
both ideas are just great! And I'm actually working on adding support for other social and workgroup services (identi.ca, presentlyapp, yammer..). This is taking a bit long now, because I needed to reorganize the code. Anyway, this stage is already done and I'm on my way to create handlers for more services.
Support for multiple accounts will also be added in the next release.
Thanks!
Dominik - Mar 27 2009
both ideas are just great! And I'm actually working on adding support for other social and workgroup services (identi.ca, presentlyapp, yammer..). This is taking a bit long now, because I needed to reorganize the code. Anyway, this stage is already done and I'm on my way to create handlers for more services.
Support for multiple accounts will also be added in the next release.
Thanks!
Dominik - Mar 27 2009
Hi!
What distro and DE/WM are you using? The browser setting should support at least Gnome/KDE and Opera/Firefox/Konqueror. I didn't check it with Iceweasel, but I guess it should behave the same way as Firefox. I'm talking about context menu links only (the user's homepage and Twitter page, and main Twitter and TwitPic pages). Other links, such as those displayed in statuses shall be handled automatically by Qt, and the browser setting has no influence on it. In this case, you should have set the default browser for your DE/WM for Qt to open those links.
Complicated, but I hope I made myself at least a bit clear :)
If you still receive the error, don't hesitate to post a bug report to http://ayoy.lighthouseapp.com/projects/27230-qtwitter/tickets?q=all .
Thanks for your feedback! - Mar 14 2009
What distro and DE/WM are you using? The browser setting should support at least Gnome/KDE and Opera/Firefox/Konqueror. I didn't check it with Iceweasel, but I guess it should behave the same way as Firefox. I'm talking about context menu links only (the user's homepage and Twitter page, and main Twitter and TwitPic pages). Other links, such as those displayed in statuses shall be handled automatically by Qt, and the browser setting has no influence on it. In this case, you should have set the default browser for your DE/WM for Qt to open those links.
Complicated, but I hope I made myself at least a bit clear :)
If you still receive the error, don't hesitate to post a bug report to http://ayoy.lighthouseapp.com/projects/27230-qtwitter/tickets?q=all .
Thanks for your feedback! - Mar 14 2009