Nice, like a future's "value" getter.
Cheers,
_
Nice, like a future's "value" getter.
Cheers,
_
There are certainly similarities. DropboxTask essentially can be described as typed representation of Json QNetworkReply data, something:
(Reply -> Json) -> (t, e)
where 't' is result type and 'e' is exception type, DropboxException derived.
On other note, we started something similar to dropboxQt for a subset of Google API - gdrive, gmail, gtask.
https://github.com/osoftteam/googleQt
Now we can compare both APIs. Dropbox at the low level (the endpoint of all routes) consists of 3 functions while Google of 1 function. It is possible to build Dropbox API on top of 1 function as well (dropbox API is even more consistent) but it was never objective. We found fascinating that all wrapper classes can be generated out of some declarative language (STONE), in case of Dropbox all Arguments, Results and Routes are generated, in case of Google Arguments are manually written and the rest generated.
2 anda_skoa - thank for your suggestions, it really helped to shape up the async stuff.
Bookmarks