tde-devels

devels@trinitydesktop.org

9 participants
3789 discussions

Re: [trinity-devel] tdebindings renaming/rebranding patch
by Darrell Anderson 08 Jan '14

08 Jan '14

>Has anyone approached the endowment and asked if they would >release tde.org to >the project? It may well be worth a shot. I for one would much >prefer tde.org >over trinitydesktop.org (just from a typing standpoint) Who types URLs any more? :) My two cents: I prefer trinitydesktop.org. Darrell

2 1

Re: [trinity-devel] tdebindings renaming/rebranding patch
by Darrell Anderson 08 Jan '14

08 Jan '14

>Wow, many times I thought that it might be proper to rename some >parts in >tdebindings - such as in java org.kde. => org.trinitydesktop. Glad >to >hear that you decided to do it! We can find another way to pass >the >patch, to I could see patch before will be pushed to git? 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. Darrell

3 2

Re: [trinity-devel] R14 press information
by Darrell Anderson 07 Jan '14

07 Jan '14

>What makes marketing of opensuse different from trinity is >that opensuse >work on a defined release schedule and has always done a number of >things to >beat the drum about their release number next. We have plans to enact a maintenance release schedule after we release R14.0.0. Tentatively set at every 90 days. As is true with any software project, we keep pecking away at the "paper cuts," but a 90 maintenance release schedule also keeps Trinity in the news. >I see marketing for tde as giving some love and attention to the >wiki to insure >that it is a welcoming and informative place for new users and >distros to check >out, learn from and get involved. There were good etherpad efforts >in the past >that probably still contain a wealth of information that has not >made its way >into the wiki. I know we all have nothing but spare time, so the >wiki gets its >love as time permits (though candidly, I do think it could use a >bit, and I've >always pointed to the Archlinux wiki as a model of how to do a >distro with a >code base integrated with it) Ah yes, spare time. I have no idea how to resolve that. Would be nice, even if only for a few days, to relive the days when Trinity patches were being submitted almost hourly and folks like you and I were testing just as fast the patches were submitted. :) >When is the next tde meeting scheduled? We could put >marketing/wiki on the >agenda and at least firm-up a direction to take in making whatever >improvements >make sense. (hell, I might even get my freenode nick to register >correctly for >once...) Keep the list posted on the schedule. We already have etherpads documenting such tasks. We don't need meetings where typically, after all is said and done, more is said than ever gets done. Instead we need able-bodied people to step forward and help. Anybody can create a wiki account and edit, reorganize, etc. Any Trinity user can review help handbook documents and post review comments to this list --- I'll update any such reviews. Somebody out there in Trinity user land has web skills to create a proposed mockup for web site changes. As the Nike logo says, "Just do it." :) Darrell

1 0

Re: [trinity-devel] tdebindings renaming/rebranding patch
by Darrell Anderson 07 Jan '14

07 Jan '14

>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. A long while back I remember testing those files. They didn't work. I don't know whether the problem is the files, changes made to tdebindings, me, or some combination thereof. If the files do work we still need some notes somewhere how to properly use the files to test tdebindings. As a group, we've treated tdebindings as a black sheep way too long. Darrell

1 0

Re: [trinity-devel] R14 press information
by Darrell Anderson 07 Jan '14

07 Jan '14

>That's cool but are end users (like me) expected to compile >LibreOffice in order to use it with Trinity or will binaries be >offered. If binaries will be offered, the the wiki needs to be on >a >developer only wiki. My mother and sister just want to type >letters >not compile. Just saying. Understood, but this is the developer's mail list, not the user's mail list. The task list is legitimate for this mail list. :) Yes, users are not concerned with such tasks, but the developers are. Much of the focus of the wiki is for developers. Darrell

1 0

rebase of 3.5.13 tree drops all non 3.5.13 sources - howto fix?
by David C. Rankin 07 Jan '14

07 Jan '14

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.

2 3

Re: [trinity-devel] R14 press information
by Darrell Anderson 07 Jan '14

07 Jan '14

>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

2 1

Re: [trinity-devel] tdebindings renaming/rebranding patch
by Michele Calgaro 07 Jan '14

07 Jan '14

> 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

1 0

Re: [trinity-devel] tdebindings renaming/rebranding patch
by Darrell Anderson 07 Jan '14

07 Jan '14

>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

1 0

Re: [trinity-devel] Recent mouse click problems
by Darrell Anderson 07 Jan '14

07 Jan '14

>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

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels