On Thu, 2010-03-11 at 21:20 +0100, Marcelo Hashimoto wrote: > > No. Libindicate is n:n really. It is just about counting messages and > > only provides a slight nod to dbusmenu in that applications that are > > using libindicate can also (not required) provide menu items for extra > > actions. They're different in that the different messaging sources for > > instance can't be in a hierarchy and are more closely associated to > > times and counts (messaging focused). > > > I think the better way to distinguish would be that libindicate is used > > to put entries inside the messaging menu, while libappindicator is for > > the application having its own menu outside of the messaging menu. > > Okay, those two responses got me a little confused... > is libindicate made for communicating only with the > messaging menu or any specific indicator? Come to > think of it, I did peek at libindicate-doc (whose > existence I only realized recently), and there were > some MessageMenu-specific sentences there...
Today libindicate is only for communicating with the messaging menu. I
don't think the library precludes other uses, but that's all it's used
for today.
> > Sure, I'm not defending the hardcoding or saying it's perfect. It just
> > hasn't been a requirement yet :) Obviously with
> > indicator-applet-complete it is a bigger issue, but that isn't really
> > anywhere by default, I don't think most people know about it yet.
>
> > I've been trying to put a bunch of this common code into libindicator
> > precisely for this reason. In general, I don't consider libindicator
> > API stable as it's more for making the indicator development easy and
> > fast so it changes as we need it to. I know everyone who's using it
> > today and I tell them :)
>
> > Great, well drop me or the list an e-mail when you get something
> > together I'd hate to do something like remove a feature that I thought
> > nobody was using and you were depending on because I didn't know
>
> Ok, I'm happy enough to know that the hardcoding
> is not by design. :) We'll try to work closely
> with you and report our experiences with the
> libraries.
Great!
> And I was almost forgetting... are there any plans
> for Mono bindings to libindicate?
I don't have any currently, but I'd happily accept a patch for it. More
about not having a reason to put the effort in, not something we're
trying to avoid.
--Ted
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Mailing list: https://launchpad.net/~ayatana Post to : [email protected] Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp
