<table><tr><td style="">dhaumann 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/D14497">View Revision</a></tr></table><br /><div><div><p>Hi Lothar. Everything in the KTextEditor namespace is public API. That's why we usually try to have excellent documentation there. The public API is also available on api.kde.org in the KTextEditor framework: <br />
<a href="https://api.kde.org/frameworks/ktexteditor/html/classKTextEditor.html" class="remarkup-link" target="_blank" rel="noreferrer">https://api.kde.org/frameworks/ktexteditor/html/classKTextEditor.html</a><br />
<a href="https://api.kde.org/frameworks/ktexteditor/html/classKTextEditor_1_1Document.html" class="remarkup-link" target="_blank" rel="noreferrer">https://api.kde.org/frameworks/ktexteditor/html/classKTextEditor_1_1Document.html</a></p>
<p>That said, it of course also makes sense to document internal API :)</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R40 Kate</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D14497">https://phabricator.kde.org/D14497</a></div></div><br /><div><strong>To: </strong>loh.tar, Kate, sars<br /><strong>Cc: </strong>dhaumann, Kate, sars, kwrite-devel, michaelh, kevinapavew, ngraham, demsking, cullmann<br /></div>