26 Jan
2011
26 Jan
'11
1:50 a.m.
Excellent. That makes things clear. I was wondering where to find the cmake
files, i ended up getting things to work from the tarballs on slack current.
Love yer work.
J
On Tue, Jan 25, 2011 at 9:42 PM, Robert Xu <robxu9(a)gmail.com> wrote:
On Tue, Jan 25, 2011 at 16:38, Thierry de Coulon
<tdecoulon(a)gmail.com>
wrote:
You have to run a separate script to launch Trinity apps? I have never had
to.
--
later, Robert Xu
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-users-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive:
http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On 1/25/11, Robert Xu <robxu9(a)gmail.com>
wrote:
TQt - the brains behind Trinity, using Qt3 and (soon) Qt4 to render
our Desktop Environment.
If any app wanted to, they could start using TQt and then not worry
about Qt3 -> Qt4 -> Qt5 changes.
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.
(...)
First of all I welcome this. the KDE team dropped KDE3, we don't need
this legacy. What I hope is that we will be able to install Trinity as
an alternate UI, and distribution could propose Trinity as a UI
choice.
Having to run a separate script to launch Trinity apps is a bit
uncomfortable.