Development
- Stephan Böhmig
- Agathe Saunier (Unlicensed)
Beebox is a translation software that was built by developers for developers. We know how hard it can be to integrate third party products or libraries. We want to make your life as easy as possible. In this chapter we outline the multiple means to interface with Beebox. Choose the options that you feel most comfortable with.
If you are new to the Beebox you might first want to read the Developer Introduction.
| Integration.Option................ | How it works |
|---|---|
| File Copy | If you know how to copy files from one place to another then you are ready to use this mechanism |
Restful Web API | The Beebox exposes a Restful Web API. You can control any aspect of a Beebox project including sending files to translate, poll translation status, receive translations, etc. The main 6 to 10 methods are sufficient for most integration scenarios. By default, the API listens on port 8089. |
Web Callbacks | You can configure Beebox to call a web URL with any important events. For example, Beebox can notify your systems when a file was translated and saved to the “OUT” directory. The callback mechanism makes it unnecessary to poll Beebox at regular intervals in order to know whether translations have arrived. |
Powershell Scripts | PowerShell scripts are another mechanism that will prove to be beneficial in certain integration scenarios. You can develop a script that is automatically executed by the Beebox whenever new files to translate are received and whenever files have been translated. |
Microsoft.Net Extensions | Extend Beebox functionality using c# and Visual Studio. You can code translation algorithms, custom filters and more, and upload your code to a Beebox. |
To learn the basic Beebox concepts now please go here: Developer Introduction
Continue reading:
Copyright Wordbee - Buzzin' Outside the Box since 2008