<table><tr><td style="">kossebau 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/D10703">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/D10703#228051" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;">D10703#228051</a>, <a href="https://phabricator.kde.org/p/nicolasfella/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@nicolasfella</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><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/D10703#228012" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;">D10703#228012</a>, <a href="https://phabricator.kde.org/p/kossebau/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@kossebau</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><p>Has there been any talk to other Qt5-based projects which might be interested in sharing KDE Connect efforts? E.g. AsteroidOS might come into mind or Unity8, who both might be happy to be able to reuse at least the kdeconnect core lib, and then add their own UI to that.</p>
<p>What would you think about some kdeconnect-qtcore which get the content of "core/", ideally even without k18n (error messages could be done with UI-textless ids) and some hooks for config storage system.</p></div>
</blockquote>
<p>Someone had this idea sometime, but it didn't get much traction.</p></div>
</blockquote>
<p>Meanwhile found it (<a href="https://github.com/Bjoe/KConnectClientLib" class="remarkup-link" target="_blank" rel="noreferrer">https://github.com/Bjoe/KConnectClientLib</a>), next to <a href="https://phabricator.kde.org/p/albertvaka/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@albertvaka</a> 's take on it (<a href="https://albertvaka.wordpress.com/2014/10/23/kde-connect-feature-brainstorming/#comment-1599" class="remarkup-link" target="_blank" rel="noreferrer">https://albertvaka.wordpress.com/2014/10/23/kde-connect-feature-brainstorming/#comment-1599</a>):</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>Actually I think this changes should be merged into the main git repo, so we don’t have to maintain two versions of the code. Right now the main repo is already split in more small parts, and for example the kded related code is already in a different directory. The last goal should be to have a Qt-only repo with a backend without user interface, and a different repo for the UI and KDE integration (plus another one for Gnome, Unity…), that should use DBus to communicate with the desktop-agnostic backend. This separation is quite done already, but not completely.</p></blockquote>
<p>Which I understand as principle support for such a qtcore repo, at least at that time :)</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>Before we pursue this we should have close collaboration with at least one stakeholder, otherwise we might just waste our time.</p></blockquote>
<p>Agreed.</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>This could also be beneficial for alternative UIs like <a href="https://phabricator.kde.org/p/andyholmes/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@andyholmes</a> Gnome extension. Since he decided not to use the official KDE Connect core it would be nice to hear about his reasoning why he didn't so we know where we have to improve.</p></blockquote>
<p>I would assume the "improvement" needed would be to drop the usage of Qt libs, so possibly not to happen ;) BTW, actually I was surprised to see the KDE Connect Android not being done with Qt, but with native Java (or whatever the oficial language name is?). Similar motivation, I assume.</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>I think it could be a idea worth pursuing if we actually find people interested in it</p></blockquote>
<p>If I look at this patch as well as the recent parallel effort <a href="https://github.com/R1tschY/harbour-sailfishconnect" class="remarkup-link" target="_blank" rel="noreferrer">https://github.com/R1tschY/harbour-sailfishconnect</a> (who so created a fork for their needs) I would think some people are showing up now.Including myself, slowly getting my fingers dirty here :) Never managed to release something for Sailfish OS, only did some experiments with writing an <a href="https://frinring.wordpress.com/2015/11/25/marble-maps-forking-for-sailfishos/" class="remarkup-link" target="_blank" rel="noreferrer">app variant of Marble Maps for SailfishOS</a> (as well as minimal rebuilding of Sailfish Office with Calligra code), so pretty interested to finally get something done and released, also for my usage needs. And with that experience, I also very much would prefer to have some non-QWidget-dependent code as common shared base.</p>
<p>For now though I would agree it is best to do the SFOS variant in the same repo. But then see to slowly prepare splitting things out. Not my call, just my 2 cents and showing up willing hands :) Time to get my SFOS SDK updated and working again, so I can do more than commenting. Even more as my latest commits made this patch no longer apply.</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R224 KDE Connect</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D10703">https://phabricator.kde.org/D10703</a></div></div><br /><div><strong>To: </strong>piggz, KDE Connect, apol, mtijink<br /><strong>Cc: </strong>andyholmes, albertvaka, kossebau, mtijink, vonreth, apol, KDE Connect, nicolasfella, adeen-s, SemperPeritus, ahmedbesbes, daniel.z.tg, jeanv, seebauer, bugzy, MayeulC, menasshock, ach<br /></div>