All,
I have a number of kde3 themes (and emerald themes) that I have created over
the years that I'm happy to give to trinity if there is any interest in
collecting them. Here is an example of a BlackGold (dark) theme that I have
updated in Trinity:
[165k]
http://www.3111skyline.com/dl/dt/trinity/ss/dcrTrinityBlackGold.jpg
The theme uses keramic style and a dark color scheme:
http://www.3111skyline.com/dl/dt/trinity/cfg/color-schemes/dcrTrinityBlackG…
(you may have to adjust the gold depending on monitor brightness :)
The .kth files are a bit large for me to host at home. If you want to try the
ktheme, (with font & icon settings, etc...) it is available here:
http://www.3111skyline.com/dl/dt/trinity/cfg/ktheme/dcrBlackGoldTrinity.kth
Let me know if there is any interest in collecting these to either package or
make available on the wiki. I probably have a dozen kthemes in varying
darknesses and probably 100+ emerald themes. A sample of the emerald themes are
available here: http://drankinatty.deviantart.com/gallery/?offset=0
I guess I could just upload the .kth files to deviantart as well..., but if
you want to broaden the selection in Trinity -- they are all GPL.
--
David C. Rankin, J.D.,P.E.
hello all,
I'm a fresh trinity user and so far, I like it :)
so I decided to resurrect some of my favourite kde 3.x programs which are not
in the trinity repos and built very simple (checkinstall-) packages from
them.
they can be found here:
http://www.hoernerfranzracing.de/zip/trinity/
maybe someone here can use them, too.
werner
Is there a way to get konqueror to work with a SOCKS proxy?
I do this:
$ ssh -D 12345 user@remote
Iceweasel works fine when I set the proxy to SOCKS localhost:12345.
now I'd like konqeror to use that SOCKS4/5 server on localhost. But whatever I
check on the SOCKS tab, I get an error message. I tried tsocks, but konqueror
still connects directly to the net.
Does anybody have an idea?
Nik
Hi,
I installed LibreOffice, but the desktop integration package
libreoffice3.3-debian-menus_3.3-6_all.deb
does not work properly wit Trinity, e. g. Open a document does not work. Is that a
Trinity problem?
--
Viele Grüße,
Hartmut
Hungerhilfe: http://www.thehungersite.com
Ohne Zensur suchen:
http://suche.amnesty-bergedorf.de/
ökologisch suchen:
http://www.ecosia.de
Das heutige Motto:
Die Dummheit von Regierungen sollte niemals unterschätzt werden.
in a super-user terminal I get this:
# synaptic
Invalid MIT-MAGIC-COOKIE-1 key
(synaptic:19493): Gtk-WARNING **: cannot open display: :1.0
in a user terminal I get this:
$ synaptic
bash: synaptic: command not found
from the debian menu, clicking synaptic does nothing.
--
Paul Cartwright
Begin forwarded message:
*From:* HHa <hha4491(a)web.de>
*Date:* February 21, 2011 13:08:20 EST
*To:* Robert Xu <robxu9(a)gmail.com>
*Subject:* *Re: [trinity-users] LibreOffice*
Hi Robert,
Can you please file a bug report at the Trinity website?
I don't have an account for bugs.
Please keep messages inline with the mailing list.
You must create an account for the bugzilla, then file a bug there.
this morning I noticed my system was rather sluggish. One thing I found
was nepomukserver, and about 5 other processes.. I am running Debian
Squeeze & trinity kde3.5 . I turned off the desktop search function, is
there anything else I can do?
I had those processes running & I use gnome desktop! my other user runs
trinity..
--
Paul Cartwright
Here is a quick forward from the Arch list regarding Trinity binaries for Arch
Linux (svn)
-----------
All,
Kaiting Chen has provided server space for Trinity binaries. Currently I have
the i686 files uploaded and will upload x86_64 shortly (after my kids are done
with toontown....)
The url for the i686 repo is:
http://www.kiwilight.com/~drankinatty/trinity/i686/
(Trinity packages are 2/19/2011 builds)
The x86_64 repo will be the same url with x86_64.
Trinity needs a clean environment currently (no kdemod3). If you have had a
prior kdemod3 install, then delete:
/var/tmp/kdecache-$USER/ksycoca
/var/tmp/kdecache-$USER/ksycocastamp
and move ~/.kde somewhere else.
If you have kde4 installed, then expect akonadi/nepomuk and all the kde4
autostart files in /usr/share/autostart to run (Trinity devs are working on a
way to ignore all the kde4 autostart files)
To install trinity, just add the repo to /etc/pacman.conf:
[trinity]
Server = http://www.kiwilight.com/~drankinatty/trinity/i686/
Then just do 'pacman -Sy trinity-kdewebdev' and it will pull in the complete
Trinity desktop (kdewebdev requires all trinity dependencies)
I recommend installing it in either a clean Arch install, or just create a new
Arch virtualbox VM and install it there. It is a darn good looking desktop.
x86_64 packages by the morning :)
See: https://wiki.archlinux.org/index.php/Trinity for current details :)
--
David C. Rankin, J.D.,P.E.
--
David C. Rankin, J.D.,P.E.
All,
Here are recent build times for Trinity svn on a middle of the road P4 3.2G
box. (nothing special - old Dell GX280 'small form factor'):
10:55 supersff:~/tblds> grep Feb bldlog.txt
Feb 19 01:44:45 building: trinity-qt3
Feb 19 02:06:12 building: trinity-pyqt3
Feb 19 02:17:05 building: trinity-tqtinterface
Feb 19 02:18:16 building: trinity-arts
Feb 19 02:22:02 building: trinity-kdelibs
Feb 19 03:01:01 building: trinity-kdebase
Feb 19 03:36:42 building: trinity-kdevelop
Feb 19 03:51:13 building: trinity-kdewebdev
Feb 19 03:58:21 done!
2:14 beginning to end. For anyone packaging Trinity, the basic 'outline' of
the build script layout I used was (link to full script below):
#!/bin/bash
<snip>
# array of build directories -- in order
declare -a blddirs
blddirs=('trinity-qt3'
'trinity-pyqt3'
'trinity-tqtinterface'
'trinity-arts'
'trinity-kdelibs'
'trinity-kdebase'
'trinity-kdevelop'
'trinity-kdewebdev')
# loop through the blddirs to build each in order
for((i=0;i<${#blddirs[@]};i++)); do
# copy your dev dir to the build dir (I don't build in my original dev dir)
# if working with srpms, you could either install them at this point and
# build with 'rpmbuild -bb specfile' or just 'rpmbuild --rebuild srpm'.
cp -a ${pbbase}/${blddirs[$i]} $bldbase
# if the dir got copied (or spec file exists) -- use it, if not skip it
if [[ -d ${bldbase}/${blddirs[$i]} ]]; then
# start time to screen & log
echo -e "\n$(date '+%b %e %T') building: ${blddirs[$i]}\n" | tee -a ${bldlog}
# change into the build dir
cd ${bldbase}/${blddirs[$i]}
# move any existing packages out to pkgdir (adjust for .rpm or .deb)
echo -e "\n Testing for old packages and moving to ${binsavdir}\n"
if ls *tar.xz &>/dev/null; then
mv -fv *tar.xz ${binsavdir} | tee -a ${bldlog}
fi
# build the new package (adjust for rpbbuild -bb or whatever deb uses)
(makepkg -s)
# install and move new package to $pkgbin dir (adjust as needed)
# if the build failed, issue warning an move on
echo -e "\n Testing for new packages, installing, and moving to ${binpkgdir}\n"
if ls *tar.xz &>/dev/null; then
sudo pacman -U --noconfirm *tar.xz | tee -a ${bldlog}
mv -fv *tar.xz ${binpkgdir} | tee -a ${bldlog}
else
echo "WARNING: Build of '${blddirs[$i]}' produced no package, skipping..."
| tee -a ${bldlog}
fi
else
echo "WARNING: Directory '${bldbase}/${blddirs[$i]}' not found - skipping" |
tee -a ${bldlog}
fi
done
exit 0
The link to the full script is:
http://www.3111skyline.com/dl/dt/trinity/arch/scr/bldtrinsvn-all.sh
It should be able to be easily adapted for rpm based builds or whatever debian
and slackware use. The PKGBUILD scripts that Arch Linux uses with "makepkg" work
the same way SPEC files work with "rpmbuild" on rpm based distros.
--
David C. Rankin, J.D.,P.E.