Patching Qt3 at newer OpenSUSE releases fails. I receive the following
message:
Patch #140 (qt3_3.3.8c.diff):
+ /bin/cat /usr/src/packages/SOURCES/qt3_3.3.8c.diff
+ /usr/bin/patch -s -p2 --fuzz=0
File include/qobject.h is not a regular file -- can't patch
So, Robert, I suggest you to patch it in your repo and then submit it to
KDE:KDE3.
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
Hi all,
I've been going through spec restructuring, but there's been a few
problems on build.o.o lately.
These include spec files that have conditions for dependencies and
such (that would be trinity's spec files)
If these problems continue persist, I'm probably going to have to move
the project to my local OBS server to continue RPM package building,
which can read the conditions for dependencies and as such, will not
been affected by these random errors. But that will mean people may
not be able to access my work for a period of time,
(even the SuSE people are confused, because this would mean everything
jpackage will fail, so...)
--
later, Robert Xu
On Jan 19, 2011, at 23:30, Kristopher Gamrat <pikidalto(a)gmail.com> wrote:
On Wed, Jan 19, 2011 at 11:06 PM, Kristopher Gamrat <pikidalto(a)gmail.com>wrote:
@Robert: gedit that's the GNOME text editor right? I can't say I've used it
(even in GNOME I still used Kwrite), but why not Kedit, Kwrite, or Kate (the
program, not the Borg with the menu mockup)? Kate can load multiple files
into tabs and can have different profiles with different sets of files open,
would really make things quick to switch between the different .desktop
files.
Well, Gedit is like the Kate for GNOME.
Besides, i'm doing work from a GNOME DE atm, so cut me some slack.
(PS KDE Advertising much? Hehe ;P)
--
later, Robert Xu
Attached is the working (for me) mock of a focused kmenu. It still
needs polishing. I'm sure it still missing things or can be focused
further. I would really like input on how to improve the structure as
well as any errors I may have made.
Thanks
Kate
On 1/10/11, Katheryne Draven <borgqueen4(a)gmail.com> wrote:
> Ok I'll make the mock up (just a directory with .desktop etc) in a day or
> two.
>
> Hope truly hope it helps. I would be nice to see years of work put to
> good use. Its based on my observations of people menu search behavior.
> What they intuitively look for.
>
> 24 to 48 hrs...
>
> Thanks
>
> Kate
>
> On 1/10/11, Timothy Pearson <kb9vqf(a)pearsoncomputing.net> wrote:
>> Sure, I'd be interested!
>>
>> Tim
>>
>>> I've been working on a kmenu setup designed to focus the menu sets so
>>> they don't take over the screen when you open it, also to make it
>>> easier to track down the item you want. Is anyone interested in seeing
>>> it? If so I can create a simple mock up.
>>>
>>> Kate
>>>
>>> On 1/9/11, Ilya Chernykh <neptunia(a)mail.ru> wrote:
>>>> Hi! It is not a secret that all major desktop environments have their
>>>> registered desktop categories for .desktop files. Since the KDE
>>>> category
>>>> has
>>>> been hijacked by KDE4, don't you plan to submit request for
>>>> registration
>>>> of
>>>> a
>>>> Trinity category?
>>>>
>>>
>>
>>
>>
>