tde-devels

devels@trinitydesktop.org

1 participants
3754 discussions

rebase of 3.5.13 tree drops all non 3.5.13 sources - howto fix?

by David C. Rankin

Slavek, all After fixing the 3.5.13 source trees I had with: git checkout v3.5.13-sru && git pull --rebase I have missing dependencies. (basically all submodules that did not have a v3.5.13-sru branch were wiped out) Example: On the 3.5.13 tree: 02:04 phoinix:/dat_f/tde/tde> l1 main/dependencies/ arts avahi-tqt dbus-1-tqt dbus-tqt qt3 tqtinterface On R14: 02:14 phoinix:/dat_e/tde/tde> l1 main/dependencies/ arts avahi-tqt dbus-1-tqt dbus-tqt libart-lgpl libcaldav libcarddav python-tqt qt3 sip4-tqt tqca tqca-tls tqscintilla tqt3 tqtinterface So basically libart-lgpl, libcaldav, libcarddav, python-tqt, sip4-tqt, tqca, tqca-tls, and tqscintilla were all dropped from the tree. (I'm sure I'm missing others under applications/ as well. How do I pull all the remaining R14 sources/sub-modules into my new 3.5.13 tree? Do I have to do a manual diff of the directory structures and then do a manual "git checkout master -- <missing>" for each missing dir --or-- is there a better way to do it? The only other way I can think of would be to do a full git checkout master and covert the entire tree to master and then come back and switch submodules that have v3.5.13-sru branches back? How do you suggest I fill in the 3.5.13 tree? -- David C. Rankin, J.D.,P.E.

11 years, 1 month

Re: [trinity-devel] R14 press information

by Darrell Anderson

>Yeah the website needs some love. It looks an engineer designed it >:D. Tim probably considers that a compliment --- in good engineering function always comes before form. :) Darrell

11 years, 1 month

Re: [trinity-devel] tdebindings renaming/rebranding patch

by Michele Calgaro

> Although I get tdebindings to build without failure, I don't know > how to test tdebindings. I wish we had a simple wiki instruction > page of how to test. Basically a collection of scripts, c, and java > apps that use TDE dialogs and functions. Hi Darrell, sorry for not having come back to this yet. I made a note in my list, but so far I have had no time to check how to test tdebindings. In tdebindings source code, there are a few folders called "test". They contain simple files written in Java, Python and Ruby that should test some of the tdebindings functionality. I doubt these are exhaustive tests, but they should serve as a good starting point. Michele

11 years, 1 month

Re: [trinity-devel] tdebindings renaming/rebranding patch

by Darrell Anderson

>Here is the patch (not archived or compressed): > >http://humanreadable.nfshost.com/misc/tdebindings-kde-tde- >rename.diff > >The patch is about 38 MB. > >Feel free to improve any way you want. > >Please test. Push to git when you are content. Although I get tdebindings to build without failure, I don't know how to test tdebindings. I wish we had a simple wiki instruction page of how to test. Basically a collection of scripts, c, and java apps that use TDE dialogs and functions. Darrell

11 years, 1 month

Re: [trinity-devel] Recent mouse click problems

by Darrell Anderson

>Could the recent patches to use udisks rather than pmount play a >role in this? The problem turned out to be nominal dust and incomplete contact of the plastic pushbutton stem against the micro switch actuator head. After cleaning the inside of the mice, I spliced a carefully cut small piece of duct tape to the end of pushbutton stems. The pushbutton stems now make firm contact on the micro switch actuator head. The mice are acting like new. No missed clicks, no double clicks instead of single cicks, no dropped select-and-drag problems. Darrell

11 years, 1 month

Re: [trinity-devel] R14 press information

by Darrell Anderson

>BTW, can I help with some non-programmer tasks? If so, show me >where... I listed several in my previous post. If you want to review top level handbooks, the wiki, etc., just send comments to this list. Usually I handle the handbook changes, but anybody with an account can edit the wiki. By 'top level' handbooks, I am referring to the first four links in the help handbook, when opening the handbook directly from the launcher menu. Likewise with the wiki. You don't have to edit but reviews are needed to start updating. Post comments to this list. :) Darrell

11 years, 1 month

Re: [trinity-devel] R14 press information

by Darrell Anderson

>Just points to consider from the article. I think this can go for >any >software (Windows and Mac included). Since I am not a developer >and >don't have to do releases, I never thought about what the >journalist >was saying. We have an etherpad where we already collect this information, including a draft press release and press contacts. More than help with those tasks, we need help with the following: * Reviewing top level help handbooks. * Reviewing the proposed R14 README. * Further testing of the r14-xdg-update script. * Reviewing and updating the wiki. * Reorganizing a web site that is functional yet needs a little "pizzazz." R14 is a big release, especially from a public relations perspective, and adding fresh polish to the web site would coincide nicely with the R14 release. * For coders, helping with those bug reports listed in the etherpad that have been identified as R14 "blockers." * Testing patches that are already attached to bug reports. * Developing a detailed wiki page for compiling LibreOffice with Trinity dialogs. Darrell

11 years, 1 month

Final inspection for KDE-TDE/kde/tde rebranding issues

by Darrell Anderson

All, I would like to inspect source tree text strings for instances of KDE/kde rebranding issues and update to TDE/tde. Mostly in tooltips and What's This help strings. My challenge is being able to efficiently grep only those strings, which often in the sources are multiple lines. I would appreciate shell scripting advice to find such text strings. Thanks! Darrell

11 years, 1 month

tdebindings renaming/rebranding patch

by Darrell Anderson

All, I have a massive tdebindings renaming/rebranding patch that I have been testing for several weeks. The patch renames the following: Text references of KDE->TDE Source directories kde*->tde*: kdejava->tdejava kdedcop*->tdedcop* etc. I do not experience any build failures or warning or error messages during the build. The patch is almost 30MB and too large to attach to a bug report. Push to git? Darrell

11 years, 1 month

Re: [trinity-devel] R14 press information

by Darrell Anderson

>Here is a lin[k] to said press kit: > >https://github.com/openSUSE/Press-Kit/zipball/12.3 > >Note that it is 37 MB. Downloaded. Thank you! Darrell

11 years, 1 month

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels