Guys,
I don't know if this is worth looking into from a TDE standpoint or if it is
still relevant, but HAL and udev stopped the boot process on my Arch box today.
Calvin had the issue that I believe he solved by removing an offending udev
rule[1]. That raised the question to me whether there is some standardization
that HAL will require across distros in order to support TDE or if there is some
part of udev that is needed to support HAL?
Arch no longer provides HAL as a standard package. I believe what triggered
the boot fail today was the loss of the 'udev-compat' package (unconfirmed). I'm
still digging into this, but if HAL will be required for TDE, then should we
look into either insuring that a generic HAL version that is compatible with
upstream udev is available to the project?
I don't know how HAL + udev affect TDE or what the long term thoughts are on
either, but I thought I would raise the issues to those smarter than I am in
case there is a looming issue coming down the road.
What say the experts? Is there any issue with HAL + udev on TDE, or is it just
a matter of the individual distro TDE builders to sort out? What worries me is
Arch no longer packages HAL and the version we have in the user supported
repository (done by 'l0ner' -- thank you!) is hal 0.5.14-7 with a *900K patch*
file. If this is where all the distros are ultimately going, we may be better
served by deciding how to handle it now rather than waiting until we run into
build problems later...
Footnote [1]: (which we are still trying to determine exactly what he removed :)
--
David C. Rankin, J.D.,P.E.
> Yes. TDE will (as of a couple days ago) build completely against tqt3,
> theoretically resolving any remaining Qt3<-->Qt4 conflicts and allowing
> the usage of Qt4 directly in new (or manually ported) TDE code. Since I
> can hear people's confusion now, this ONLY ALLOWS NEWLY-WRITTEN QT4-BASED
> CODE to be compiled and linked into TDE applications--it does NOT
> magically make TDE compile on Qt4, nor will it ever. :-)
>
tdelibs doesn't build against tqt3:
Unable to find tqt!
Try adding the directory in which the tqt.pc file is located
Which is created by tqtinterface, but not tqt3. Since tqt3 doesn't
build with tqtinterface installed I don't see a correct way to build
tdelibs.
People, how do you build it??
Update git last night. Autobuild of tdeadmin now fails to find valid qt
version. I have /usr/lib/qt3-3.4 built from last nights update 14th Feb
2012. (Sorry i am not familiar with git jargon). Most other packages
compile.
CFLAGS=$CPUOPT \
CXXFLAGS=$CPUOPT \
./configure \
--prefix=${PREFIX} \
--sysconfdir=${SYSCONFDIR} \
--libdir=${LIBDIR} \
--mandir=${MANDIR} \
--with-qt-dir=${QTDIR} \
--with-qt-includes=${QTDIR}/include \
--with-qt-libraries=${QTDIR}/lib \
--enable-closure
checking for Qt... configure: error: Qt (>= Qt 3.3 and < 4.0) (headers and
libraries) not found. Please check your installation!
I'm busy updating the TDE handbook files. Right now I'm working on the user guides. I'm progressing nicely. Revising text, submitting patches and new images to the bugzilla, repairing web links, etc. Eventually I'll post the user guides for reviews.
I'm writing notes to explain the processes used. Eventually I'll post that information too, either at the wiki or directly in a handbook help file.
As a technical writer, for many years I have grimaced every time I read the expressions "left mouse button," "right mouse button," "click," and "right-click." I frown when I read the word "click" rather than "select."
I'm not anal about language. I'm not a purist. I embrace the fact that languages and usage evolve. Yet I strive for technical correctness because communicating ideas is challenging. Skilled communicators say what they mean and mean what they say. :)
Those mouse related terms bother me from a technical correctness perspective. Why?
Because the terms are technically incorrect for people who use a mouse configured for left-handed use. That is, with the mouse button roles swapped. I should know --- I have used my mouse that way for almost two decades. I have a pretty good laugh every time people try to use a computer desktop I have configured. Swapping the buttons of the mouse confuses people like crazy because they never pay attention to the fact that my mouse is on the left side of my keyboard. :)
I have wondered through the years how such lazy street language terms translate into other languages.
The challenge most people counter is what terms to use as replacements?
The best I have conceived is "primary" and "secondary" buttons. Yet I realize some people might find those terms confusing too.
Should we talk about people who use three button mice? In the days before scroll wheels such mice existed --- I have one in my junk box. :) How about five button mice? Seven? When does "left" and "right" become meaningless? Should those terms be used at all?
I realize conventional usage often prevails but that does not mean those terms are technically correct. :)
I'd like to hear some other thoughts and opinions about the subject.
Darrell
Is there a stable tag for 3.5.13 in Git or somewhere else which I can
build without problems? I can't build trinity for about year! I want
to continue application development but these endless build issues
hold me stopped. There were once git branch somelike named v3.5.13,
but it weren't building smoothly anyway. Now 'git branch' command
shows nothing.
A hypothetical poll for users here....
If TDE were to close down, which desktop would you use instead? You would
be allowed to abandon Linux entirely in this scenario. ;-)
Please state why you have not already switched; i.e. what item are missing
or suboptimal in the other environment.
I am curious as to why TDE still exists and need some concrete examples to
fall back on to counter detractors.
Thanks!
Tim
Can we keep negativity to a minimum and find bugs to fix? Thanks.
One KDE developer/user's attitude does not represent the KDE community
as a whole (however influential).
Likewise, one TDE dev/user's attitude doesn't represent the Trinity
community as a whole.
So please, can we get along?
*(This is why I try not to participate in threads that could possibly
turn negative :|)
tl;dr: shut up, let feuds die, get along in peace. don't judge a book
by its cover.
--
later daze. :: Robert Xu :: protocol.by/rxu
Finally, tdesdk is completely buildable with cmake. Let me know if I missed
something.
PS Do not forget to use latest qt3 version, otherwise "kompare" will fail.
--
Serghei.