<table><tr><td style="">antonanikin 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/D3424" rel="noreferrer">View Revision</a></tr></table><br /><div><div><blockquote style="border-left: 3px solid #8C98B8;
color: #6B748C;
font-style: italic;
margin: 4px 0 12px 0;
padding: 8px 12px;
background-color: #F8F9FC;">
<div style="font-style: normal;
padding-bottom: 4px;">In <a href="https://phabricator.kde.org/D3424#87489" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;" rel="noreferrer">D3424#87489</a>, <a href="https://phabricator.kde.org/p/mwolff/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;" rel="noreferrer">@mwolff</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><p>Any update on this? Sounds like a useful feature</p></div>
</blockquote>
<p>Hi, Milian, I have an updated version, but it not finished. The current state is:</p>
<ol class="remarkup-list">
<li class="remarkup-list-item">If we doesn't want to provide docsets loading the plugin can be quickly adapted to current master.</li>
</ol>
<ol class="remarkup-list" start="2">
<li class="remarkup-list-item">Zeal's author doesn't provide it's infrastructure for docsets downloading :(</li>
</ol>
<ol class="remarkup-list" start="3">
<li class="remarkup-list-item">I have quick-and-dirty version of scripts which downloads docsets information from github repositories and convert them in "compressed" form, which currently hosted on my server. The docsets repo author agrees to provide it's stuff for our plugin with providing copyright information.</li>
</ol>
<p>Now I don't know which way is better. Some peoples also suggests to provide library/kioslave for docsets support. All this possible but with different time cost. I also agree with Rene when he suggest to add ability for external-app documentation viewer, because the internal is far from ideal :(</p>
<p>Personally for me the ideal situation is provide "full stack" solution with our docsets information distribution server and downloading/updating docsets independently from Zeal (but if we can share docsets with Zeal it may be useful) with creating some external app (something like KDevDoc, Zeal/Dash inspired), which supports all types of documentation (Qt, man, cmake, dash docsets, etc) and provides an API to integrate it with KDevelop as internal or external viewer (user choice).</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R32 KDevelop</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D3424" rel="noreferrer">https://phabricator.kde.org/D3424</a></div></div><br /><div><strong>EMAIL PREFERENCES</strong><div><a href="https://phabricator.kde.org/settings/panel/emailpreferences/" rel="noreferrer">https://phabricator.kde.org/settings/panel/emailpreferences/</a></div></div><br /><div><strong>To: </strong>antonanikin, KDevelop<br /><strong>Cc: </strong>mwolff, ltoscano, kfunk, brauch, kdevelop-devel<br /></div>