xfrun4 + dbus

[Benedikt Meurer]

Jani Monoses wrote:
>>Looks good at first sight. I'd add service activation too. And I think
>>I'd be better to rewrite xfrun4 from scratch with only a very simple
>>fallback (without any goodies, just make sure it's fast).
> 
> I have just started on d-bus so to make sure, by service activation you 
> mean setting  dbus_message_set_auto_start (message, TRUE) ? 

Yap.

> Also I have 
> a DBusError there but do not really check it's contents, maybe there 
> should be just NULL instead.
> 
> xfrun4 rewriting from scratch can come after this works I guess. That 
> would mean a regression though for people who don't start dbus services 
> for this but still want the goodies (completion I suppose) at the cost 
> of startup time. When I tried xfrun without icon buttons it started 
> faster but still you could feel it start. There are a lot of files 
> stat() ed even without the icon stuff - ld.so files, fonts, locales.
> gmrun while faster still has a noticable startup time.
> 
> One other thing may be turning the current xfrun into a background 
> process started from xsession, providing the dbus service and the real 
> xfrun be only the remote call and no fallback. Then we'd have the same 
> behavior as now but relying on a slightly more complicated setup with 
> the advantage of lower latency. Then the default xfrun service provider
> could be optionally replaced by thunar/xffm.

As said, org.xfce.RunDialog can be implemented by every service, it
doesn't need to be Thunar/Xffm. It would just reduce overhead when
implemented by a file manager, since everything required for this to
work will already be loaded into memory/built into the file manager. I
think it's a good idea to provide another implementation -
xfce4-run-damon? ;-) - which can be run by xfce4-session on startup,
either using real session management or through the new autostart
mechanism, and which provides the run dialog for people that run neither
Thunar nor Xffm. This way, xfrun4 would really only do the
OpenDialogOnDisplay() call and can thereby be turned into a really
simple tool with only D-BUS dependency.

> Jani

Benedikt