tde-devels

devels@trinitydesktop.org

7 participants
3840 discussions

Re: [trinity-devel] TDE Status Report
by Darrell Anderson 06 Apr '13

06 Apr '13

>As a tireless advocate KDE-3 user, I really want TDE has a long >life and continue to develop and improve in the future (short, >medium and long term). >I look for a desktop that is configurable and complete (not >simplistic as LXDE,...) and with characteristics centered in its >useful for users and no a sample of technic virtuosity (tablet >sense GNOME3/Shell/Unity, plasmoids KDE4,...). KDE3/TDE and XFCE4 >are the closest to this ideal of desktop focused on what users >really need to take advantage of your desktop (MATE is too simple, >more inline with LXDE), and KDE3/TDE most than XFCE4 (KDE3/TDE is >more complete in features). (My apologize for those who feel >uncomfortable with this statements, nor do I have any interest in >entering into a discussion about desktop environments). I suspect we all share similar sentiments for wanting to use Trinity. :) >As a reporter of a lot of bugs, my biggest reservations about TDE >has been little attention paid to solve bugs reported. I have find >frustrating that TDE have a number of bugs significantly greater >than its predecessor KDE3 (comparing TDE with Debian Etch and >Lenny's KDE-3, I tested TDE in Lenny, Squeeze and Wheezy). Several >months ago I volunteered to help with what little I can to do for >the development of TDE (basically contribute with Spanish >translations and report bug), but that I continue locating bugs >back down me to invest time in translations and more. If you >really are going to invest a lot of effort in TDE now to resolve >outstanding bugs, for me is the best possible news! Yes, this is good news and if all goes well, as the days go by we'll see a dramatic change in this area. I'm looking forward to this as well. Bugs have a nasty way of eroding a person's enjoyment of any software. The old adage about "death by a thousand paper cuts" rings true with software bugs. :) The project road maps indicate this new emphasis as well. So let's all take a deep breath, start hacking, and start testing the patches! :D By the way, to help with translations, Slavek is the best person to contact about that kind of help. Darrell

1 0

Re: [trinity-devel] TDE Status Report
by Baron 06 Apr '13

06 Apr '13

Hi Tim & All, On Saturday 06 April 2013 03:59:48 Timothy Pearson wrote: > Hi all, > > After discussions with the core development team, I have realised > that I owe everybody a long overdue update regarding Trinity. > > I apologise for the relatively long term silence on these mailing > lists. Like most people, I have to work in order to keep the lights > on and the servers humming, and these commitments have taken time > away from TDE. In particular over the past several months I have not > had any spare time to dedicate to TDE, which is why most development > (other than Slavek's tireless patching) had appeared to grind to a > halt. > > The good news is that the work which had been taking most of my time > is now easing up. I am currently diving into the bugtracker and am > currently focused on getting R14.0.0 stabilized and ready to ship. > > Thanks to several other dedicated individuals involved in the Trinity > project, progress has continued while I was away. R14.0.0 is looking > good overall, and the R14.0.0 road map and long term TDE road maps > have been updated on the Etherpad to more accurately reflect our > goals. > > Despite my absence I am encouraged that TDE will continue to move > forward. > > After some discussions with the core developers of TDE, I have begun > to realise that the project's top priority from now on needs to be > resolving bug reports. Other work will continue, including > enhancements and feature requests, but bug quashing will need to > remain a top priority to ensure TDE's survival and success. > > Secondly, Trinity has much in common with other "secondary" desktop > environments. We never will have the developer power or userbase of > KDE, GNOME, or Unity, but like our cousin "secondary" desktops, TDE > has a vtal role to play in the free/libre software world. We should > strive for excellence within our particular software design model, > and not worry so much about what the Big Three desktops are doing at > any given instant. > > My motivation for using and developing Trinity is to create a desktop > that functions the way I think it should function. How people believe > a desktop should function varies widely and this is why so many > exist, along with many window managers. The Trinity philosophy does > not embrace certain popular elements now available in other desktops, > and those elements are unlikely to ever become a part of Trinity. > That kind of focus is neither "bad" nor "good." We live in a large, > varied world and there is plenty of room for all of these varying > opinions and designs. This is also part of the method why free/libre > software will succeed in the long run: by encouraging choice and > freedom of opinions. > > Continuing Trinity is not about "us" versus "them"; instead, we are > simply exercising our freedom of choice by improving our software as > we see fit. Nothing more, nothing less. > > Thank you so much for being patient the past several months. I know > it was difficult for many of you, but rest assured that work on TDE > will pick up again, especially with your continuing support! > > Timothy Pearson > Trinity Desktop Project Seconded: I would like to add my thanks to all those developers for their good work. They are achieving things that I am not able or skilled enough to assist with. My gratitude to them is well deserved. Thanks guys ! -- Best Regards: Baron

1 0

Re: [trinity-devel] Problem with URL links
by Darrell Anderson 05 Apr '13

05 Apr '13

On Fri, 05 Apr 2013 03:12:06 -0500 "Jean Milot" <milot.jean(a)gmail.com> wrote: >Hello, > >I have set Iceweasel to open URL link. > >If i create a link on my desktop (right clic), i can't open it if >i put in my kdeglobals : > >[KDE URL Restrictions][$i] >rule_12=list,,,,http,,,false >rule_13=open,,,,http,,,false > > >These lines are for forbidden http / https in konqueror. > >How i can do ??? > >Thanks for your help. This type of question probably is more appropriate for the users mail list, but look at tdelibs/tdecore/README.kiosk: http://git.trinitydesktop.org/cgit/tdelibs/tree/tdecore/README.kiosk The purpose of those rules and the kiosk framework is to restrict user access to various components. The reason you can't open the desktop link is one of the restriction rules is preventing that from happening. Figure out which specific rule is doing that. :) Darrell

1 0

Problem with URL links
by Jean Milot 05 Apr '13

05 Apr '13

Hello, I have set Iceweasel to open URL link. If i create a link on my desktop (right clic), i can't open it if i put in my kdeglobals : [KDE URL Restrictions][$i] rule_12=list,,,,http,,,false rule_13=open,,,,http,,,false These lines are for forbidden http / https in konqueror. How i can do ??? Thanks for your help. Sincerely, Jean

1 0

FW:
by jamesg＠dimensionality.com 02 Apr '13

02 Apr '13

http://www.zaszlokeszites.com/gjilq0.php

1 0

Re: [trinity-devel] Name of distribution in the version number of Debian and Ubuntu packages
by Darrell Anderson 01 Apr '13

01 Apr '13

>What do the other developers on this list think of the >current state of GIT in relation to a possible release? Regressions (14): http://bugs.trinitydesktop.org/buglist.cgi?cmdtype=runnamed&namedcmd =Regressions Blocker (12): http://bugs.trinitydesktop.org/buglist.cgi?cmdtype=runnamed&namedcmd =Blocker Critical (24): http://bugs.trinitydesktop.org/buglist.cgi?cmdtype=runnamed&namedcmd =Critical Patches Available (30): http://bugs.trinitydesktop.org/buglist.cgi?bug_status=PATCHAVAIL&que ry_format=advanced&order=bug_severity%2Cbug_id%20DESC&query_based_on =PatchesAvail Build Issues (79): http://bugs.trinitydesktop.org/buglist.cgi?cmdtype=runnamed&namedcmd =Build%20issues Darrell

1 0

Name of distribution in the version number of Debian and Ubuntu packages
by Slávek Banko 01 Apr '13

01 Apr '13

Hello, I noticed two problems with the name of distribution and its location in the version number of packages. 1) We can soon expect: Names of distributions are not ascending. After Wheezy will follow Jessie => packages with ~jessie in the name will be considered older than ~wheezy (and also ~squeeze). 2) It is a real problem already now: Before the name of the distribution is in the version of package 'packaging-release' number by tde-packaging. After split folder for new distribution this number is *always lower* than the previous distribution. This now makes it impossible to do dist-upgrade for many distributions. My suggestions are: 1) Use the version number of the distribution instead of the name. 2) Move the distribution version number before other numbers. For example, from: 14.0.0-0debian12+r789+pr42~wheezy Change version to: 14.0.0-0debian12.7.0+r789+pr42 And in the future (to allow switch format from native to quilt): 14.0.0~r789-0debian12.7.0+pr42 Note: I noticed that the same use version number of distribution can be found even in the standard ubuntu packages - such as firefox. Slavek --

2 1

Bugzilla Email Options
by Sergey Frolov 24 Mar '13

24 Mar '13

Hi. I'd like to ask if there is a specific reason for not allowing one to set 'Reporter' flag beside "I'm added to or removed from this capacity" option? I am trying to achieve behaviour similar of default Debian BTS, which sends confirmation letter for bugs, submitted by me. Regards, Sergey.

1 0

Problem with kicker
by Jean Milot 21 Mar '13

21 Mar '13

Hello, I have some problem with the process kicker. For example, it takes 99% CPU. I have about 10 kde desktop launch on the server (ltsp) and sometime the process kicker is not terminate at the end. Thanks four your help. Sincerely, Jean

4 9

Archlinux - systemd will cause challenges for Trinity
by David C. Rankin 18 Mar '13

18 Mar '13

All, I apologize for my absence, but economic challenges demanded my time elsewhere -- and will for the next little while. I wanted to drop a note on Archlinux changes that impact Trinity. Specifically the massive transition in Arch from an 'initscript' startup to 'systemd'. I have moved a test machine to systemd. Trinity (hal) does not start when systemd is used. The problem appears to be a hang on X startup. However, initscript behavior can be retained even after the move to systemd that allows Trinity to continue to run -- flawlessly (3.5.13-SRU). If any other archer has time, please look into booting to tdm on Arch. Any issues with systemd/hal should be noted on the hal AUR page. Thanks. I will investigate as time permits, but I don't foresee much free time for the next several months. Keep fighting the good fight. -- David C. Rankin, J.D.,P.E.

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels