Hi, Great initiative, I was missing a cloud API in C++.
>From my 2 min skim-over: - Why the dependency on DBus instead of making each application access directly the storage? - Why use the backend name directly (Dropbox* db = new Dropbox(); ) instead of taking a string, enumerate or something like that? If QCloud is going to offer a common interface (a-la libcloud, jclouds, fog, etc), then hardcoding the classname favors code duplication - Examples? (apart from the tests) On Tue, Oct 9, 2012 at 9:20 PM, Weng Xuetian <wen...@gmail.com> wrote: > Hi KDE world, > Well, I'm here asking for some help if anyone interested in one of my little > project: > https://github.com/csslayer/qcloud > > The main purpose of this little project is to provide a synchronization and > file accessing file interface for all online storage. > > It's still in very earily stage and still have lots of things to do. > > Here comes an simple architecture description of this. > https://docs.google.com/drawings/d/1HrGZpzUl3NwZlTmf7LiGgdMzpnXB952C09QafUARVks/edit > > BTW I still not decided whether to let this depends on KDE in order to make > more use of kio (currently kio integration is kinds of broken due to some > architecture problem). > > Any help and comments are welcome :) > > Regards > >>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe << > -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer) >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
