[Owncloud] [GSoC 2011] syncing client

[Maxime Côté]

Hi all,

I'm one of those who develop this client:
http://gitorious.org/owncloud-sync-client and I'm still working on it, even
thought not as much as I would like because of school. It's nearly finish,
the UI is designed, the core mechanic is coded and working but the UI is non
working and I haven't find a way (still searching) to send the data to the
server easily and securely. It's written in C++ with Qt and a bit of Python
(mostly mercurial command) and work with mercurial to provide versioning of
files. The main mechanic is pretty simple: the user enter some files (or
folders) to sync and a interval for syncing (1 min, 5min, 10 min etc), after
that the client start a cron like daemon to send data over to the ownCloud
server. I know it's may not be the best way to do this, but it's the way we
were seeing it.


Cheers
Maxime



On Tue, Jan 25, 2011 at 8:21 AM, Robin Appelman <icewind1991 at gmail.com>wrote:

> On Tuesday 25 January 2011 09:36:47 Martín Marcucci wrote:
> > 2011/1/24 Miha Čančula <miha.cancula at gmail.com>
> >
> > > I saw your idea at the wiki page, and I would be very interested to
> > > write a client for ownCloud. I have followed its development closely
> > > and I am already using it at home, but unfortunately I do not have any
> > > experience with PHP. I do however have some xperience with C++, python
> > > and KDE/Qt, which would be good languages for a desktop client.
> >
> > Hi list, I'm interested in having dropbox style syncing. I want to
> > collaborate, I have experience with PHP and  C++ very little with QT
> > and python.
> > I think the way to go is make the client use inotify to monitor file
> > system changes and make a quick upload.
> If Qt is going to be used for the client, using QFileSystemWatcher is
> probably
> the best, it's portable across operating systems and uses features that the
> OS
> offers like inotify.
> But more difficult would be watching for changes on the remote server,
> there are
> a couple of ways to do that but all seem to have their downsides
> > The client might be a command
> > line utility or a daemon written in C or C++ to be tiny and eat little
> > resources. It might be able to be controlled by a GUI here can be QT
> > or GTK or FLTK and written in java, c, c++ python,etc...
> > If the core code of the daemon is based in non portable libraries, it
> > will be very difficult to port the client to other platforms.
> Splitting the core and gui is a good idea imo.
> >
> > I want to collaborate in one of the clients. Can the ones that are
> > programming a client upload the code somewhere so the rest of us can
> > take a look of it.
> > May be then they can make an entry in the wiki like Clients, a tiny
> > description and what is missing and the links to the repository, so
> > other developers can take  a look and collaborate.
> afaik there are 2 unfinised projects:
> http://gitorious.org/cloudsync a more general syncing client that uses kio
> and
> kdirwatch but kdirwatch doesn't work good with kio slaves.
>
> http://gitorious.org/owncloud-sync-client which is exactly as the name
> says it
> is but not yet in a working state from what I've heared
> >
> > Regards
> > --
> > R. Martin Marcucci    ( MarkU )
>
> -- Robin Appelman
> _______________________________________________
> Owncloud mailing list
> Owncloud at kde.org
> https://mail.kde.org/mailman/listinfo/owncloud
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/owncloud/attachments/20110125/ab28bc58/attachment.html>