tde-devels

devels@trinitydesktop.org

5 participants
3840 discussions

Testing tdebindings
by Darrell Anderson 26 Feb '12

26 Feb '12

I'm able to build tdebindings against TQt3. Exceptions are qtsharp and xparts but I plan to test the former today. Yeah, a slight miracle anybody can build that package. :) (Several patches are needed.) I plan to further test building against both ruby 1.8.7 and 1.9.1. I notice there are directories in tdebindings named test. I presume these are test programs and scripts to ensure the bindings built correctly? Anybody know for sure? Darrell

1 1

tdelibs errors
by Robert Xu 26 Feb '12

26 Feb '12

I have working packages. But... they failed rpmlint checking: tdelibs failed the build process with the errors at the bottom. Can anyone help? I: A function overflows or underflows an array access. This could be a real error, but occasionaly this condition is also misdetected due to loop unrolling or strange pointer handling. So this is warning only, please review. W: tdelibs arraysubscript /home/abuild/rpmbuild/BUILD/tdelibs-R13.99/libkmid/track.cc:337 I: Program is likely to break with new gcc. Try -fno-strict-aliasing. W: tdelibs strict-aliasing-punning /home/abuild/rpmbuild/BUILD/tdelibs-R13.99/kimgio/dds.cpp:493, 503 W: tdelibs strict-aliasing-punning /home/abuild/rpmbuild/BUILD/tdelibs-R13.99/kioslave/iso/kiso.cpp:252, 307, 308, 314 W: tdelibs strict-aliasing-punning /home/abuild/rpmbuild/BUILD/tdelibs-R13.99/libkmid/deviceman.cc:547, 560, 579, 601, 622 W: tdelibs strict-aliasing-punning /home/abuild/rpmbuild/BUILD/tdelibs-R13.99/libkmid/fmout.cc:121, 235, 237, 238, 243, 280, 290, 302, 316 W: tdelibs strict-aliasing-punning /home/abuild/rpmbuild/BUILD/tdelibs-R13.99/libkmid/gusout.cc:200, 234, 236, 237, 241, 276, 298, 312, 407 W: tdelibs strict-aliasing-punning /home/abuild/rpmbuild/BUILD/tdelibs-R13.99/libkmid/midiout.cc:81 W: tdelibs strict-aliasing-punning /home/abuild/rpmbuild/BUILD/tdelibs-R13.99/libkmid/synthout.cc:167, 173, 180, 191 W: tdelibs strict-aliasing-punning /home/abuild/rpmbuild/BUILD/tdelibs-R13.99/tdecore/kcrash.cpp:304 I: Program returns random data in a function E: tdelibs no-return-in-nonvoid-function /home/abuild/rpmbuild/BUILD/tdelibs-R13.99/krsync/rsyncconfigdialog.cpp:180 E: tdelibs no-return-in-nonvoid-function /home/abuild/rpmbuild/BUILD/tdelibs-R13.99/tdecore/kapplication.cpp:198 -- later daze. :: Robert Xu :: rxu.lincomlinux.org :: protocol.by/rxu

2 2

tde-i18n localization files
by Darrell Anderson 25 Feb '12

25 Feb '12

How do I test the tde-i18n localization files? I can't read the other languages. I'm interested in validating that the various help files reflect entity changes I make in those files. I need to test the files with some basic spot checking of help files and verify the entities are correct. Oh, and when in the build sequence should those files be built? At the very end after all other packages are built? Thanks! Darrell

1 0

invalid use of incomplete type 'struct TQXEmbed'
by Darrell Anderson 25 Feb '12

25 Feb '12

