I'm feeling really stupid. I have an installation of Trinity on Squeeze
where the user uses Icedove for email. For some reason, it wants to
open PDF files in GIMP. I see the same thing in other Gnome
applications like Evolution.
I've gone to Icedove preferences and tried to change the application
type and clicking on other . . . does not produce a dialog box to select
an application (like KPDF or acroread). I installed kgtk-config-icedove
but that did not help. I even installed Nautilus and tried setting the
application association there. That at least presented KPDF as an
option in Evolution but not in Icedove. I installed gconf-editor but
that does not seem to address application associations.
Short of finding which defaults.list file it is looking at and manually
editing it or manually setting it in mimetypes.rdf, how does one set
this in a Trinity only environment (in that Gnome desktop is not
installed)? Thanks - John
Guys,
Just a quick sanity check. I have the Arch Linux package for tqtinterface
building, but I saw a few headers that were not found during cmake:
Checked out revision 1217590.
==> SVN checkout done or server timeout
==> Starting cmake...
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- checking for 'Qt'
-- Performing Test HAVE_PATCHED_QT3
-- Performing Test HAVE_PATCHED_QT3 - Success
-- found patched Qt, version 3.3.8
-- Looking for qinputcontext.h
-- Looking for qinputcontext.h - not found
-- Looking for qinputcontextfactory.h
-- Looking for qinputcontextfactory.h - not found
-- Configuring done
<snip>
Are the 'not found' headers OK, or do I have a build problem on my end? Sorry
if this is a stupid question, but I'm still feeling my way through the initial
build :)
--
David C. Rankin, J.D.,P.E.
Guys, Gals,
After pulling my hair out getting pykde to build correctly with the old kde3
removed, I patched built and installed qt3-3.3.8c, reinstalled kde3, built pykde
and I'm now moving forward through the trinity svn build order.
Can I do this?
My plan is to rebuild pykde as I get the trinity packages built and put in
place. Any gotchas?
--
David C. Rankin, J.D.,P.E.
On 01/26/2011 03:08 PM, Neil Youngman wrote:
> Different Wikis have different markups. The Trinity Wiki is FOSWiki. See
> http://foswiki.org/System/TextFormattingRules for FOSWiki's markup.
>
> I have corrected the headers to use FOSWiki markup.
>
> HTH
>
> Neil Youngman
>
That's the ticket! Thanks Neil. I'll go grab the foswiki reference.
--
David C. Rankin, J.D.,P.E.
As requested by some people (Xu_R AKA The Old Man) an odt and pdf of
the reasoning behind my kmenu setup.
I would appreciate any input to improve the setup.
Thanks
Kate
Guys,
How do I get pykde to use the right dcopobject.h from trinity svn in order
to successfully build it after removing my prior kde3 install? I ask because I
read that you MUST remove prior KDE3 installs before building trinity. I did
that. I also patch qt3 for 3.3.8c and I have it installed. However when you
run 'python configure.py' it grabs the kde4 install information:
gcc version 4.5.2
concatenating files
KDE base directory is /usr
KDE include directory is /usr/include
KDE lib directory is /usr/lib
lib directory is lib
<snip>
and then fails during make because it can't find the right dcopobject.h:
<snip>
Creating top level Makefile...
Creating pykdeconfig.py...
make[1]: Entering directory
`/home/david/arch/pkg/trinity-notes/pykde3/src/PyKDE-3.16.7/dcop'
g++ -c -Wno-deprecated-declarations -pipe -fPIC -march=x86-64 -mtune=generic
-O2 -pipe -Wall -W -D_REENTRANT -DNDEBUG -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -I.
-I../extra/kde353 -I/usr/include -I/usr/include/python2.7
-I/opt/qt/mkspecs/default -I/opt/qt/include -I/usr/X11R6/include -o
sipdcoppart0.o sipdcoppart0.cpp
sip/dcop/dcopobject.sip:30:24: fatal error: dcopobject.h: No such file or
directory
compilation terminated.
make[1]: *** [sipdcoppart0.o] Error 1
make[1]: Leaving directory
`/home/david/arch/pkg/trinity-notes/pykde3/src/PyKDE-3.16.7/dcop'
make: *** [all] Error 2
I know I am missing something basic concerning setting up my build
environment. I can't just add something like:
-I /home/david/arch/pkg/trinity/kdelibs/dcop
to the dcop Makefile because it then fails to find tqobject.h and so on. So I
need a push in the right direction. Anybody have a reference, a link, or some
notes squirreled away that would help cure my ignorance here?
Any help would be greatly appreciated. I'm more than willing to RTFM, if I
just know which FM to read :-)
--
David C. Rankin, J.D.,P.E.
I've been thinking about submitting a few bug reports and feature requests. I am posting the list here, in case someone would like to comment...
1) Kinfocenter launches empty. None of the components is available. I found a workaround: right-click the KDE task bar and add the "Settings" applet. All the functions are there.
2) I request installation of kdepim-kde3 and Adept Manager tells me it is going to BREAK something. Should I proceed? Is that safe?
3) My old configuration of Yakuake is no longer usable because many keyboard shortcuts don't work anymore. For example, Shift+Ctrl+c, Shift+Ctrl+v, Ctrl+/, Alt+c/Alt+s inside Vim etc.
(Hmm... the Vim shortcuts don't work on Konsole either. I will have to investigate that further.)
4) KDE 3 has had a bug with key shortcuts for years: in the config app, Regional & Accessibility, Keyboard Shortcuts, we can change some of the global shortcuts. I like this: copy with Ctrl+c and Ctrl+Ins, paste with Ctrl+v and Shift+Ins, Undo with Ctrl+z and Redo with Ctrl+y. The problem is Ctrl+Ins, Shift+Ins, and Ctrl+y do not work everywhere. In Kmail, for example, Ctrl+y does not work. Ctrl+c and Ctrl+v did not use to work, they do now. But Ctrl+Ins and Shift+Ins still don't work in a few places, especially small dialogues.
5) This has bothered me for ages: in Konqueror, I REALLY, REALLY wish I could highlight files, COPY them (say, Ctrl+c) and PASTE them into another Konqueror window or panel (Ctrl+v perhaps?). I used to do that a lot in Windows Explorer. I migrated to Linux in 2006 and I still miss that feature...
6) I also love how I can press Ctrl+(NumPad +) to "adjust" the width of all file manager columns. Try doing that in a Windows machine. It's great! Can we have that in Konqueror too? Pleeeease?...
7) I may be the only one in the world who has or notices this problem:
I use a netbook that I can carry around, but I use an external keyboard when I'm at home. The netbook has a US International keyboard, the keyboard at home is Brazilian, ABNT2. Whenever I plug/unplug the keyboard and switch layouts, I lose my Repeat Delay/Rate configuration, so the keyboard feels a little bit slow. So I have to open Kcontrol, readjust the delay and click OK. The number never seems to have changed, but the keyboard definitely feels different. Redoing the config fixes it, but it's annoying. I also have to do that ritual every time I boot/reboot/log out. I wish KDE would keep those settings.
--
Luciano ES
>>
Hi all. This is a post to clear up any issues that people might be
confused with.
We've all agreed to this, so this is now here for reference.
So, let me start of by saying:
TRINITY IS NOT KDE3 (anymore).
KDE3 IS DEAD.
And let me go a bit further with that.
We are currently in an alpha stage of porting Trinity to cmake.
There is currently the following in usable or finished states:
- tqtinterface
- arts
- kdelibs
- kdebase
- kdedevelop
The 3.5.12 tarballs DO NOT have them. I repeat, DO NOT have cmake scripts.
You will need to download them from http://thel.ro/ and insert them
into the build directory.
We are also in a pre-alpha stage of porting Trinity to Qt4.
Before I go any further, let me say:
WE ARE NOT PORTING APPLICATIONS ONE BY ONE TO QT4 (as may have been
interpreted before).
What we are doing is porting the apps to tqt (a relatively easy thing
to do), and then letting tQT handle the Qt version specifics.
tQt for Qt4 has been progressing along for some time, although it is
COMPLETELY FAR from stable.
If you'd like to see a screenshot from 3.5.13, Tim provides one here:
http://tinypic.com/view.php?pic=1586qmp&s=7
I assure you, we are not making another KDE4. We'll leave that junk to
the KDE4 developers.
Thank you for taking the time to read this.
The Trinity Developers
I've managed to get Trinity running nicely on Slackware 13.1. To be more
precise it is a linux live derivative of slackware (similar to slax).
Everything runs nicely and i have only one question.
On the root account i get the error 'cannot start kstartupconfig` after
logging on and just before the desktop loads. I can click ok and move to the
desktop no problem. I imagine it is a permissions thing with the home/root
directory but nothing i've tried fixes the error. For testing i boot from an
iso. Before creating the iso i have chowned the folder and also tried chmod
755. Can anyone point me in the right direction to remedy this. I am sure it
is a simple permission problem but it eludes me so far.
Jay
On Monday 24 January 2011 14:01:10 Katheryne Draven wrote:
> With regard to "mytools", it smacks too much as a homage to MS, with
> its "My this" and "My that", but in the end its not my decision. Its
> clearly something Trinity as a whole must make. I do urge against the
> use of MS terminology. I understand the belief that if its familiar,
> it will make the use more comfortable. That, however, has not been my
> eXPerience :). Users who leave windows for Linux cringe when they see
> references to it. They're finally free of their master, why would
> they wish to build a shrine to it? The use of MS terms, also
> reinforces the belief that Linux is just a second rate Windos
> wannabe.
>
> OH BLAST! Where did this soapbox come from??!!
>
>
> Kate
I and I suspect many others will agree with you !
However sensible naming should improve clarity.
--
Best Regards:
Baron.