
Video Players by DavidEdmundson 12 comments

System Tools (NOT OS or ROMS) by apachelogger 32 comments
b) Yes, generally when you do that all applications should load Qt 4.7 rather than the system one (that is: all apps that are not statically linked or have an rpath, I think rpath takes higher importance).
c) You do not want to do this globally since it can hurt stability (if/where) Qt 4.7 is incompatible with 4.6 (e.g. apps that are linked against QtMultimedia would still load that from 4.6 since 4.7 doesnt have it anymore and in the end you would have an application that overall runs on 4.7 but som parts are 4.7 due to QtMultimedia -> that can cause serious trouble). - Sep 08 2010

System Tools (NOT OS or ROMS) by apachelogger 32 comments

System Tools (NOT OS or ROMS) by apachelogger 32 comments
Say you have a Qt 4.7 installation in /opt/qt47 and your regular Qt 4.6 in /usr. Then you export LD_LIBRARY_PATH to include /opt/qt47/lib and hence override the standard search path /usr/lib, then every dynamically linked Qt application started with that setup will use Qt 4.7 and the option will have effect.
So it is more a question of runtime library loading rather than what an application was built against. - Sep 07 2010

System Tools (NOT OS or ROMS) by apachelogger 32 comments
You will need to install to the KDE search path (usually /usr), otherwise the desktop file will not be found and hence not show up anywhere. - Sep 07 2010

System Tools (NOT OS or ROMS) by apachelogger 32 comments

System Tools (NOT OS or ROMS) by apachelogger 32 comments

System Tools (NOT OS or ROMS) by apachelogger 32 comments
On a netbook for example the plasma-netbook application launcher ought to perform super fast with OpenGL.
As far as I know there is no way to check what backend is in use.
I do not think Qt will use a fallback though, if it breaks, it breaks. So as long as you have a recent enough Qt version (which ought to be 4.7 beta2 or above if I am not mistaken) it should be usign OpenGL if that is selected. - Sep 07 2010

System Tools (NOT OS or ROMS) by apachelogger 32 comments
The backend basically is how widgets (i.e. buttons and textfields and icons etc.) are painted. And that how can either be a native toolkit choice, for example on Linux it will default to use the X11 API for that kind of stuff which will then take care of the actual processing. The raster engine is an own implementation of software rendering (which should be the same as X11 except that it is not as it mostly performs better). And OpenGL will, as the name suggests, directy all painting to the GPU.
So, say you use OpenGL then every button, textfield, icon... in a Qt application will be painted via OpenGL in the GPU. GPUs being specifically tweaked for graphics of course will calculate that usually super fast.
How the raster backend works is descirbed here:
http://labs.trolltech.com/blogs/2009/12/18/qt-graphics-and-performance-the-raster-engine
More information on OpenGL here:
http://labs.trolltech.com/blogs/2010/01/06/qt-graphics-and-performance-opengl/
So, while the OpenGL backend is probably the least working one (with Linux graphics drivers not being that much piece of awesome) it ought to be the fastest one if working, since the GPU will almost always out-perform the CPU when it comes to graphics. - Sep 07 2010

Konsole Color Schemes by apachelogger 6 comments
Also, this theme was in a modified version included into Konsole, so I doubt I will change the version published here at all. - May 03 2010

Plasma 4 Extensions by apachelogger 4 comments
I do not find packages of scripting plasmoids very useful, since essentially Plasma implements its own version management and update stuff system, so having it in apt would just duplicate what is already built into plasma anyway. - Feb 17 2010

Utilities by geflei 43 comments

Utilities by geflei 43 comments
Are you planning on getting KAudioCreator back into kdemultimedia, or is it going to stay in extragear?
Just asking because I am working on a Kubuntu package, and our version number depends a lot on where you are heading with KAC :) - Nov 03 2009
I noticed that your 0.2 tarball contains a pretty useless choqok.tar.gz, I assume this happened when trying to create the actual release tarball :). Therefore I add a choqoK frontend to release script used by Amarok and Digikam. This should make releasing a lot easier and a lot saver in terms of unwanted files.
You can find the script at https://code.edge.launchpad.net/~apachelogger/+junk/extragear-release-script
Just execute release_choqok.rb and it will query the necessary information for creating the tarball. It fetches source, translations, changes the version number automagically and generates a tag in KDE SVN (tags/choqok/VERSION), if you don't want the tag, just comment out the createTag() line in the script.
If you have feature requests or bug reports for the script, just drop me a mail :)
I also uploaded 0.2 to the Kubuntu/Ubuntu archive, though it is still pending approval from an archive administrator... should be available for the upcoming Kubuntu release (9.04).
A fellow Kubuntu developer requested identi.ca support and from looking at the source, a bit of abstraction in the backend code should make it easy enough to add services other than Twitter. So if you feel like it, adding identi.ca support would make at least one Kubuntu developer very happy ;)
Thank you for the application. - Jan 02 2009

Karamba & Superkaramba by techbugs 28 comments
I moved it to the karama section in order to reflect this (+avoid confusion since it is not working at all without superkaramba installed). - Oct 21 2008

Fonts by PeTTi 12 comments
Thus either translate or ask someone else to translate.
Thank you very much. - Aug 01 2008

KDE 3.x Splash Screens by Agentvenom00 1 comment

KDE 3.x Splash Screens by Agentvenom00 4 comments

KDE 3.x Splash Screens by Agentvenom00 1 comment

KDE 3.x Splash Screens by vegetto 3 comments

KDE 3.x Splash Screens by rowancompsciguy 1 comment

KDE 3.x Splash Screens by Agentvenom00 3 comments

KDE 3.x Splash Screens by Agentvenom00 1 comment

KDE 3.x Splash Screens by vegetto 1 comment

KDE 3.x Splash Screens by vegetto 1 comment

KDE 3.x Splash Screens by vegetto 1 comment

KDE 3.x Splash Screens by Agentvenom00 6 comments

KDE 3.x Splash Screens by Agentvenom00 1 comment

KDE 3.x Splash Screens by madsheytan 2 comments

Various Stuff by ipero 1 comment

Various KDE 1.-4. Styles by chrissi75 6 comments

AmarokFS by bigceca 3 comments

AmarokFS by bigceca 1 comment

AmarokFS by afterc0ffee 13 comments

AmarokFS by cherusker 7 comments

AmarokFS by RepsaJih 2 comments

AmarokFS by mith88 1 comment

Various Stuff by japper 1 comment

Icon Sub-Sets by CLEARview 1 comment

Icon Sub-Sets by CLEARview 2 comments

Icon Sub-Sets by CLEARview 2 comments

Icon Sub-Sets by CLEARview 1 comment

KDE 3.x Splash Screens by caf4926 3 comments

Icon Sub-Sets by CLEARview 6 comments

KDE 3.x Splash Screens by iwakunrock 4 comments

KDE 3.x Splash Screens by rowancompsciguy 1 comment

Screensavers by baetrtram-01 1 comment

Audio Apps by Sebien 324 comments

Audio Apps by Sebien 324 comments
But, in the meanwhile the Ubuntu archive admins found a new way to make packaging a bit less funny :S
The admin directory is containing GPL as well as LGPL licensed files, both of these licenses enforce the source publisher, in this case that would be you, to ship a complete license text with the source.
Simply put: please add a COPYING.LIB containing the full license text of the GNU LGPL. Without this file the chance to get Kirocker into the next Kubuntu release is exactly: 0%
However I'll release the current version for revuing now, you should release a fixed tarball ASAP, so I just need to change the tarball then, and therefore speed things up a bit. - Jul 29 2007