Tim, Can you help or shed light how to fix this error? Thanks. xparthost_kpart.cpp: In constructor 'XPartHost_KPart::XPartHost_KPart(TQWidget*, const char*, TQObject*, const char*)': xparthost_kpart.cpp:24: error: invalid use of incomplete type 'struct TQXEmbed' xparthost_kpart.h:10: error: forward declaration of 'struct TQXEmbed' xparthost_kpart.cpp:25: error: no matching function for call to 'XPartHost_KPart::setWidget(TQXEmbed*&)' /opt/trinity/include/kparts/part.h:268: note: candidates are: virtual void KParts::Part::setWidget(TQWidget*) xparthost_kpart.cpp: In member function 'virtual DCOPRef XPartHost_KPart::registerXPart(const DCOPRef&)': xparthost_kpart.cpp:48: error: invalid use of incomplete type 'struct TQXEmbed' xparthost_kpart.h:10: error: forward declaration of 'struct TQXEmbed' xparthost_kpart.cpp:50: error: invalid use of incomplete type 'struct TQXEmbed' xparthost_kpart.h:10: error: forward declaration of 'struct TQXEmbed' make[4]: *** [xparthost_kpart.lo] Error 1 Darrell

2 2

Patches pushed to GIT
by Darrell Anderson 25 Feb '12

25 Feb '12

I pushed some patches to GIT. I don't expect problems but I'm still a newbie at GIT. Things to watch for: * You should see changes in the Help Center. Right now most of the changes are cosmetic, but at least when using Help you now see Trinity and TDE rather than KDE. * If during a package build you see errors about help files, please let me know right away. There should not be any but I'm only one person working on one computer. I have not yet updated help files for applications packages I don't yet build so just let me know and I'll push the patch. * The tdebase CMakeLists.txt was updated from STARTKDE->STARTTDE. This could affect your build script if you explicitly define that option. * The tdegraphics CMakeLists.txt was updated from WITH_LIBPAPER to WITH_PAPER. This was broken and since nobody complained I suspect nobody explicitly defined that option in their build scripts. You have to install the libpaper package from your distro repository to use that build option. * Obsolete tips and links have been removed from KTips. Please verify the tool still works. You should see all of the changes in the Commit Patches web page sometime tomorrow. Thanks! Darrell

3 7

Extending Darrell's script idea
by Keith Daniels 25 Feb '12

25 Feb '12

Hi All I have a marketing/advertising background. The following suggestion is primarily aimed at increasing the name recognition of "Trinity Desktop" but should have other useful side effects as well. This idea is structurally similar to the concept of "loss leaders" that commercial stores use to entice people to come to their store, in the hopes that they will buy something else while they are there (which they usually do). Darrel's suggestion of offering Kate scripts to the Trinity Desktop audience started me thinking about this idea. If we had something on the Trinity Desktop web site that people need or want (outside of Trinity itself), and that could be found through a Google search--they would go there to check it out and while there... be able to read what Trinity Desktop is, and what it is trying to do. If they find things they want and that help them (scripts in this case) they will post about what they found on social networks, blogs and forums. If they like what they read about Trinity Desktop, they will post about that as well--whether or not they are interested in using Trinity Desktop or not. These postings would increase hits to the Trinity Desktop site, and cause it to rise in Google ratings. This hopefully would put Trinity's matches in the first 100 results of a Google search--which would radically increase the hits on the Trinity Desktop site and name recognition. My idea is to start a "Trinity Desktop scripts" webpage or forum containing user submitted scripts. This should be interactive and monitored so I think something like a forum would be the best idea. The site/page would be based around the concept of "Useful scripts that can help you to learn scripting as well". It would include scripts that could be used from Konsole or from inside Kate or Konqueror (which sometimes have to be structured differently than standard scripts). Information on how to use scripts inside Kate and Konqueror would also be available. To have a script accepted, a vote or committee approval would be needed. Besides being useful (either in actual use or in learning to script) the script would have to be heavily documented by the writer so that the "what" and "why" of the script could be understood by users not familiar with scripting (the majority of them). What doing this would require: 1 - A web or forum page. 2 - Someone to create & monitor the page. 3 - Someone to manage the submissions, uploads and page entries for the scripts. 4 - Someone(s) to write a Trinity Desktop oriented description of each script -- the authors are usually terrible at this. 5 - People (or a voting system) to look at and and approve the scripts and descriptions. To seed this site/page--all of us could post of its existence on social network, forum and wiki sites that we are members of. I will volunteer to create and manage the web page (if it is not a wiki). Being a retied webmaster I have the skills to do so. Note that I will be on the road from mid April to late June. I could start it and set it up--but would not be able to put a lot of time into it until after June. I personally have been considering doing something like this for the last 5 years as a personal project--so it is not a new concept for me. Because of this my scripts are already heavily documented and ready to use. I have somewhere between 50 and 100 scripts that I think would qualify, and that are ready to be posted. I am sure the rest of you have quite a few scripts as well. This means that an impressive number of scripts could be put up rapidly, providing the variety needed to attract viewers. Thoughts? Another useful page/site similar in effect to the above would be one that specialized post and information on how to modify the appearance and function of menus, toolbars, popups, etc. for Trinity Desktop programs. Keith

