Re: Reinstall KDE completely
Am Sonntag, 20. September 2015, 18:13:23 CEST schrieb M.: > Sorry, Martin, but what I´m trying to achieve is irrelevant. I need to do For you it seems to be. For me it is not: Cause instead of wiping an existing installation completely, there may be easier ways to fix up issues with it. > So I´ll remove all packages by hand and the config files one by one - it > seems that is the only way. If you are concerned with this, you can consider to write an upstream bug report. I am not sure whether it could change anything tough. I actually would like to have all Plasma and KDE application configuration files in one directory as well. [top posting not fixed properly this time] -- Martin
Re: KDE5 Java SystemTray not supported
Thanks for your answers ! They gave me some insight and I started reading... sni-qt is for QT4 only. Since I have a QT5.4 KDE (Debian unstable) and QT5.4 has the QPA-API (which replaces sni-qt), I should see my Tray Icon regarding http://blog.martin-graesslin.com/blog/2014/06/where-are-my-systray-icons/. But I don't. Could anyone provide an Java example code that shows SNI / TrayIcon on QT >= 5.4 (using OpenJDK 7 or 8) ? I could and would amend my application. Regards, Tim Rühsen On Friday 18 September 2015 23:52:56 Kevin Krammer wrote: > On Friday, 2015-09-18, 11:18:09, Richard Newton wrote: > > I had similar problem with "synergy" and have seen reports about other > > programs. As a work-around I installed "lxpanel", configured it to only > > show the system-tray, located it so it doesn't interfere with the KDE > > panel, and made it unobtrusive. Any panel should work, I only used > > lxpanel > > because I was familiar with it and it is light-weight. > > > > I understand KDE changed the way they handle system-tray items. Either > > they > > need to make a way to use the "old method" or all the effected programs > > > > will need to adjust to the KDE method. Don't know how that is going to > > go! > > All major workspace implementations (GNOME, KDE, Unity, but also smaller > ones) on Linux are changing this because the current (now legacy) option is > based on an X11 specific mechanism and won't be available on Wayland or > Mir. > > The new system, called Status Notifier Icons, is based on a windowing system > independent mechanism and can be used on X11 and next generation display > systems. > > Most UI frameworks have kept up with that change, after all they want to > stay relevant in the future as well, but it seems Java hasn't or at least > not in the version used by Tim's program. > > Quite a shame given that Java started out as *the* option for cross platform > application development, but always lacked platform integration in the > default feature set (one of the reasons why so many multiplatform Java > applications use Eclipse's SWT instead of SWING). > > Anyway, for now there are quite some tools capable of providing an XEmbed > based "tray area", I think Martin Gräßlin's blog even mentions a couple. > > Cheers, > Kevin
Re: KDE5 Java SystemTray not supported
On Monday, 2015-09-21, 15:08:54, Tim Ruehsen wrote: > Thanks for your answers ! > > They gave me some insight and I started reading... > > sni-qt is for QT4 only. Since I have a QT5.4 KDE (Debian unstable) and QT5.4 > has the QPA-API (which replaces sni-qt), I should see my Tray Icon > regarding > http://blog.martin-graesslin.com/blog/2014/06/where-are-my-systray-icons/. > But I don't. No, this is a misunderstanding I think. qni-qt is for Qt4 applications to show "Status Notifier Items" (in short "SNI"). It doesn't matter if the SNI host is even using Qt. The QPA für Qt5 includes that already, so a Qt5 application can use SNI out of the box. In your case we have a Java application. Unless it or the Java Class Library it uses have Qt in use for platform integration, then neither sni-qt nor the QPA have anything to do here. > Could anyone provide an Java example code that shows SNI / TrayIcon on QT >= > 5.4 (using OpenJDK 7 or 8) ? I could and would amend my application. My, quite limited, understanding of SNI is that the communication between application and SNI host happens via D-Bus [1]. If there is currently no nice wrapper for Java, you might have to use D-Bus via the D-Bus Java bindings directly. Cheers, Kevin [1] http://www.notmart.org/misc/statusnotifieritem/ might not be the most current version, just came up first when googling signature.asc Description: This is a digitally signed message part.
Re: Akonadi/KDEPIM upgrade hints
On Sunday, 2015-09-20, 19:37:07, Martin Steigerwald wrote: > Am Sonntag, 20. September 2015, 18:11:26 CEST schrieb Kevin Krammer: > > On Sunday, 2015-09-20, 13:07:29, Martin Steigerwald wrote: > > > Am Sonntag, 20. September 2015, 12:57:45 CEST schrieb Martin Steigerwald: > > > > Hi! > > > > > > > > Please update to 15.08 in lockstep for kdepim and akonadi packages. > > > > > > > > If you upgrade to akonadi 15.08 before installing kdepim 15.08 your > > > > kdepim > > > > 4.14 will be inoperable. Thats the switch to Qt5 based akonadi and > > > > kdepim. > > > > Qt4 based KDEPIM cannot talk to Qt5 based Akonadi. > > > > > > BTW Akonadi 15.08 contains the binary protocol which helps to improve > > > performance. > > > > That sounds like the new version of the Qt based kdepimlibs is not shipped > > or not somehow not used by the Qt4 based kdepim. > > Hm? > > According to what I saw on debian-qt-kde-ml Maxy basically uploaded Akonadi, > KDEPIM and kdepim-runtime stuff to unstable, yet, as far as I am aware its > important to update it all in once. > > I don´t think KDEPIM 4.14 can talk to new Akonadi 15.08. Thats all I wanted > to point out. When packages are available on Tuesday I will try to update > to them on workstation at work, for laptop I need to stay with > self-compiled stuff for now. When Akonadi server switches to a new protocol, they need to update the library to also use that protocol. KDEPIM, i.e. the applications, just use the library. Some of all other applications that use the Akonadi client libraries in kdepimlibs, e.g. Kraft. Even if there is a new version of the applications from KDEPIM, not updating the library will break all these other applications. Cheers, Kevin signature.asc Description: This is a digitally signed message part.
