NGCP-CSC Dashboard

The NGCP-CSC Dashboard is an application template for you to copy and adapt to suite your specific needs. While you can remove the files and folders that your application does not use, be sure to read below before deciding what can be deleted and what needs to be kept in source control.

The following files are all needed to build and load the application.

• "app.js" - The file that launches the application. This is primarily used to launch an instance of the NgcpCsc.Application class.
• "app.json" - The application descriptor which controls how the application is built and loaded.
• "index.html" - The default web page for this application. This can be customized in "app.json".
• "build.xml" - The entry point for Sencha Cmd to access the generated build script. This file is a place where you can hook into these processes and tune them. See the comments in that file for more information.
• ".sencha" - This (typically hidden) folder contains the generated build scripts and configuration files for the application. This folder is required in order to build the application but its content should not need to be edited in most cases. The content of this folder is updated by "sencha app upgrade".

These files can be ignored from source control as they are regenerated by the build process.

• "build" - This folder contain the output of the build. The generated CSS file, consolidated resources and concatenated JavaScript file are all stored in this folder.
• "bootstrap.*" - These files are generated by the build and watch commands to enable the application to load in "development mode".

Other Folders

Application Structure

This application is a Universal Application. The following folders contain the code, resources, etc. that are shared by both Classic and Modern build profiles.

app/                # Contains JavaScript code
    model/          # Data model classes
    view/           # Views as well as ViewModels and ViewControllers
    store/          # Data stores
    controller/     # Global / application-level controllers

overrides/          # JavaScript code that is automatically required

sass/
    etc/            # Misc Sass code (all.scss is imported by default)
    var/            # Sass variable and mixin declarations
    src/            # Sass rules

resources/          # Assets such as images, fonts, etc.

See the Sass readme for details on the "sass" folder.

The following additional directories are used to isolate code and other files that are toolkit-specific:

classic/                # Content specific to the classic toolkit
    src/
        model/          # Data model classes
        view/           # Views as well as ViewModels and ViewControllers
        store/          # Data stores
        controller/     # Global / application-level controllers

    overrides/          # JavaScript code that is automatically required

    sass/
        etc/            # Misc Sass code (all.scss is imported by default)
        var/            # Sass variable and mixin declarations
        src/            # Sass rules

    resources/          # Assets such as images, fonts, etc.

modern/                 # Content specific to the modern toolkit
    src/
        model/          # Data model classes
        view/           # Views as well as ViewModels and ViewControllers
        store/          # Data stores
        controller/     # Global / application-level controllers

    overrides/          # JavaScript code that is automatically required

    sass/
        etc/            # Misc Sass code (all.scss is imported by default)
        var/            # Sass variable and mixin declarations
        src/            # Sass rules

    resources/          # Assets such as images, fonts, etc.

Overrides

The contents of "overrides" folders are automatically required and included in builds. These should not be explicitly mentioned in "requires" or "uses" in code. This area is intended for overrides like these:

Ext.define('NgcpCsc.overrides.foo.Bar', {
    override: 'Ext.foo.Bar',
    ...
});

Such overrides, while automatically required, will only be included if their target class ("Ext.foo.Bar" in this case) is also required. This simplifies applying patches or extensions to other classes.

Build the app

Run from within app folder (Sencha CMD should be installed https://www.sencha.com/products/extjs/cmd-download/ ) :

sencha app build

The application manifest (app.json) is ingested and the minified app generated and placed in build/production folder.

The build consists of

• index.html containing the microloader (dynamic JS/CSS loader)
• toolkit (classic / modern) manifests: desktop/mobile specific configurations defined in the manifest
• /resources folder : extra resources copied from /resources in root folder
• /app folder
  • app.js : minified file containing codebase, framework and external libs as configured in manifest
  • /resources folder
    • framework resources
    • generated css

Run the app

sencha web start

makes the build available at localhost:1841

Watch changes

sencha app watch

watch for changes and performs a quick rebuild of the app

Further info about CMD http://docs.sencha.com/cmd/

and regarding ExtJS http://docs.sencha.com/extjs/6.2.0/

Tests

Install all Node.js dependencies in ngcp-csc/t/ with npm install.

Local

Make sure that selenium-server and the NGCP-CSC application is running.

npm test

Docker

Create and run Docker Image (see instructions inside the Dockerfile).

Inside docker:

cd /code && ./t/testrunner

RTC:engine integration

By default you will get a 404 NotFound for the file cdk-prod.js. Since both, the CSC panel and the RTC:engine are running under the same base url in production, the file will be available. But in your local development environment you need to put the file in the required path manually.

1. Checkout RTC:engine repository
2. Install dependencies

npm install

3. Run build command

npm run build-cdk

4. Copy file from build folder to CSC folder

cp /ngcp-rtcengine/built/client/cdk-prod.js /ngcp-csc/rtc/files/dist/