On Tue, 14 Jan 2014 15:40:24 -0500 Conrad Hill-Knight <[email protected]> said:
> On Mon, Jan 13, 2014 at 9:35 PM, Carsten Haitzler <[email protected]> > wrote: > > you disabled the notification module? > > Well, that's what i thought... it was unchecked (in Extensions > > Modules > Core > Notification, this is the right place, isn't it? yes. this enables/disables the notification module > There's also Extensions > Notification) so i reenabled it, but no this is the settings FOR the notification module. it will only be here if the notification module is enabled. > change. I even restarted from the enlightenment menu to see if that > would help, but no luck. I was wondering if this module somehow works > in conjunction with another one, or some other setting somewhere. The > original top-right-corner pop-ups displayed in Unity, too, if that > makes a difference. well you need a session dbus running - but i assume you do as it used to work. enlightenment will start a session bus if it doesnt detect one already (via dbus session bus environment var). it could be that some other process took over being the notification module - something from gnome or kde? only 1 process can be the notification daemon handler. normally e gets in first and thus is the notification daemon IF it's enabled. > On a similar note, is there any documentation on what these various > modules do, and how to use them? A lot of them use abbreviations and > don't even have a one-line description (DBus Extension? AT-SPI D-Bus > Bus?). Just asking about these specifically, because i came across the > phrase "d-bus" a few times while trying to figure this problem out. the description below is all the documentation you'll get beyond asking case-by-case or reading the code. modules are basically runtime patches to enlightenment that can be added or removed at runtime rather than at compile. they came about as i added more and more features to enlightenment and realized... not everyone wants that feature at all or may want to change/replace it. to discourage people going and patching enlightenment thus creating forks, modules were created to allow clean creation of patches that can extend or replace functionality in e. since they are viewed as patches, e's internal api changes will affect/break modules like any patch will, but that's the same as any library that doesn't keep a stable abi (and e doesn't - much like the kernel - we just don't want to spend the time on it - we have efl for a stable abi as libs). so much like a lot of e's internal code - we haven't written documents explaining what e_comp.c does or e_zone.c or e_module.c - the name pretty much gives you the rough domain and responsibility and the rest is details. if you don't know what dbus is - use google. at-spi - same. use google. :) or maybe read the code for that module. :) -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
