CBL webapps

Running live changes

Each frontend Sencha application needs to be built at least once with the Sencha CMD build tool to scaffold/update a set of loader files. After that, you can just edit files the working tree and reload the browser. The two exceptions where you need to build again are changing the list of packages or changing the list of override files.

There is a shortcut studio command for building each frontend application:

• build-enroll-admin
• build-demos-teacher
• build-demos-student
• build-tasks-manager
• build-tasks-teacher
• build-tasks-student

Once built, the live-editable version of each app can be accessed via the static web server that the studio runs on port 2191. The backend host must be provided to the apps via the ?apiHost query parameter. Any remote backend with CORS enabled will work, or you can use the local backend:

• localhost:2191/SlateStudentCompetenciesAdmin/?apiHost=localhost:2190
• localhost:2191/SlateDemonstrationsTeacher/?apiHost=localhost:2190
• localhost:2191/SlateDemonstrationsStudent/?apiHost=localhost:2190
• localhost:2191/SlateTasksManager/?apiHost=localhost:2190
• localhost:2191/SlateTasksTeacher/?apiHost=localhost:2190
• localhost:2191/SlateTasksStudent/?apiHost=localhost:2190

Working with breakpoints

By default, the Sencha framework will automatically append random cache buster values to every loaded .js source. This helps ensures that your latest code always runs, but will also prevent any breakpoints you set from persisting across reloads.

With the Disable cache option of the network inspector activated, you can disable this built-in cache buster by appending &cache=1 to the current page’s query string.

Connecting to remote server

You can connect to any remote slate-cbl instance that has CORS enabled by appending the query parameter apiHost when loading the page. If the remote instance requires HTTPS, append apiSSL=1 as well.