This page captures notes on the directory structure of the GUI client-side code.

Structure Overview

The following illustrates the directory structure:

webapp
+-- app
| +-- fw
| | +-- layer
| | +-- mast
| | +-- nav
| | +-- remote
| | +-- svg
| | +-- util
| | +-- widget
| |
| +-- view
| +-- device
| +-- sample
| +-- topo
|
+-- data
| +-- img
| +-- map
|
+-- tests
| +-- app
| | +-- fw
| | | +...
| | +-- view
| | | +...
| | +...
| +-- e2e
|
+-- tp
|
+-- WEB-INF
 

app directory

The app directory contains subdirectories

app / fw directory

The fw subdirectory contains the following subdirectories, providing a number of categories of functionality:

app / view directory

The view subdirectory contains a subdirectory for each implemented view.

For example, topo contains the code implementing the Topology View.

data directory

The data directory contains subdirectories for static data files

tests directory

The tests directory contains karma / jasmine unit tests and end-to-end (scenario) tests for javascript modules.

tp directory

The tp directory contains third-party code, such as AngularJS, D3, jquery, topojson, etc. 

WEB-INF directory

The WEB-INF directory contains the web.xml file for configuring the web bundle.