On 13-11-10 01:55 AM, PCMan wrote: > 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.
...and that necessitates a custom appindicator host... how? My point is that, if you write a non-distro-specific plugin to handle the Status Notifier spec that KDE apps use, then applications using libindicator (intentionally or via an Ubuntu patch) should Just Work™ because libindicator's D-Bus API is a restricted subset of it. Think of it as similar to how the current version of the YAML spec allows certain bits of optional punctuation so that JSON is a valid subset of YAML. If you've already got a quality YAML parser, you don't need to also include a separate parser for JSON. > > > (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 > > http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk > _______________________________________________ > Lxde-list mailing list > Lxde-list@lists.sourceforge.net <mailto:Lxde-list@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/lxde-list > > > > > ------------------------------------------------------------------------------ > 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 > http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk > > > ------------------------------------------------------------------------------ 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 http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ Lxde-list mailing list Lxde-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxde-list
