Software Development Kit: Difference between revisions
mNo edit summary |
No edit summary |
||
Line 10: | Line 10: | ||
{{main|SDK (Python)}} | {{main|SDK (Python)}} | ||
The Python SDK is developed separately from the {{software}}, and from a user-perspective. It is geared towards simplified and scripted tooling. It consists of a single folder which can be imported as a module. | The Python SDK is developed separately from the {{software}}, and from a user-perspective. It is geared towards simplified and scripted tooling. It consists of a single folder which can be imported as a module. | ||
{{article end | |||
|seealso= | |||
* [[API]] | |||
}} |
Latest revision as of 07:52, 9 July 2024
The Tygron Platform offers an API, which allows external application to interact with it. This means that external tools, such as scripts and plugins, can be created to interact with the Tygron Platform. However, with the large amount of options available in the API, as well as the various states for the Tygron Platform can be in and the step in workflow, there's more to the development of such tools than just the direct function calls.
To facilitate interaction with the API, a Software Development Kit (or SDK) can be used. A Software Development Kit is additional software or code libraries which wrap the raw API calls into more manageable functions, as well as take care of some of the overhead associated with the communication and state-management.
Java
- Main article: SDK (Java)
The Java SDK is derived directly from the Tygron Platform source code and is developed in lockstep with the Tygron Platform itself. It includes both an importable .jar file, as well as source docs.
Python
- Main article: SDK (Python)
The Python SDK is developed separately from the Tygron Platform, and from a user-perspective. It is geared towards simplified and scripted tooling. It consists of a single folder which can be imported as a module.