2 2

Useful Kate scripts
by Darrell Anderson 25 Feb '12

25 Feb '12

I was considering opening an enhancement request to add some missing features to Kate. Specifically, adding a word count feature is what motivated me. Rather than file an enhancement request for adding a word count feature, I decided to first request a list of Kate scripts that all of you find useful. The key is "find useful" because there probably are hundreds or thousands of scripts floating around the web that could be added to Trinity. A word count script is useful. :) At this point I don't know whether the scripts should be added as part of tdeaddons or posted someplace at the wiki or web site. We can decide that later. Possibly we can vote and the most popular half-dozen can be added to tdeaddons and the remainder posted to the wiki or web site. If you use any such scripts, please share the name of the script and a full description. Either attach a copy to your email or post a link to the script. A full description is important because file names often are cryptic and do not lend well toward understanding the script's purpose. By the way, I found some word count script candidates: http://muzso.hu/2007/06/08/word-count-in-kate http://kde-look.org/content/show.php/Kate+script%3A+Word+Count?content=1360… http://old.nabble.com/Re%3A-Kate-external-tools-p3788414.html I have yet to test. :) Thanks! Darrell

5 10

Does your KHelCenter TOC fully populate?
by Darrell Anderson 24 Feb '12

24 Feb '12

For those who have Trinity installed from GIT. From the TDE Menu, select Help. When KHelpCenter opens, on the left side, top, in the navigator tabs, scroll to the far left to select the Contents tab. Open/expand Application Manuals. Open/expand Development. Do you see individual apps or only categories? Thanks! Darrell

1 1

Is Tree View Broken?
by Darrell Anderson 24 Feb '12

24 Feb '12

In Konqueror (built from GIT), I no longer see the tiny expansion and contraction widgets to the left of a folder. The little plus and minus in a box. Nothing I do makes the widgets appear. Would somebody confirm this behavior? Thanks! Darrell

2 5

Arch tarball specifications - why tqtinterface files prefixed with 'dependencies/'?
by David C. Rankin 24 Feb '12

24 Feb '12

Guys, Working with the current tarballs compared with those created from the git tree I have run into a difference in path information included in the existing tarballs instead of those created from a local copy of the git tree. The existing tarballs referenced in the PKGBUILD scripts contain the dependencies path information i.e.: dependencies/tqtinterface/ dependencies/tqtinterface/TODO dependencies/tqtinterface/ConfigureChecks.cmake dependencies/tqtinterface/COPYING dependencies/tqtinterface/CMakeLists.txt dependencies/tqtinterface/configure.in.mid dependencies/tqtinterface/qtinterface/ dependencies/tqtinterface/qtinterface/tqlcdnum.h dependencies/tqtinterface/qtinterface/parser2.sh While those I create from the git tree simply contain e.g.: tqtinterface/CMakeLists.txt tqtinterface/configure.in.bot tqtinterface/AUTHORS tqtinterface/admin/ tqtinterface/configure.in.mid Is prefixing the files in the tarball with the entire directory path below 'main/' going to be the standard? In the past, I have always excluded the module prefix (applications, common, dependencies, libraries, ...). Either way will work, but from a PKGBUILD standpoint, we need to make sure there is a standard. What is the consensus? -- David C. Rankin, J.D.,P.E.

5 9

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels