I would suggest getting rid of the config.json file as well as reliance on directories full of images. It seems to me that the config file can simply be replaced by functional interface. Also, I don't think the arguments to those function should be directories. The API should not care where image data is retrieved from.
I think a more intuitive and generic API would look something like.
I would suggest getting rid of the config.json file as well as reliance on directories full of images. It seems to me that the config file can simply be replaced by functional interface. Also, I don't think the arguments to those function should be directories. The API should not care where image data is retrieved from.
I think a more intuitive and generic API would look something like.
img1 = open("/path/to/file.jpg") img2 = open("/path/to/file2.jpg") c = PCloudCv() c.stitch(img1,img2, callback=onCompletion) c.detect(img1,callback=onCompletion)
Generally, what I am suggesting is that the API use functions, that take python object and return python objects.
Also you might consider looking at picloud, to see how their python API works with async jobs http://docs.picloud.com/primer.html#creating-a-job-from-python .