tde-devels

devels@trinitydesktop.org

9 participants
3775 discussions

by Darrell Anderson

I submitted a small patch to resolve one of the biggest irritants on my hit list, bug report 392 (http://bugs.pearsoncomputing.net/show_bug.cgi?id=392), Desktop Device Icon Placement. The patch is small and restores a snippet of code that was deleted long ago. I found the solution by persistent trial-and-error and not any elegant C++ sleuthing. Thus, I ask for a signoff review to inspect the restored code. I am using the patch here but I'd like to push to GIT. Thanks! Darrell

13 years, 1 month

A note of encouragement!

by Darrell Anderson

I am typing this message from a Trinity session built from GIT. Trinity is noticeably snappier than my KDE3 setup. Even Firefox responds faster, both in page rendering speed and interface response. Except for the startup speed Firefox almost feels native. I feel as though I have new hardware, the difference is that noticeable. After we eliminate some build issues and resolve some usability bugs I think R14 will be nice indeed. Very nice. Much faster. Thanks everybody! Darrell

13 years, 1 month

Build split package for sip4-tqt & provide Python2 and Python3 support

by David C. Rankin

Darrel, All, After examining the way Arch handled the building and installation of sip and python2-sip, I believe the same can be applied to the sip4-tqt package to build and provide both python2 and python3 support. I have setup the arch build of sip4-tqt to do this. It can probably be done the exact same for all distros. The build proceeds as follows: pkgbase=tde-sip4-tqt pkgname=('tde-sip' "${pkgbase}") build() { CFLAGS="${CFLAGS} -I/usr/include/tqt -I${TDEDIR}/include -I${QTDIR}/include" cd ${srcdir} # the directory holding sip4-tqt source dir ## copy source for Python3 build cp -r ${pkgbase#*-} sipPy3 ## Python3 version cd ${srcdir}/sipPy3 python configure.py CFLAGS="${CFLAGS}" LFLAGS="${LDFLAGS}" make ## Python2 version cd ${srcdir}/${pkgbase#*-} python2 configure.py CFLAGS="${CFLAGS}" LFLAGS="${LDFLAGS}" make } ## package Python3 version as 'tde-sip' package_tde-sip() { pkgdesc="The TDE SIP C/C++ Bindings Generator for Python3 - Trinity upstream GIT version" depends=('python') replaces=('python-sip' 'sip') provides=('python-sip' 'sip') cd "${srcdir}/sipPy3" make DESTDIR="${pkgdir}" install install -Dm644 LICENSE "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE" } ## package Python2 version as 'tde-sip4-tqt' package_tde-sip4-tqt() { pkgdesc="The TDE SIP C/C++ Bindings Generator for Python2 - Trinity upstream GIT version" depends=('sip' 'python2') replaces=('python2-sip') provides=('python2-sip') cd "${srcdir}/${pkgbase#*-}" make DESTDIR="${pkgdir}" install install -Dm644 LICENSE "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE" # Provided by tde-sip rm "${pkgdir}/usr/bin/sip" } The resulting packages avoid the /usr/bin/sip conflict by removing the version produced by python2 in the package stage resulting in packages that install nicely together. The file list provided is: 08:57 nirvana:~/tde/bld/tde-sip4-tqt> pacman -Qpl tde-sip4-tqt-3513_tqt-2-x86_64.pkg.tar.xz tde-sip4-tqt /usr/ tde-sip4-tqt /usr/bin/ tde-sip4-tqt /usr/include/ tde-sip4-tqt /usr/include/python2.7/ tde-sip4-tqt /usr/include/python2.7/sip.h tde-sip4-tqt /usr/lib/ tde-sip4-tqt /usr/lib/python2.7/ tde-sip4-tqt /usr/lib/python2.7/site-packages/ tde-sip4-tqt /usr/lib/python2.7/site-packages/sip.so tde-sip4-tqt /usr/lib/python2.7/site-packages/sipconfig.py tde-sip4-tqt /usr/lib/python2.7/site-packages/sipdistutils.py tde-sip4-tqt /usr/share/ tde-sip4-tqt /usr/share/licenses/ tde-sip4-tqt /usr/share/licenses/tde-sip4-tqt/ tde-sip4-tqt /usr/share/licenses/tde-sip4-tqt/LICENSE 08:58 nirvana:~/tde/bld/tde-sip4-tqt> pacman -Qpl tde-sip-3513_tqt-2-x86_64.pkg.tar.xz tde-sip /usr/ tde-sip /usr/bin/ tde-sip /usr/bin/sip tde-sip /usr/include/ tde-sip /usr/include/python3.2mu/ tde-sip /usr/include/python3.2mu/sip.h tde-sip /usr/lib/ tde-sip /usr/lib/python3.2/ tde-sip /usr/lib/python3.2/site-packages/ tde-sip /usr/lib/python3.2/site-packages/sip.so tde-sip /usr/lib/python3.2/site-packages/sipconfig.py tde-sip /usr/lib/python3.2/site-packages/sipdistutils.py tde-sip /usr/share/ tde-sip /usr/share/licenses/ tde-sip /usr/share/licenses/tde-sip/ tde-sip /usr/share/licenses/tde-sip/LICENSE May be worth looking at for other distros as well. -- David C. Rankin, J.D.,P.E.

13 years, 1 month

python configure.py - howto set include paths? can't find tqt.h ...

by David C. Rankin

All, I am working to build sip4-tqt and I'm running into problems telling python configure.py where to find the include files. I patched sipgen/sip.h to #include <tqt/tqt.h> which allow it to find tqt.h, but then it failed to find the next include: /usr/include/tqt/tqt.h:54:23: fatal error: ntqglobal.h: No such file or directory which is in /opt/tqt3/include/ntqglobal.h So with a python configure, how do I set the include search path to include /opt/tqt3/include:/opt/whatever/else/I/need? python2 configure.py --help tells me how to flag where the completed files go, but not where to help configure.py look for them. What's the trick? -- David C. Rankin, J.D.,P.E.

13 years, 1 month

sip4-tqt, sip, python2-sip (the sips) what is needed - Arch splits sip between python2 and python3 (worth doing?)

by David C. Rankin

Darrell, All, Investigating the default sip packages provided by arch I find: sip (python3) and python2-sip (python2). What arch has done is build /usr/bin/sip with python3, but still provides all the packages we provide in sip4-tqt in the python2-sip package. I wonder if this might not be a better setup. Specifically here is the current arch package setup: 22:44 valkyrie:~/Documents/bld/tde-sip4-tqt> pacman -Ql python2-sip python2-sip /usr/ python2-sip /usr/bin/ python2-sip /usr/include/ python2-sip /usr/include/python2.7/ python2-sip /usr/include/python2.7/sip.h python2-sip /usr/lib/ python2-sip /usr/lib/python2.7/ python2-sip /usr/lib/python2.7/site-packages/ python2-sip /usr/lib/python2.7/site-packages/sip.so python2-sip /usr/lib/python2.7/site-packages/sipconfig.py python2-sip /usr/lib/python2.7/site-packages/sipdistutils.py python2-sip /usr/share/ python2-sip /usr/share/licenses/ python2-sip /usr/share/licenses/python2-sip/ python2-sip /usr/share/licenses/python2-sip/LICENSE 22:45 valkyrie:~/Documents/bld/tde-sip4-tqt> pacman -Ql sip sip /usr/ sip /usr/bin/ sip /usr/bin/sip sip /usr/include/ sip /usr/include/python3.2mu/ sip /usr/include/python3.2mu/sip.h sip /usr/lib/ sip /usr/lib/python3.2/ sip /usr/lib/python3.2/site-packages/ sip /usr/lib/python3.2/site-packages/sip.so sip /usr/lib/python3.2/site-packages/sipconfig.py sip /usr/lib/python3.2/site-packages/sipdistutils.py sip /usr/share/ sip /usr/share/licenses/ sip /usr/share/licenses/sip/ sip /usr/share/licenses/sip/LICENSE The sip4-tqt provides essentially what the arch python2-sip package provides EXCEPT /usr/bin/sip which is provided by the python3 based sip package. If the python3 sip is backwards compatible with the sip4-tqt needs, then couldn't I simply replace the python2-sip package on arch with the sip2-tqt package without the binary and keep both the original Arch sip package and sip4-tqt installed and use the existing sip binary? The sip4-tqt package I just built includes the following: 22:45 valkyrie:~/Documents/bld/tde-sip4-tqt> pacman -Qpl tde-sip4-tqt-3513_tqt-1-x86_64.pkg.tar.xz tde-sip4-tqt /usr/ tde-sip4-tqt /usr/bin/ tde-sip4-tqt /usr/bin/sip tde-sip4-tqt /usr/include/ tde-sip4-tqt /usr/include/python2.7/ tde-sip4-tqt /usr/include/python2.7/sip.h tde-sip4-tqt /usr/lib/ tde-sip4-tqt /usr/lib/python2.7/ tde-sip4-tqt /usr/lib/python2.7/site-packages/ tde-sip4-tqt /usr/lib/python2.7/site-packages/sip.so tde-sip4-tqt /usr/lib/python2.7/site-packages/sipconfig.py tde-sip4-tqt /usr/lib/python2.7/site-packages/sipdistutils.py That would be a neat way to have sip cover both python2 as well as python3. What say the experts? -- David C. Rankin, J.D.,P.E.

13 years, 1 month

TDE Qt4 theme engine [TDE spring fundraiser]

by Timothy Pearson

It's time for our TDE spring fundraiser! The TDE project relies on your financial support to continue development of this reliable and easy-to-use desktop environment. As my way of saying thank you I have developed a new theme engine for Qt4 that allows you to use your TDE styles and file dialogs in new Qt4 applications, as well as interface methods required to easily convert common Qt4 objects to TQt3 objects and vice versa. If we can raise the $2,000 required to keep the TDE project running for the rest of the year by April 30, 2012, I will release the source code for this new theme engine under the GPL and also integrate it into the next TDE release. Once this engine and the conversion methods are part of TDE, the foundation will have been laid for work to begin on a Webkit-based replacement for the aging KHTML engine. Donations can be securely made to the project at this address: http://trinitydesktop.org/donate.php I will also update that page from time to time with progress made towards the $2,000 goal. TECHNICAL SPECIFICATIONS Library requirements: TQt3, Qt4, and TDE core Lines of C++ source code: 4207 (theme engine and Qt4 object translator) License: GPL Functional quality: ALPHA Screenshots of the theme engine in action are attached, showing common TDE styles in use with Qt4 applications. If you want to see this engine released and think the TDE project is worth a few dollars, please donate to help keep the TDE project going! Timothy Pearson Trinity Desktop Project

13 years, 1 month

Multiple pushes with GIT

by Darrell Anderson

I would appreciate anybody who knows sharing how to perform a multiple pushes with GIT. I have some low level patches I want to push. Patching my local repository is straightforward with find and sed. The trick thereafter is diiscovering which modules were changed, creating a commit message for each individual module, and then pushing each individual module. My understanding is that each module must be pushed individually. Also each module push requires typing a password. There are 117 modules (packages) in TDE. Doing this manually I foresee myself missing or overlooking a few modules. My only solution thus far is to write a script that can recurse through my local repository, but even that seems like a lot of work because of all the error checking that should occur. Is there a simpler way? Thanks! Darrell

13 years, 1 month

March Meeting

by Robert Xu

Forgive me for not bringing this up earlier. We invite everyone to attend the March Meeting on IRC (irc.freenode.net, #trinity-desktop-meeting). It will take place on 25 March 2012, at 1200 EST (that's 1600 for my friends in London, and 1100 for Central Time). If you cannot make it, or you are busy, please let me know ASAP so that I can change the date or time. You may also leave topics to be discussed with any opinions or such. And this is also a friendly reminder that Etherpad still exists (etherpad.trinitydesktop.org). Thanks, Robert Xu

13 years, 1 month

Updating bugzilla

by Darrell Anderson

I would like us to improve our bug report triage efforts. If you filed bug reports related to build issues, please consider updating them as follows: * Any package that fails to build from source (FTBFS), change to Blocker P1. Ensure the acronym FTBFS is in the description. * Any package that builds without failure but requires work-arounds or nominal patching, change to Critical P1. * Any package that builds without failure but builds incompletely, such as missing components, or causes other problems, change to Major P1. Thanks! Darrell

13 years, 1 month

gtk-qt-engine KDE -> TDE issues + patch to push

by David C. Rankin

Tim, Darrell, applications-gtk-qt-engine had KDE -> TDE issues. See: http://www.3111skyline.com/dl/dt/trinity/ss/gtk-styles-kde-fix.jpg The patch file K2T.patch corrects this issue. I just need someone to push it. Let me know if we need a bug report, otherwise, you can just add it to the GIT code. -- David C. Rankin, J.D.,P.E.

13 years, 1 month

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels