activitymanager api

[Marco Martin]

On Wednesday 06 October 2010, Chani wrote:
> [crap, I suck at reply-to...]
> 
> On October 6, 2010 21:57:57 you wrote:
> > On 6 October 2010 21:40, Chani <chanika at gmail.com> wrote:
> > > summary for people who are not ivan:
> > > we were talking off-list about needed additions to activitymanager
> > > kded, to support the shiny fun session stuff.
> > > 
> > > the new API that's already agreed on (modulo naming conventions) is:
> > >  void requestCloseActivity(id);
> > >  QStringList openActivities();
> > >  QStringList closedActivities();
> > 
> > At least in the service, I went for ListActivities(Status)
> > 
> > >  activityClosed(id);
> > >  activityCloseCancelled(id);
> > 
> > What about having one method with a bool?
> 
> neh, it'd be awkward api. activityClosedOrCancelled()? yuck.
> plus, everyone but plasma will be ignoring the cancel signal.
>
closed*OR*Cancelled?
what this signal is supposed to do? a closing has been cancelled, an event 
where we are not sure if it was closed or cancelled or? ...

Cheers,
Marco Martin