One thing I have noticed about Konqueror 3.5.13 is embedded viewing is the default for just about everything.
I prefer to use the external app rather than the KPart embedded viewers.
When I migrate a KDE 3.5.10 profile to TDE none of those settings remain. I'm thrown back to the embedded viewers.
Is there an easy or quick way to reverse this default without having to manually reset them with each mimetype of app that is opened?
Darrell
I already asked but no-one replied to me.
Is there any way in which I could tell automake (./configure) for
which version of TQt or Qt should it look, or where to find them?
In my system it keeps detecting TQt4 and thus is searching for Qt4.
Both of them aren't present on my system, since I have clean install,
only with Qt3 and other trinity deps.
It is crucial to me, since without solving this problem I cannot
continue on building trinity components, nor I can continue on
creating PKGBUILDs for Arch.
My distro is Archlinux and I'm building from 3.5.13 tarballs.
I need some help with the autoconf packages.
When building it finds qt3 and tqtinterface but it keeps failing on linking
QString and QWidget. So I think it is missing some library. What is weird
is that all the libraries are in /opt/trinity/lib and /usr/lib.
ldconfig.so.conf has those paths.
What library are these in.
Thanks
Hi everyone,
we are currently in the process of standardizing a new "Keywords" key in
the freedesktop.org desktop entry spec[0].
Apparently KDE used to use a slightly different variant (using commas
instead of semi-colons as separators) before it was prefixed with X-KDE.
It was agreed that the differences are too minor to matter in practice,
but as the Trinity desktop still uses the non-prefixed variant, it
seemed like a good idea to make you aware of the spec change anyway :)
Regards,
Florian
[0] http://lists.freedesktop.org/archives/xdg/2011-December/012173.html
I'm hoping this is not a bug but a case of my poor memory.
In Konqueror, one of my user accounts shows a search bar to the right of the location bar.:
http://humanreadable.nfshost.com/trinity/konq-user1.png
Another user does not show the search bar:
http://humanreadable.nfshost.com/trinity/konq-user2.png
Both users show an rsync plugin button from the kdeaddons package.
I have no idea how to enable or disable either the search bar or the rsync button. I'm not commenting on the merits of the tools, just the inability to enable (show) or disable (not show).
I thought perhaps the solution was in the Configure Extensions menu option, but nothing happens when I change the check boxes.
Neither option appears in the Configure Toolbars menu option.
I hope I'm missing something obvious!
Darrell
a little bug that is present in the tarballs (and what I've seen in
the git too). During compilation of
kopete/protocols/msn/CMakeFiles/kopete_msn_shared-shared.dir/msnswitchboardsocket.cpp,
the kopeteemoticon.h is not found. I checked and
kopeteemoticon.{h,cpp} are present in the kopetelib subdirectoory
"private" not in main dir. In attachement patch that fixes incluson of
that file in msnswitchboardsocket.cpp
kdenetwork fails on kopete compilation. I compile it with every
feature available. See attachment for log and more info.
Seems that kopeteemoticon.h is missing.
This article surfaced on our IRC channel through <NachPlus>
><NachPlus>I don't know if this is of interest to anyone, but an article came out today which praises the KDE 3.5 user interface: http://insanecoding.blogspot.com/2011/12/progression-and-regression-of-desk…
I read whole thing and this is the guy that seems to understand why we
are keeping trinity alive. But I didn\t like the last paragraph. It
seems that he blames re-branding of trinity. I think we should explain
clearly why this was done either in the about page or in the FAQ. I
already added question about this to the FAQ Draft in etherpad, but
honestly, I didn't really know how to ask this kind of thing, nor
explain this... This kind of criticism isn't really constructive, and
we should have all the tools we need to fight against any kind of
un-constructive, and unreasonable blaming either in the faq or in the
about page IMO.
