To use apps developed with the Nexacro, an appropriate environment must be created on the user's devices. Certain files must be downloaded to the user environment. The process of establishing this environment and downloading files is called "deployment". Deployed files are managed automatically based upon the cache policy and are replaced with new files as necessary.
If you launch a Nexacro-based app (Nexacro app or Nexacro app for short) in web browsers running on the desktop computers or mobile devices, your device will need just HTML, JavaScript, CSS files from the web server to execute the app. In the Nexacro runtime environment (NRE), you need to download and install other modules. Detailed deployment processes may vary according to run environments.
Deployment Overview
To run Nexacro apps, you need several files. The deployed files for each execution environment are listed in the following table.
File | Contents | NRE | WRE |
|---|---|---|---|
Runtime engine | Runtime engine used to process scripts, memories and rendering | O | X |
Nexacro framework | Frameworks and component libraries (JavaScript) | O | O |
Code | Code converted as the result of generation (JavaScript, CSS) | O | O |
License | License file | O | O |
The most important feature of the NRE is its runtime engine. Frameworks, components and code are directly applicable to the web browser environment. By contrast, the NRE requires the distribution of the runtime engine appropriate to each operating environment.
You may feel that the deployment of the runtime engine is inconvenient. In many cases, however, users want connectivity with existing systems or need extended features that web browsers cannot provide. In those cases, the Nexacro runtime environment can meet their needs.
Nexacro offers its basic features no matter which version you use. However, extended features, such as device APIs and connectivity with external devices, may vary according to run environments.
Deployed Files
This section describes each distribution in detail.
Please refer to Alias Pathfor alias paths used by the Nexacro to set paths on the user's computer.
The of name of files and libraries listed herein may change depending on distribution updates.
The list of files generated may vary according to the deployment option.
Desktop NRE
Windows NRE
After distributing the Nexacro runtime engine, apps are called according to their execution types. Although the same contents are included, framework JavaScript files are not be downloaded from the server but are distributed by being included in library files of the DLL format.
Category | File | Description | Location |
|---|---|---|---|
Runtime Engine | v8.dll | V8 Script Engine Library | |
XMemLib.dll | Memory Management Library | ||
XBasicLib.dll | Base Libaray | ||
nexacrolib.dll | Platform & Render Engine Library | ||
nexacro.exe | Nexacro Executor | ||
Framework DLL | XFrameworkLib.dll | Framework API Library | |
Extend DLL Files | protocol adaptor dll | Network Protocol Adaptor | %UPDATE% |
External DLL | External DLLs | %UPDATE% | |
Runtime Config Files | nexacro.xml | Runtime Execution Environment File & UserProfile | %USERAPP% |
Log Files | nexacro_xxxxx.log | Log File | %USERAPP%\Log |
Launcher Download Files | splash.png | Splash Image File | %USERAPP% |
loadingimage.png | WaitCursor Image File | %USERAPP% | |
nexacro.ico | Application Icon File | %USERAPP% | |
globalvars.dat | Global Variable List File | %USERAPP% |
File names can vary according to engine versions and operating systems. The above table lists important files only.
macOS NRE
The macOS NRE requires separate packaging process. Firstly, you need to build an archive file based on the code converted through generation process. Then, make deployment files based on the archive file.
Category | File | Description | Packing |
|---|---|---|---|
macOS App Files | nexacroN.macOS.framework | macOS Library Framework | macOS App |
start_macos.json | macOS Archive Information | ||
localizable.strings | macOS Locale String Information | ||
Execute HTML | index.html | Hybrid Run Archive | |
Framework JS | Hybrid Engine Archive | ||
Component JS | Hybrid Engine Archive | ||
Resource Files | loadingimage.png | Hybrid Engine Archive | |
Theme File | theme_*.css | Hybrid Theme Archive | |
Application Files | Hybrid Application Archive |
Mobile NRE
Android NRE and iOS NRE
iOS/Android apps need separate packaging processes for the different operation systems. Archive files are created based on the code converted through generation process. Then, deployment files appropriate to each operating system are created.
Category | File | Description | Packing |
|---|---|---|---|
Android App Files | nexacro.aar | Android Archive | Android App |
start_android.json | Android Archive Information | ||
strings.xml | Android Locale String Information | ||
iOS App Files | nexacro.framework | iOS Library Framework | iOS App |
start_ios.json | iOS Archive Information | ||
localizable.strings | iOS Locale String Information | ||
Execute HTML | index.html | Run Archive | |
Framework JS | Engine Archive | ||
Component JS | Engine Archive | ||
Resource Files | loadingimage.png | Engine Archive | |
Theme File | theme_*.css | Theme Archive | |
Application Files | Application Archive |
WRE
This type of deployment directly loads all of the required files on the web browsers. It performs differently depending on web browser in use.
Category | File | Description | Location |
|---|---|---|---|
Execute HTML | index.html | %WEBDEPLOY PROJECT% | |
Framework JS | BasicObjs.js | %WEBDEPLOY FRAMEWORK% | |
SystemBase.js | System Utility | %WEBDEPLOY FRAMEWORK% | |
Platform.js | Platform Objects | %WEBDEPLOY FRAMEWORK% | |
CssObjs.js | Style Object | %WEBDEPLOY FRAMEWORK% | |
Error.js | Error Information | %WEBDEPLOY FRAMEWORK% | |
Component JS | CompBase.js | Component Base Module | %WEBDEPLOY COMPONENT% |
ComComp.js | Common Component Module | %WEBDEPLOY COMPONENT% | |
Grid.js | Grid Component Module | %WEBDEPLOY COMPONENT% | |
DeviceAPI.js | DeviceAPI Module | %WEBDEPLOY COMPONENT% | |
Resource Files | waitimage.gif | WaitCursor Image File | %WEBDEPLOY RESOURCE% |
Theme File | theme_*.css | Deployed Theme Source | %WEBDEPLOY THEME% |
Application Files | Deployed files that compose an Application | %WEBDEPLOY PROJECT% |
License
The license information is required to distribute the Nexacro apps to users and to use them. A warning message is displayed at the top of the app if a proper license information is not available.
Status | Explanation | Action |
|---|---|---|
No license | The licenseurl property value of the application object is not specified or the license file does not exist in that path | Error message displayed |
Product information mistmatch | The product information specified in the license is different | Error message displayed |
User information mismatch | The IP address specified in the license is different from the host IP address | Error message displayed |
Feature information mismatch | Use of features not permitted under the license | Error message displayed |
Execution environment mismatch | Use of execution environment not permitted under the license | Error message displayed |
Duration mismatch | Use before the start date specified in the license or after the expiration date | Error message displayed |
File tampered | License information changed without authorization | Error message displayed |
Communication error | Communication error while accessing licenseurl | Error message displayed |
The license is not checked in the following cases.
When running QuickView in Nexacro Studio
When the starting file path is a local file (file://)
When running on localhost (127.0.0.1)