Skip Navigation

Development Languages and Technologies Overview

The Sabre Red 360 Software Development Kit supports Java code, SWT, HTML, Sabre Scribe, Java Swing, and JavaScript.

Note: On Sabre Red 360 and Sabre Red 360 Software Development Kit the Browser control mode used defaults to use the compatibility mode that matches the installed Internet Explorer version. This means, for instance, that some advance capabilities in HTML documents containing for example HTML5 canvas tags will not be shown properly, even if IE9 is installed on the machine. For more information on Eclipse browser support please visit this_web_page, or access the Sabre Red 360 Software Development Kit to validate rendering your Web Red App

  • Integration of HTML-based websites using a custom implementation of an editor. If you want to customize the browser, display more than a browser in an editor, or add complex business logic to handle the editor, you must write your own editor wrapper with Java code. When a website is integrated in your own editor, the website is a standalone tool with the following characteristics:

  • The website is embedded in an editor (or tab), and does not interact with other Red Apps in Sabre Red 360.

  • The website can be based on HTML.

On the server side, your website can be based on Java technologies, for example, servlets or JSP. Your website can also be based on other technologies, such as Microsoft .NET Framework or PHP. From the perspective of Red Apps, all of these technologies are HTML.

  • Integration of websites using default implementations of an editor and a view. Default implementations simplify running a website with a known URL. To use this functionality, add your URL and a single default editor or view class. The editor or view cannot be customized. Communications with other Red Apps and Sabre data stores is possible. Java code is not used for this simple alternative.

  • Website integration using JavaScript. If you are more familiar with JavaScript than Java, you can implement Event Listening and register Event Listeners with JavaScript. You can also use JavaScript to access OSGi whitelisted services without communications, and access SRWRuntime to use communications channels, such as host communications. Exposed OSGi services are called whitelisted services. They are exposed through a Java-to-JavaScript bridge (JS bridge). Additionally, you can register JavaScript functions as services.

  • Sabre Scribe scripts. You can wrap your compiled Sabre Scribe script files as plug-ins for Sabre Red 360. The wrapping of a Sabre Scribe script does not change the functionality of the script, but instead, it improves the deployment and version control of the scripts.

Sabre Scribe scripts can also read to or write from files in a plug-in, and update files when you have a new version of your plug-in. In addition, you can secure your scripts from unauthorized use when you create your bundle. It is also possible to add active listening for commands to trigger a Sabre Scribe script.

  • Swing apps. Your Swing apps can be wrapped as plug-ins. The Swing API enables developers to create desktop and internet applications. This API consists of GUI components and services.