KDBusService, Open and ActivateAction

[Alex Merry]

On 12/11/13 17:17, David Faure wrote:
> IOW, I would let the app handle this the way it wants.
> It receives the command line, it gets the dbus calls via KDBusService, so it 
> can handle it all.

Which means we need a way to *let* the application deal with it like
that.  As it stands, the application has a choice between duplicating
the internals of KDBusService (to check whether it is the first instance
or not) or not dealing with command line args passed to later instances.

With that constraint, we either need to implement a CommandLine-like
call (which means getting it added to the spec or adding our own
extension interface), or restructure how KDBusService is used so that
the application can parse the command line args before creating it, and
then tell it to make the correct D-Bus call if necessary.

I think the CommandLine call is probably the neatest solution (although
it does mean the application has two different paths for dealing with
command-line arguments).  I'll email Ryan about getting it in the spec.

Alex