You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't quite understand what do you mean by "better existing model to use for implementing a Seafile plugin". Do you want to add support for Seafile service to Cloud plugin -or- do you want to create a new plugin with support for Seafile? Can you please explain this a bit more?
Hello,
the idea is to add Seafile support to the cloud plugin.
Looking at the code in blocktype/, i see that most of the code is duplicated between different cloud modules. So as far as I understand, adding support for a new cloud system consists in copying one of the existing modules and adjusting it for the API. So my question is : looking at Seafile API, what is the best existing base for implementing it ?
By quickly looking through Web API v2.1 I probably would start with ownCloud implementation and would also implement the method for getting the auth token. I would borrow and change/update that piece of code from some other blocktype. This probably means implementing/adapting the "access_token" method (and/or if it is necessary also the "request_token" method).
Hello,
Seafile is a very powerful open source cloud service. It offers an API for accessing the service : http://manual.seafile.com/develop/web_api_v2.1.html, or a webdav access.
Can you advise me about the better existing model to use for implementing a Seafile plugin ?
Thanks
The text was updated successfully, but these errors were encountered: