I was listening in on the last irc meeting and caught an aftermeeting
mentioning about bad Qt4 performance. I offered an article and a possible
workaround I found recently, in case people are not aware of it, and was
asked to bring it to attention to other developers also, so here goes:
I'm suffering bad graphical performance in Qt4 and PyQt4 applications and
searched for solutions. I found a post on nokia.com  that mentions a
command line switch that might help.
In short: adding "-graphicssystem raster" to my Qt4 applications' command line
improved performance drastically for me. There's also a method to set it
programmatically, and an environment variable .
Thanks and much regards,
> Yes. TDE will (as of a couple days ago) build completely against tqt3,
> theoretically resolving any remaining Qt3<-->Qt4 conflicts and allowing
> the usage of Qt4 directly in new (or manually ported) TDE code. Since I
> can hear people's confusion now, this ONLY ALLOWS NEWLY-WRITTEN QT4-BASED
> CODE to be compiled and linked into TDE applications--it does NOT
> magically make TDE compile on Qt4, nor will it ever. :-)
tdelibs doesn't build against tqt3:
Unable to find tqt!
Try adding the directory in which the tqt.pc file is located
Which is created by tqtinterface, but not tqt3. Since tqt3 doesn't
build with tqtinterface installed I don't see a correct way to build
People, how do you build it??
Since I'm trying to come up with an idea for new [a little more
modern, and not looking like it was made in 2003 (no offense to
creator intended)] Trinity website I'd like some help. What I need is
a logo, a symbol for Trinity. And one that is not religious (since the
name was understood as a religious one once). The current logo is a
no-no IMO since it's a too big reference to the KDE logo (gears) and
it just kde3.5 logo with a "T" instead of "K". It should be something
simple and easy to remember.
I know I might be demanding too much, but I think it's a good idea to
come up with something together.
attached is a patch (tested in KDE 3 in Kubuntu Hardy, untested
in Trinity) which resolves the problem with non-ASCII filenames
on WebDAV servers. I’ve designed it using the Qt3/KDE3 APIS af‐
ter how it was fixed in KDE 4.
I’m not a C++ developer, and this is a one-shot. Criticism – of
course – welcome. Please Cc me in replies.
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-314
HRB AG Bonn 5168 • USt-ID (VAT): DE122264941
Geschäftsführer: Boris Esser, Elmar Geese
FYI the TDE mirror system is down due to permanent uidaho mirror server
failure and secondary mirror server misconfiguration.
Details here: http://trinity-announce.pearsoncomputing.net/?0::16
I am working to resolve this issue, however given the limited upload
bandwidth of the TDE servers and lack of donations it may be several weeks
before service is 100% restored.
Note that all non-mirrored TDE services, such as the website, mailing
lists, GIT, Wiki, and bugtracker will all continue to function normally.
This failure affects mirrored source tarballs and binary packages ONLY.
Yesterday I downloaded a mirror image of the GIT repository. 3.9 GB. :)
I have been updating and revising my build scripts with many obvious things but I suspect the renaming project will throw a few speed bumps into the build process.
The ehterpad has helped some. Yet is there anything specific or generic we need to know? A list of "gotchas"? Environment variables that have not been renamed? Etc.
I'm getting my local GIT mirror and build scripts ready for when GIT goes public.
My build scripts extract the version number from tdelibs/tdecore/tdeversion.h. I notice in GIT the TDE_VERSION_STRING define does not match the number of levels. That is, the variable is assigned a value of R14.0 rather than R14.0.0. The variable should be the latter to remain consistent. :)
Slowly, ever so slowly, I'm trying to learn C++. I have this Big Fat Book on my desk and almost every day I read, tinker, and study code.
While trying to compile koffice I ran into these fatal errors:
../../.libs/libkexidb.so: undefined reference to `KexiDB::Parser::~Parser()'
../../.libs/libkexidb.so: undefined reference to `KexiDB::Parser::statement() const'
../../.libs/libkexidb.so: undefined reference to `KexiDB::Parser::parse(QString const&)'
../../.libs/libkexidb.so: undefined reference to `tname(int)'
../../.libs/libkexidb.so: undefined reference to `KexiDB::Parser::Parser(KexiDB::Connection*)'
../../.libs/libkexidb.so: undefined reference to `KexiDB::Parser::query()'
If the g++ error lists a line in a *.cpp file, then usually the "undefined reference to" error means a missing header file that declares the namespace or function.
In this particular error, g++ listed a static library. From what I've read, this means something is awry in the linking process and not in the code itself. Am I on the right track?
If not then please set me straight. :)
If yes, then how do I fix the error? I presume something in the Makefiles? Does the error provide me clues as to where I need to fix the problem?
Trying to learn! Thanks!
Oddball request, but I need a way to crash Trinity. :)
I created bug report 769 (http://bugs.pearsoncomputing.net/show_bug.cgi?id=769). Basically, on one particular computer I am able to get Ark to crash consistently.
Yesterday I started tinkering with building my packages with separate debug packages rather than building the debugging symbols into one package. I figure outside of the devs and packagers most end-users are not interested in that support. :(
Today on that same computer I installed new packages for kdelibs, kdebase, and kdeutils: six packages instead of three.
Now I can't get Ark to crash.
1. I don't pretend to understand the nuances of debugging symbols, but by splitting the debug symbols into a separate package, could I have resolved the bug? Does that make sense?
2. I need a way to crash something in Trinity so I can test my split packages. I have browsed through the bugzilla and could not find anything that was repeatable here. Would someone please suggest a way to test the Dr. Konqi crash handler so I can generate a backtrace? My request is not related to point 1 above --- I just want to test whether my new package scheme is working and I need a way to verify I can generate a backtrace in Trinity. Perhaps there is a built-in easter egg or something that can do just that?