Difference between revisions of "Globalyzer API for Continuous Globalization"
(→Typical Workflow) |
(→Introduction) |
||
| Line 1: | Line 1: | ||
= Introduction = |
= Introduction = |
||
| − | Globalyzer API allows |
+ | [[Terms_and_Definitions|Globalyzer API]] allows organizations to write their own logic in Java around [[Terms_and_Definitions|scanning]] code for [[Terms_and_Definitions|i18n]] issues detection; The wrapping program can then be deployed on a [[Terms_and_Definitions|Continuous Globalization]] system. It allows i18n scanning of source code with all the flexibility and power of Java. For instance, the Java wrapper logic can decide what is to be scanned, with what rule set, and how to consume the results. |
| + | |||
| + | This approach is more powerful than using either [[Terms_and_Definitions|Globalyzer Command Line Interface]] or [[Terms_and_Definitions|Globalyzer Lite]]. It does require writing Java code. |
||
| − | This approach is more powerful than using either Globalyzer Command Line Interface or Globalyzer Lite. It does require writing Java code. |
||
= Target User= |
= Target User= |
||
The wrapper application writer will decide who is the target user. |
The wrapper application writer will decide who is the target user. |
||
Revision as of 18:55, 22 December 2016
Introduction
Globalyzer API allows organizations to write their own logic in Java around scanning code for i18n issues detection; The wrapping program can then be deployed on a Continuous Globalization system. It allows i18n scanning of source code with all the flexibility and power of Java. For instance, the Java wrapper logic can decide what is to be scanned, with what rule set, and how to consume the results.
This approach is more powerful than using either Globalyzer Command Line Interface or Globalyzer Lite. It does require writing Java code.
Target User
The wrapper application writer will decide who is the target user.
The typical Globalyzer Lite actor is a Continuous Integration system which automates the tasks of scanning source code.
Typical Deployment
The wrapper code on top of Globalyzer API will be deployed as per the Java application.
Note: If you add LRM to this picture, the Continuous Globalization system needs to be a Linux machine, preferably Ubuntu.
Typical Workflow
The workflow will be determined by the Continuous Integration system and the written application on top of Globalyzer API.
This requires that the rule sets used to scan the code have been vetted.
Installation Notes
To install the API, login to the Globalyzer server, download the Globalyzer Client installer for the platform you are running on, and run the installer. You will then write a Java program calling the API calls as described on the Globalyzer help pages under help/referenceAPI/toc.html .
