<table><tr><td style="">davidedmundson added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D10078" rel="noreferrer">View Revision</a></tr></table><br /><div><div>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>For the future perhaps there could be a XDG D-Bus interface for such quicksearch plugins, so a separate krunner-independent library would make sense for that as well.</p></blockquote>
<p>Gnome does have an equivalent: org.gnome.Shell.SearchProvider2</p>
<p>It's similar to how I would have done it if I wasn't trying to fit into the existing krunner achitecture. <br />
But it's not feasible do retrofit into here.</p>
<p>Making a client API speak both... /might/ be feasible.</p>
<hr class="remarkup-hr" />
<p>I want to us to make sure this is still usable without a library dependency, but I think having this makes sense for the KDE apps. Definitely +1 to the idea.</p>
<p>I like how you've made it so you can reply in a sync or async way without making the sync version too complex. <br />
I have a proposal that re-arranges a little bit to take it just a bit further.</p>
<p>void match( QSharedPointer<MatchContext> context)<br />
that context object stores the m_mLastMatchDBusMessage and has the addMatches methods and it calls finish in its destructor</p>
<p>If a user wants to reply normally, they just do context.setMatches() in this method, with nothing else.</p>
<p>The baloo/p-b-i code can cache the latest MatchContext as a member variable exactly like they currently cache the lastMessage, and everything else gets automatically taken care of. <br />
(with this API it looks quite easy to send the wrong data as a reply if a user doesn't handle the cancel signal correctly)</p>
<p>If a user wants to reply to all messages, they can too.</p></div></div><br /><div><strong>INLINE COMMENTS</strong><div><div style="margin: 6px 0 12px 0;"><div style="border: 1px solid #C7CCD9; border-radius: 3px;"><div style="padding: 0; background: #F7F7F7; border-color: #e3e4e8; border-style: solid; border-width: 0 0 1px 0; margin: 0;"><div style="color: #74777d; background: #eff2f4; padding: 6px 8px; overflow: hidden;"><a style="float: right; text-decoration: none;" href="https://phabricator.kde.org/D10078#inline-46274" rel="noreferrer">View Inline</a><span style="color: #4b4d51; font-weight: bold;">abstractrunner.h:161</span></div>
<div style="font: 11px/15px "Menlo", "Consolas", "Monaco", monospace; white-space: pre-wrap; clear: both; padding: 4px 0; margin: 0;"><div style="padding: 0 8px; margin: 0 4px; background: rgba(151, 234, 151, .6);"> <span style="color: #aa4000">void</span> <span class="n">matchingCancelled</span><span class="p">();</span>
</div><div style="padding: 0 8px; margin: 0 4px; background: rgba(151, 234, 151, .6);">
</div><div style="padding: 0 8px; margin: 0 4px; background: rgba(151, 234, 151, .6);"><span style="color: #a0a000">private</span><span class="p">:</span>
</div></div></div>
<div style="margin: 8px 0; padding: 0 12px;"><p style="padding: 0; margin: 8px;">please add a virtual hook for future expansion</p></div></div><br /><div style="border: 1px solid #C7CCD9; border-radius: 3px;"><div style="padding: 0; background: #F7F7F7; border-color: #e3e4e8; border-style: solid; border-width: 0 0 1px 0; margin: 0;"><div style="color: #74777d; background: #eff2f4; padding: 6px 8px; overflow: hidden;"><a style="float: right; text-decoration: none;" href="https://phabricator.kde.org/D10078#inline-46283" rel="noreferrer">View Inline</a><span style="color: #4b4d51; font-weight: bold;">dbusadaptor_p.h:31</span></div>
<div style="font: 11px/15px "Menlo", "Consolas", "Monaco", monospace; white-space: pre-wrap; clear: both; padding: 4px 0; margin: 0;"><div style="padding: 0 8px; margin: 0 4px; background: rgba(151, 234, 151, .6);"><span style="color: #74777d"> */</span>
</div><div style="padding: 0 8px; margin: 0 4px; background: rgba(151, 234, 151, .6);"><span class="n">class</span> <span style="color: #a0a000">DBusRunnerAdaptor</span><span class="p">:</span> <span class="n">public</span> <span class="n">QDBusAbstractAdaptor</span>
</div><div style="padding: 0 8px; margin: 0 4px; background: rgba(151, 234, 151, .6);"><span class="p">{</span>
</div></div></div>
<div style="margin: 8px 0; padding: 0 12px;"><p style="padding: 0; margin: 8px;">Can you put a 1 in the class name for future proofing.</p></div></div></div></div></div><br /><div><strong>REPOSITORY</strong><div><div>R308 KRunner</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D10078" rel="noreferrer">https://phabricator.kde.org/D10078</a></div></div><br /><div><strong>To: </strong>kossebau, davidedmundson, broulik<br /><strong>Cc: </strong>ngraham, Frameworks<br /></div>