<html>
<head>
<meta name="generator" content="Windows Mail 17.5.9600.20689">
<style data-externalstyle="true"><!--
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
}
p.MsoNormal, li.MsoNormal, div.MsoNormal {
margin:0in;
margin-bottom:.0001pt;
}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst,
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle,
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
line-height:115%;
}
--></style></head>
<body dir="ltr">
<div data-externalstyle="false" dir="ltr" style="font-family: 'Calibri', 'Segoe UI', 'Meiryo', 'Microsoft YaHei UI', 'Microsoft JhengHei UI', 'Malgun Gothic', 'sans-serif';font-size:12pt;"><div>I don’t think we should use KDE libs for other things than UI. Bear BlackBerry and Android platforms in mind. <br>However, admittedly, some plugins should have separated versions for each OS. For example, battery plugin - the approach on how we can show battery info is different on each OS.<br><br>About sshfs: Again, I do not want to break existing code and architecture. There is SFTP server in Android client already.<br>Though everything related to sshfs in windows seems vague so I’ll be realistic: it will have the lowest priority for me (though there’s no problems with OS X - FUSE is available).</div><div><br></div><div style="padding-top: 5px; border-top-color: rgb(229, 229, 229); border-top-width: 1px; border-top-style: solid;"><div><font face=" 'Calibri', 'Segoe UI', 'Meiryo', 'Microsoft YaHei UI', 'Microsoft JhengHei UI', 'Malgun Gothic', 'sans-serif'" style='line-height: 15pt; letter-spacing: 0.02em; font-family: "Calibri", "Segoe UI", "Meiryo", "Microsoft YaHei UI", "Microsoft JhengHei UI", "Malgun Gothic", "sans-serif"; font-size: 12pt;'><b>From:</b> <a href="mailto:kinnalru@gmail.com" target="_parent">Yuri Samoilenko</a><br><b>Sent:</b> Wednesday, January 21, 2015 6:21 PM<br><b>To:</b> <a href="mailto:kdeconnect@kde.org" target="_parent">kdeconnect@kde.org</a></font></div></div><div><br></div><div dir=""><div dir="ltr">About sftp plugin, portability and so on. I think that using KDE technology is greate, but I dream that mobile device can be integrated not only in KDE, but in gnome, win and so on. So I think we must aim on cimplicity of used technology to be able to not only port-as-is but write native application in simple way.<br>So sshfs is very simple high-performance(in compare to KIO) technology that can be easily used and integrated to any UNIX-like systems, but windows... Windows port can have own File-share plugin, utilized SAMBA for example. The new KF5 framework split KDE on three layers according to diffrent level of dependencies(<a href="http://en.wikipedia.org/wiki/KDE_Frameworks_5" target="_parent">http://en.wikipedia.org/wiki/KDE_Frameworks_5</a>). I think me must use tier1(dependent on Qt) and tier2(dependent on tier1) levels in kde-connect to reach simplicity and portability. So Kded and other runtime services must be used only for native integration(to KDE, Gnome) and so on.</div>
</div></div>
</body>
</html>