Hi Trinity developers,
finally I can announce the availability of a patch  to build KWin
standalone. That is without building other parts of kde-workspace. The patch
is on top of KDE/4.10 branch  as of Friday and available in git branch
"kwin/standalone" of my kde-workspace clone .
I hope this patch can help you to provide a tailored version of KWin. Most of
the functionality which is required for this is already part of KWin master
and also used in some KDE projects. E.g. for Plasma Active we use an adjusted
KWin version without window decorations, without KCMs, with a different binary
name and different configuration files. To make it easier to build KWin for
new developers we introduced a build option to disable the Oxygen window
decoration which required to build most parts of kde-workspace. All available
build options are documented in .
For the usage in your project I would suggest the following build options:
* adjust the "KWIN_NAME" variable in CMakeLists.txt
* disable KWIN_BUILD_OXYGEN
* disable KWIN_BUILD_KCMS
* disable KWIN_BUILD_KAPPMENU
* disable KWIN_BUILD_ACTIVITIES
The steps on how to build KWin are probably well known given that it is a
cmake project. If not there is a beginners guide available in .
The patch does not reduce the dependency on kdelibs and kde-runtime. We still
have a dependency on kdelibs and that cannot change in the lifetime of KWin on
Qt 4 due to part of KWin being implemented in kdelibs.
Also KWin has a pretty standard Plasma look'n'feel. But this can be easily
* window decorations can be written in QML since 4.10 - with disabled Oxygen
the default decoration is in fact on QML. Documentation for this is still
missing, but is on my TODO list ;-)
* Alt+Tab window switchers can be written in QML. Documentation for this is
available in  and this feature is e.g. used by Plasma Active to have a
* QML scripts can be loaded - e.g. our "Desktop Change OSD" is written in QML.
It would be easy to replace it with one that does not use Plasma Components.
*What are the next steps?*
Development focus is currently on porting KWin to Qt5. Given the strong usage
of XLib this is more work than for most projects. But I hope that this will
soon be finished. With Qt5 and KDE Frameworks 5 the dependencies will go down
to what is really needed and quite some for KWin important functionality from
kdelibs has been upstreamed into Qt.
Other plans are to use KConfigXT for the complete configuration of KWin. This
is already used (since 4.10) for KWin effects and would allow to easily
integrate our configuration interfaces in your available configuration module.
With KConfigXT the configuration modules basically consist of .ui files and an
xml description of the config values. (Note: the KCMs belonging to KWin do not
support a changed binary name.)
Apart from that I want to have everything which is UI to be done in QML.
This patch is a personal service provided by me and is not officially
supported by KDE. I will not update the patch on a regular basis, though I
intend to update it for each release cycle once a new version has been
branched. This also means that I cannot guarantee that everything works
correctly. If you hit a bug related to this patch let me know, but please
don't open a report on bugs.kde.org.
I hope this patch is helpful for you. If you need improvements you are of
course more than welcome to contribute to KWin :-)
A Merry Christmas to you and a happy and successful new year 2013.
>Developers, please delete and re-download the top-level GIT
>I have temporarily locked out commit access to that top level
>to prevent accidental merges of the old history. All other GIT
>continue to have normal read/write permissions for the TDE
>team, so the impact of this should be minimal.
Supermodule? Delete exactly what directory in the tree?
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,
The deadline has been extended to December 21st. There will be no more
FOSDEM is one of the largest gatherings of Free Software contributors in
the world and happens each February in Brussels (Belgium). One of the
tracks will be the CrossDesktop DevRoom, which will host Desktop-related
We are now inviting proposals for talks about Free/Libre/Open-source
Software on the topics of Desktop development, Desktop applications and
interoperativity amongst Desktop Environments. This is a unique opportunity
to show novel ideas and developments to a wide technical audience.
Topics accepted include, but are not limited to: Enlightenment, Gnome, KDE,
Unity, XFCE, Windows, Mac OS X, general desktop matters, applications that
enhance desktops and web (when related to desktop).
Talks can be very specific, such as developing mobile applications with Qt
Quick; or as general as predictions for the fusion of Desktop and web in 5
years time. Topics that are of interest to the users and developers of all
desktop environments are especially welcome. The FOSDEM 2012 schedule might
give you some inspiration:
Please include the following information when submitting a proposal:
The title of your talk (please be descriptive, as titles will be listed
with around 250 from other projects)
Short abstract of one or two paragraphs
Requested time: from 15 to 45 minutes. Normal duration is 30 minutes.
Longer duration requests must be properly justified.
The deadline for submissions is December 14th 2012. FOSDEM will be held on
the weekend of 2-3 February 2013. Please submit your proposals to
crossdesktop-devroom(a)lists.fosdem.org (subscribtion page for the mailing
list: https://lists.fosdem.org/listinfo/crossdesktop-devroom )
-- The CrossDesktop DevRoom 2013 Organization Team*
Pau Garcia i Quiles
(Due to my workload, I may need 10 days to answer)
Sorry to bother you again today :)
I am trying to build python-tqt from GIT (after I built sip4-tqt and
tqscintilla. Btw, somebody with the required access could edit the
"How to build guide" section 7 "Build order" and move "tqscintilla"
before "python-tqt" since the former is a requirement for the latter).
I have this situation:
1) if I use sip 4.10.5 (the one from sip4-tqt package) the correct sip.h
file is installed in /usr/include/python2.X. Nevertheless configuration
fails as follow:
sip: /home/tde_src/2_build/build/dependencies/python-tqt/sip/qt/qtmod.sip:23: syntax error
at configure.py:927 os.system(string.join(argv)), where this command
/usr/bin/sip" -x TQt_STYLE_WINDOWSXP -x TQt_STYLE_INTERLACE -x TQt_STYLE_WINDOWSXP -x TQt_SIP_PRE_4_7_2 -x VendorID -t WS_X11 -t TQt_3_3_6 -j 10 -c qt -b qt/qt.sbf -I/home/tde_src/2_build/build/dependencies/python-tqt/sip /home/tde_src/2_build/build/dependencies/python-tqt/sip/qt/qtmod.sip
For reference, the failing line in qtmod.sip is:
%Module qt 2
PS: I am no SIP expert at all :(
2) instead if I use sip 4.13.3-2 that comes with debian/testing (and which
should not be used according to the How to Build giude) the configuration
is able to complete correctly (beside a never ending list of deprecated
warnings) but then the building fails since the incorrect
sip.h file (and libraries) is installed
qobject.sip:2199:9: error: ‘pyqt3TQtSignal’ was not declared in this scope
So I wonder how you manage to build python-tqt.
What am I missing?
Have a nice weekend :)
sip4-tqt FTBFS on my computer (debian/testing). I used the most recent GIT sources for both TDE and
The problem is in compiling the sipgen module, when the sip.h file is not found.
>> gcc -c -O2 -g -I/usr/include/tqt -I/usr/include/tqt3 -I/usr/include/qt3 -w -DNDEBUG -I. -o parser.o parser.c
>> /home/tde_src/2_build/build/dependencies/sip4-tqt/sipgen/parser.y:24:17: fatal error: sip.h: No such file or directory
The patch adds the module source folder to the include path when generating the makefiles.
In the GIT repo, there is a file siputils.py.orig in the dependencies/sip4-tqt folder. I guess this is a left over from a previous change and it could be removed.
On a side note, what's the standard procedure followed by the TDE team members for submitting bug
fixes/improvements? Should we post patches to this ML or is there another way? Or should we just commit
that to the GIT repo?
I am taking some time off of TDE to spend more time with family and
friends over the holiday season, and therefore will probably not be
available on the TDE mailing lists for the next couple of weeks or so. In
other words, don't be alarmed if I don't respond to queries; I will be
back on these lists shortly after Christmas! :-)
If a service stops functioning properly during my absence I can still be
reached via Email, though my response time may be somewhat delayed.
Merry Christmas to all, especially the many dedicated contributors that
make this project possible. Here's to a bright and shining future for TDE
in 2013 and beyond!
Trinity Desktop Project
I notice that in the GIT TDE packaging repo for sip4-tqt there are two patches (siputils_debian_changes.diff
and siputils_objdir_module_fix.diff) that are not used during the building process.
I wonder if this is intentional or if they are just old patches not needed or what (since I am new here I don't
much of the TDE history).
I would like to either merge them or remove them before applying the patch for the FTBFS, so to clear up
the tree a little. Does anybody remember anything about these two patches?
If there are no objections or no specific instructions before sunday night, on monday morning I
will proceed to remove the two patches from the packaging repo for debian and ubuntu since they
are not currently used, apply the fix for today's FTBFS and finally update the GIT repos.