Hey, > Many thanks for this pointer. How closely pyOwnCloud behaviour follows the > existing ocsync and the upcoming owncloudcmd? As I said before pyOwnCloud is just using ocsync and usies the same configs like oCC and so on, so it is a replacement for oCC at the cmdline. The cmdline tool ocsync is released together with libocsync -> I don't know if Klaas is develop it any further or it just a thing that came from csync. owncloudcmd is developed by the mirall team. The pyOwnCloud is developed independly from ocsync and oCC. I see the place for pyOwnCloud as leightweight oCC client. Cause it is a very small layer on top of ocsync. You don't need QT or fancy stuff. We try to make all featuers that libocsync has available for users. f. ex. we added now bandwidth trotteling like oCC. For the upcomming 0.4 we planning to support the logging system from libocsync and the possibility to show the progress at the cmdline.
> If I understand with newest versions of the sync client ocsync is replaced > by owncloudcmd which would then be *exactly* equivalent to the desktop GUI > client. as i said before ocsync and owncloudcmd come from different projects. Regads, sandro
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Owncloud mailing list Owncloud@kde.org https://mail.kde.org/mailman/listinfo/owncloud
