On March 30, 2015, 5:48 p.m., Martin Klapetek wrote: > > If the host application is required to check for a property, then this > > should be documented as well. > > > > I'm unsure about the use-case there though. Why do we need to filter the > > actions? If we just want chat, wouldn't it be better to directly request it > > to KTp? > > Eike Hein wrote: > > I'm unsure about the use-case there though. Why do we need to filter > the actions? If we just want chat, wouldn't it be better to directly request > it to KTp? > > We don't want frontends to be tied to KTp in the long run - we want other > messengers (e.g. Konversation) to integrate with KPeople, and a programatic > way to start a conversation using the user's preferred messenger (we already > have a Default Apps setting for one), depending on presence. > > Something like startTextChat(PersonData *data) would be much better to > hide the implementation instead of relying on action list sorting to return > the preferred TextChatAction first, but as KTp is the only available backend > right now this is fine for use in Plasma 5.3, there's no need to rush the API > design. > > There was some email forth and back on this you were CC'd on btw.
Clients are not required for checking the property, they can if they want/need to, as Eike explains. Adding more metadata to the actions only allows for better flexibility, this would also allow for example to group related actions together in say address book. - Martin ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/123184/#review78223 ----------------------------------------------------------- On March 30, 2015, 5:03 p.m., Martin Klapetek wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/123184/ > ----------------------------------------------------------- > > (Updated March 30, 2015, 5:03 p.m.) > > > Review request for Telepathy and Eike Hein. > > > Repository: kpeople > > > Description > ------- > > Some clients need/want to filter actions based on types, this adds the > actions enum with currently known actions. Plugins returning QList<QAction*> > should then use this enum to set the appropriate type on the action (via > setProperty). > > I've put it to PersonData because all code dealing with actions currently > need to include PersonData header and I'm not sure if it makes sense anywhere > else. > > > Diffs > ----- > > src/persondata.h c3f99a9 > src/widgets/actions.h 2931ef8 > > Diff: https://git.reviewboard.kde.org/r/123184/diff/ > > > Testing > ------- > > > Thanks, > > Martin Klapetek > >
_______________________________________________ KDE-Telepathy mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-telepathy
