Difference between revisions of "Globalyzer Lite for Developers"
(→Typical Deployment) |
(→Typical Workflow) |
||
| Line 11: | Line 11: | ||
= Typical Workflow= |
= Typical Workflow= |
||
| − | The developer uses Lite within the IDE to: |
+ | The developer uses [[Terms_and_Definitions|Globalyzer Lite]] within the IDE to: |
| − | * Scan the code being worked on for potential i18n issues before checking in the code to the source code repository |
+ | * [[Terms_and_Definitions|Scan]] the code being worked on for potential [[Terms_and_Definitions|i18n]] issues before checking in the code to the source code [[Terms_and_Definitions|repository]] |
* Refactor the code based on the checks |
* Refactor the code based on the checks |
||
| − | * Push that code to the repository |
+ | * Push that code to the [[Terms_and_Definitions|repository]] |
| − | This requires the rule sets used to scan the code have been vetted and the Globalyzer |
+ | This requires the [[Terms_and_Definitions|rule sets]] used to [[Terms_and_Definitions|scan]] the code have been vetted and the [[Terms_and_Definitions|Globalyzer Lite Project Definition file]] makes sense. |
= Installation Note = |
= Installation Note = |
||
Revision as of 00:52, 22 December 2016
Introduction
Globalyzer Lite can be integrated into a developer's IDE (Integrated Development Environment). It allows i18n scanning of a project based on a Globalyzer Lite Project Definition file, most likely at the top level directory of the source code, so that developers can check their code before pushing it to the main repository. It does not have the power features of Workbench, but can be used entirely within developers' IDEs. This makes it easy for developers to check code for i18n candidate issues.
Target User
The typical Globalyzer Lite user is a developer working on a global market application.
Typical Deployment
Globalyzer Lite has been unzipped on the software developer's desktop and configured as an external tool in their IDE. The source code has a Globalyzer Lite Project Definition file at the top level directory which specifies how the code should be scanned. The developer's desktop has access to the Globalyzer Server.
Typical Workflow
The developer uses Globalyzer Lite within the IDE to:
- Scan the code being worked on for potential i18n issues before checking in the code to the source code repository
- Refactor the code based on the checks
- Push that code to the repository
This requires the rule sets used to scan the code have been vetted and the Globalyzer Lite Project Definition file makes sense.
Installation Note
To install Globalyzer Lite, you must have access to a the zip file for Lite. The installation is a question of unzipping the zip file and executing the lite-setup script. To configure Globalyzer Lite, you then need to look at the globalyzer.com help page for Lite, globalyzer-lite-IDE-usage.html.
