Single Qt codebase for kdeconnect

Pavel Borisov pzinin at gmail.com
Thu Jan 22 09:29:49 UTC 2015


Oh, I see, you're porting KAlgebra to Android. Interesting. So you think 
that there's no problem in using KF5 for every platform?

On 22.01.2015 03:02, Aleix Pol wrote:
> It's not a problem to use KF5 on android and on blackberry it's fine
> as long as you use Qt5 (Blackberry itself uses Qt4, so it needs to be
> bundled).
>
> Please, let's not add FUD. It's definitely true that many of the
> frameworks are not easily portable, but let's keep the technical
> decisions clear.
>
> Aleix
>
> On Wed, Jan 21, 2015 at 9:11 PM,  <pzinin at gmail.com> wrote:
>> I don’t think we should use KDE libs for other things than UI. Bear
>> BlackBerry and Android platforms in mind.
>> 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.
>>
>> About sshfs: Again, I do not want to break existing code and architecture.
>> There is SFTP server in Android client already.
>> 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).
>>
>> From: Yuri Samoilenko
>> Sent: ‎Wednesday‎, ‎January‎ ‎21‎, ‎2015 ‎6‎:‎21‎ ‎PM
>> To: kdeconnect at kde.org
>>
>> 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.
>> 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(http://en.wikipedia.org/wiki/KDE_Frameworks_5). 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.
>>
>> _______________________________________________
>> KDEConnect mailing list
>> KDEConnect at kde.org
>> https://mail.kde.org/mailman/listinfo/kdeconnect
>>


-- 
Best regards, Pavel Borisov
Jabber ID: pashazz at gentoo.ru



More information about the KDEConnect mailing list