On Sun, Nov 10, 2013 at 2:41 PM, Stephan Sokolow <gmane.ssokolow@spamgourmet.com> wrote:

On 13-11-10 12:08 AM, PCMan wrote:
> After these are done, we can develop plugins outside the lxqt-panel
> source tree. So other third parties can develop lxqt panel plugins as
> well. We can also develop some distro-specific panel plugins, such as
> libindicator plugin for ubuntu.

Why would you need a libindicator plugin for Ubuntu?

Everything I've read indicates that the status notifier D-Bus API used
in KDE via KStatusNotifierItem is a superset of the libindicator D-Bus
API that's trying to become the successor to the old XEmbed standard and
a host for that wouldn't be distro-specific.

Yes, but ubuntu goes their distro-specific way in this area. Many applications are changed to use appindicator by default in ubuntu. I have no comment on the thenical details about which one is better.
I just want to make sure the users can have a working desktop and get what they want.
So if some distros insist that they want to use different technologies, be it upstart or appindicator, I hope that we can support it to some degree if it's not too difficult. Mir is another story, though.
Since ubuntu is a popular distro that many people are using, I hope the users can have an lxde-qt desktop as usable as in other distros.

(Though, given how libindicator is the only client binding that seems to
be available for GTK+, I could sort of understand if the whole purpose
was to un-swap the idiotic "context menu is primary (left-click), toggle
visibility is secondary (middle-click in Unity)" behaviour that
libindicator forces on applications.)

November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
Lxde-list mailing list