Darrell Anderson via tde-users wrote: > I tried using the kdbusnotifcation package. My original post was about > notify-send expiration times that are not being honored. So dbus > notifications do work in TDE but not in full conformance. > I am interested to know as notify-send uses dbus, concluding from your statement above, you have tried to use kdbusnotifcation which is actually using notification-daemon-tde. Is this correct? If so, I've been looking into DBus in TDE in the past few years and we did many improvements, some of which can be seen in 14.1. I am even testing a fully DBus notifications complient client for the past year or so, but as mentioned before, I could not identify any use case. When I was monitoring DBus I found out that Skype/Firefox and other applications do listen and handle notifications themselves. If you want to try this https://mirror.git.trinitydesktop.org/gitea/TDE/kdbusnotification/src/branch/feat/with_dbus-1-tqt I am sure if you try this, you will be satisfied. If you need a debian package for testing, let me know. On top there is not enough man power and priority to work more intensively, but Michele mentioned he is willing to backport some part of the Qt4 DBus code. IIRC it was few weeks ago. This is very good idea. At the moment it is much more work to create TDE DBus capable application, even with the improvements and bug fixing we did to dbus-1-tqt. You can see the PoC here https://mirror.git.trinitydesktop.org/gitea/deloptes/dbus-1-tqt-example This is the closest we could get. In Qt4 and later there is a way to access all the bells and wistles by just providing the xml introspection file. But as TDE is using dcop, all this DBus stuff is not being used that much in TDE. In the cases it is used ... it is not that good, I must agree. This is why I spent some time in the past 4 years learning more about DBus and doing some work. It is not without selfish interest ... you see I simply want to sync my phone contacts and calendar with the desktop as I was able to do it in 2004 with the Palm III. You will ask perhaps what it has to do with DBus ... well this is the bluetooth part that brought me to DBus and a kdebluez application that SuSE released just before KDE moved to Qt4. Since bluez5 is using dbus, I started looking for a way, how I can have all working as it should. Remember I am not focused on new applications but on working use cases. I hope I will be lucky to enjoy it working for couple more years, before some new "modern standard" tries to break things again. It happens about every 10y. > Anybody using free/libre software is aware of the break neck speed at > which software evolves and matures. A dozen years is a "lifetime" in > that respect. Many of the changes have much to do with modern standards. > Much software in TDE is from an era when there were few standards. TDE > remains entrenched in those old ways. The rest of the world has moved on > to support those standards. For example, despite claims on the TDE web > site, TDE is not XDG compliant. Well, if those "modern standards" were that good and everything was playing along, I guess we won't be using TDE. I myself am not a person that sticks to old things, because I am afraid of changing world. Unfortunately the changing world and the new standards brought a lot of new stuff that never works. So it is a consious trade off. And again I saw how during the years much more people joined the community and are helping improve TDE. I think your words are heard and this or that will be solved in the future. The problem is the man power as it is volunteer work. It is even amazing how people are motivated to do so many work aside normal life. > > Not to despair because dbus notification is broken in KDE too > (https://bugs.kde.org/show_bug.cgi?id=381693). In KDE the notification > design remains rooted in a presumption that KDE is the only DE > installed. With a shared heritage TDE design suffers from this same > foundation. > > TDE is similar and does not coexist well with other DEs. The GTK theming > engines are examples. That TDE remains relegated to living in /opt > purgatory will always cause issues that the other DEs do not have, > especially with environment variables. Many TDE users are unlikely to > notice these issues because TDE is the only DE installed and the only > one they use. Many TDE users likely have grown accustomed to various > warts and blemishes. > Perhaps you should write bug reports and also I am not sure if it is TDE or a general DE issue. I am unaware of a reason, why I would even try putting any other desktop on the daily driver. For testing purposes I use VM or USB images. My last experience with Gnome was horrible, KDE looked nice, but now and then things stop working. All other desktops are rubbish for daily use. I now searched for linux desktops and got 18. See there is TDE too: K Desktop Environment 3 is the third series of releases of the K Desktop Environment. There are six major releases in this series. After the release of KDE 4, version 3.5 was forked into the Trinity Desktop Environment. Wikipedia > My grand curse seems to be having worked as a technical writer for many > years and having a trained eye and mind to see both the "trees and > forest." I tend to break software more easily than most folks and tend > to discover usability issues faster than many people. I also have been > using computers for more than 40 years and have a different usage > perspective than most of the modern smartphone generation of computer > users. > You are the perfect tester! (jokingly) > I do not have any slick answers or solutions. sharing ideas is good enough BR
Attachment:
ksnapshotjsOZgP.png
Description: PNG image
____________________________________________________ tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx
