What does the new screenlets daemon do?

[rgdg]

In the 0.0.10 version a Screenlets Daemon is added to gnome session (autostart), but when you add screenlets in screenlets-manager and choose "Automatically start on logon." it adds each screenlet individually to sessions too. It seems to work the same whether Screenlets Daemon runs or not. SO, what does Screenlets Daemon do?

It's a lot more cluttered adding all of them individually. Id rather start them in one script at logon rather than 6 (for me) commands in logon.

So, unless I'm missing something, why not have screenlets-manager add one entry in sessions and let screenlets-manager edit that one entry to manage which screenlets start at logon.

Look forward to your input RYX, I really appreciate your hard work.

[RYX]

The screenlets-daemon sets up a DBus-service which keeps track of opened screenlets and offers functions to get notified about those changes. That is needed for the ultra-cool Enable/Disable checkbox :) (e.g. it always gets notified if you quit or start a screenlet, no matter from where you add/quit it).

The individual autostart files are there because it seemed as if it integrates better with gnome (they appear each under System/Settings/Sessions/StartupPrograms). But maybe it makes more sense to have one starter which then launches a startup-script which then gets modified by the manager - I'll think about that (even though it doesn't really make any difference :D).

(And thanks, too - I really appreciate that people have fun with the outcome of my work ... :))

[rgdg]

The individual autostart files are there because it seemed as if it integrates better with gnome (they appear each under System/Settings/Sessions/StartupPrograms). But maybe it makes more sense to have one starter which then launches a startup-script which then gets modified by the manager - I'll think about that (even though it doesn't really make any difference :D).

(And thanks, too - I really appreciate that people have fun with the outcome of my work ... :))

Ok, thanks for the clarification. You're right, it doesn't really make a difference. I'll put "my vote" in the one starter box. Often I'll disable things in sessions (fusion, awn or kiba, and screenlets) to make a simple/less ram intensive mode so unchecking one box as opposed to six is great. But if it doesn't matter to anyone else, your time is better spent fixing other problems/making screenlets even better. I can launch all the ones I want from a script like I did in 0.0.9 and not auto-enable in screenlets-manager!

I can't tell you how much I appreciate your/compiz develpopers/other project devels work. Not only does my desktop look better and be more functional, I just say I can already do that when my mac friends start going on about leopard.

[bouncingmolar]

It seems the other way of autostarting was better. The current method, pops the autostarting widget layer screenlets on the desktop for a few seconds surrounded by black before they get loaded into the widget layer.

I don't remember that happening before?