tde-devels

devels@trinitydesktop.org

3753 discussions

First draft of help handbook FAQ available

by Darrell Anderson

If you are building from GIT, the FAQ will be current. Open the help handbook to read. If you are not building from GIT, you can read the draft here: http://humanreadable.nfshost.com/trinity/patches/faq.html This is a draft. I'm a tad bleary-eyed from the task and I expect mistakes. :-) Please review for currency, technical correctness, grammar, punctuation, clarity, etc., etc. Links to other help handbooks will not work. Links to online sources should all work. Hopefully by the time R14.0.0 is released we figure out how to generate this document using the existing style sheets. The web site then can host a current copy updated directly from the GIT sources. Thanks everybody. :-) Darrell

12 years, 7 months

FAQ: How do I specify the startup folder for Konqueror?

by Darrell Anderson

In the help center FAQ, the following appears: ===================================================== How do I specify the startup folder for Konqueror? Using the right mouse button, click on the Home icon and choose Properties. Under the Application tab you will probably find something like kfmclient openProfile filemanagement; just append file:/whereever/you/want with the folder you would like Konqueror to start in. ===================================================== Does anybody understand this answer? If yes, please provide additional details because I can't figure out how to follow the instructions. Darrell

12 years, 7 months

Should tdevelop generate apps using the new TQt3 binary names?

by David C. Rankin

Tim, Darrell, I thought about giving tdevelop a run through working with the older examples from kdevelop, but ran into questions and a problem. Before spending the time doing this -- should I expect it to work? What about documentation for tdevelop? I found the entry in the help center, but the tdevelop pages are blank. Are the examples or references from the kdevelop docs still workable? (i.e., if you take a kdevelop tutorial and substitute the new binary names should tdevelop still build the examples?) If that is not possible, does that mean there is really no such thing at the 'Qt3' toolkit for development purposes in TDE? What to do with tdevelop's reliance on Qt3 as a toolkit in the IDE? How far back would we have to go in the GIT tree to get to a point where tdevelop would build the examples? My guess is just before the TQT3 binary rename. Would that be a point where we would expect tdevelop IDE to be able to build older example code? Looks like a minefield. Hopefully it is just because I don't fully understand it, but to me, it looks like the ability to have a TQt 'toolkit' in TDE for tdevelop integrated development environment purposes wont work with the current code. Am I thinking about this right? -- David C. Rankin, J.D.,P.E.

12 years, 7 months

No descriptons for two TDE services

by Darrell Anderson

Two services listed in TDE Components->Service Manager have no description: KDED Subversion Module (installed by tdesvn) TDevelop subversion module (installed by tdevelop) If one of you developer types would provide descriptions I'll merge them quickly into the sources. Thank you! Darrell

12 years, 7 months

Rename KDED -> TDED

by Darrell Anderson

Tim, What is involved to rename KDED to TDED? I'm willing to explore and perform the grunt work and testing, but would appreciate guidance about covering all angles. This is one of those cosmetic things that doesn't look right in Trinity. We've done so much good work with renaming and branding that to see "KDED" in kcontrol, dialogs, etc., just looks awkward. Thanks. Darrell

12 years, 7 months

Updating TDE for Administrators help guide

by Darrell Anderson

I'm updating various help guides. The first section of the "TDE for Administrators" help guide, "Chapter 25. TDE Internals, Overview," is empty. Note: To view this help guide, select the TDE User Guide and scroll to section VI. I would be grateful for suggestions and ideas for what information should go in this section. For R14 I would like at least to provide an outline of topics, even if we don't get around to actually providing detailed content. Thanks! Darrell

12 years, 7 months

Commit 513ffc6e (kled off color) causes log out crash?

by Darrell Anderson

Tim, Within the past two days or so I am experiencing occasional crashes when I log out of the Trinity session. I suspect commit 513ffc6e because of this backtrace: [Thread debugging using libthread_db enabled] [KCrash handler] #5 0xb6139a67 in raise () from /lib/libc.so.6 #6 0xb613b2e2 in abort () from /lib/libc.so.6 #7 0xb617805d in __libc_message () from /lib/libc.so.6 #8 0xb617e5aa in malloc_printerr () from /lib/libc.so.6 #9 0xb6181503 in _int_free () from /lib/libc.so.6 #10 0xb61846b0 in free () from /lib/libc.so.6 #11 0xb636b191 in operator delete(void*) () from /usr/lib/libstdc++.so.6 #12 0xb636b1ed in operator delete[](void*) () from /usr/lib/libstdc++.so.6 #13 0xb675f2f0 in ~TQObject (this=0x8180da8, __in_chrg=<value optimized out>) at kernel/qobject.cpp:475 #14 0xb6794a39 in ~TQWidget (this=0x8180da8, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:1007 #15 0xb71cd059 in ~KLed (this=0x8180da8, __in_chrg=<value optimized out>) at /dev/shm/tdelibs/tdeui/kled.cpp:106 #16 0xb5eb8195 in ~KLedButton (this=0x8180da8, __in_chrg=<value optimized out>) at kledbutton.cpp:43 #17 0xb67949ad in ~TQWidget (this=0x8174e20, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:996 #18 0xb5ea1c11 in ~MixDeviceWidget (this=0x8174e20, __in_chrg=<value optimized out>) at mixdevicewidget.cpp:67 #19 0xb5ea739f in ~MDWSlider (this=0x8174e20, __in_chrg=<value optimized out>) at mdwslider.h:66 #20 0xb67949ad in ~TQWidget (this=0x8171c28, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:996 #21 0xb5e9bab3 in ~ViewBase (this=0x8171c28, __in_chrg=<value optimized out>) at viewbase.cpp:68 #22 0xb5ea0331 in ~ViewSliders (this=0x8171c28, __in_chrg=<value optimized out>) at viewsliders.cpp:59 #23 0xb5e9c7a5 in ~ViewOutput (this=0x8171c28, __in_chrg=<value optimized out>) at viewoutput.cpp:35 #24 0xb67949ad in ~TQWidget (this=0x81700e8, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:996 #25 0xb689df81 in ~TQFrame (this=0x81700e8, __in_chrg=<value optimized out>) at widgets/ntqframe.h:51 #26 ~TQWidgetStack (this=0x81700e8, __in_chrg=<value optimized out>) at widgets/qwidgetstack.cpp:182 #27 0xb67949ad in ~TQWidget (this=0x816ff08, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:996 #28 0xb688b4e6 in ~TQTabWidget (this=0x816ff08, __in_chrg=<value optimized out>) at widgets/qtabwidget.cpp:257 #29 0xb72e8119 in ~KTabWidget (this=0x816ff08, __in_chrg=<value optimized out>) at /dev/shm/tdelibs/tdeui/ktabwidget.cpp:77 #30 0xb67949ad in ~TQWidget (this=0x816f578, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:996 #31 0xb5eab253 in ~KMixerWidget (this=0x816f578, __in_chrg=<value optimized out>) at kmixerwidget.cpp:91 #32 0xb5e96cee in TQPtrList<KMixerWidget>::deleteItem (this=0x80b5710, d=0x0) at /opt/trinity/include/ntqptrlist.h:153 #33 0xb6a22e81 in TQGList::clear (this=0x80b5710) at tools/qglist.cpp:704 #34 0xb5e96d1d in TQPtrList<KMixerWidget>::clear (this=0x80b5710) at /opt/trinity/include/ntqptrlist.h:96 #35 0xb5e970bd in ~TQPtrList (this=0x80b5710, __in_chrg=<value optimized out>) at /opt/trinity/include/ntqptrlist.h:73 #36 0xb5e9626f in ~KMixWindow (this=0x80b5620, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at kmix.cpp:103 #37 0xb5ebbc0b in ~KMixApp (this=0x80c2cb0, __in_chrg=<value optimized out>) at KMixApp.cpp:36 #38 0xb5e93b3d in kdemain (argc=7, argv=0x80a8560) at main.cpp:67 #39 0xb787e474 in tdeinitmain (argc=7, argv=0x80a8560) at kmix_dummy.cpp:3 #40 0x0804e461 in launch (argc=<value optimized out>, _name=<value optimized out>, args=<value optimized out>, cwd=0x0, envc=1, envs=0x80a8a3d "DISPLAY=:0.0", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x80a8a4e "ovenbird;1341414944;536038;3110_TIME51073") at /dev/shm/tdelibs/kinit/kinit.cpp:673 #41 0x0804f191 in handle_launcher_request (sock=9) at /dev/shm/tdelibs/kinit/kinit.cpp:1240 #42 0x0804f89e in handle_requests (waitForPid=<value optimized out>) at /dev/shm/tdelibs/kinit/kinit.cpp:1443 #43 0x08050db0 in main (argc=5, argv=0xbf934614, envp=0xbf93462c) at /dev/shm/tdelibs/kinit/kinit.cpp:1909 Darrell

12 years, 7 months

Help Handbooks

by Darrell Anderson

I started an etherpad to track missing, broken, or empty help handbooks. Please add to the list as necessary. http://trinity.etherpad.trinitydesktop.org/50 Darrell

12 years, 7 months

TDE licensing question

by Darrell Anderson

From the help handbook FAQ: All TDE libraries are available under the LGPL making commercial software development for the TDE desktop possible, but all TDE applications are licensed under the GPL. Is everything in TDE now fully GPL or do LGPL remnants remain? Darrell

12 years, 7 months

Minimum hardware requirements

by Darrell Anderson

From the help handbook FAQ: What kind of hardware do I need to run TDE? To run TDE it is recommended that you have at least a pentium II processor, 64MB of memory and 500MB of free disk space for a basic installation. While TDE may run on slower configurations than this, performance can be severely impaired. Generally, if your computer runs an X-Server already with other desktop environments or window managers it's probably fast enough to run TDE. I have tested Trinity on a PII with 448 MB of RAM. Barely usable and requires patience. What are _realistic_ minimum hardware requirements? I'm guessing Pentium III and 512 MB of RAM. Thoughts? Experiences? Darrell

12 years, 7 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels