In this section, we will discuss the layout and directory structure of the Basic Application tutorial.
Introduction to JS Development Environment
As mentioned in the previous section, HOOPS Communicator ships with a Node.js server, which will serve up the samples included in the package.
In your installation directory for HOOPS Communicator, we have provided a library of sample code that corresponds to tutorials in this documentation. There is a directory named basic_app that holds all of the starting files you need to start this tutorial. You will find other directories with names that correspond to the tutorials listed in the sidebar to the left under Tutorials.
<HC_installation_root> ├── tutorials │ ├── basic_app │ │ ├── index.html │ │ ├── start_server.[bat|sh] │ │ ├── server_config.js │ │ ├── js │ │ │ └── hoops
Let’s take a closer look at the contents of the basic_app directory.
start_server.[bat|sh] – This script will start the same HOOPS Server used in Getting Started, but slightly modified to serve the files from this project.
server_config.js – This file contains the HOOPS Server configuration.
<HC_installation_root> └── web_viewer ├── src │ └── js │ ├── engine-asmjs.js │ ├── engine-wasm.js │ ├── engine.wasm │ └── hoops_web_viewer.js └── typescript ├── hoops_web_viewer.d.ts └── tcc.d.ts
The file hoops_web_viewer.js contains the core functionality of the HOOPS Web Viewer component and has dependencies on engine-asmjs.js, engine-wasm.js, engine.wasm. Copy all these files into /js/hoops of your project. To keep things simple, we will not use the HOOPS Web Viewer UI for this tutorial.