s_whiteboard.js

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
LDEV-5362 Upgrade Whiteboard to version 1.7 (2023-02-10)

  1. … 8 more files in changeset.
LDEV-5204, UMAN-16 After load prefix author so steps can not be undone

  1. … 1 more file in changeset.
LDEV-5204 Adjust LAMS customisations for latest Whiteboard code

  1. … 8 more files in changeset.
LDEV-5204 Embed images when exporting Whiteboard canvas

In vanilla Whiteboard images are referenced by absolute URLs. If we

upload content to another LAMS instance with a different URL, images

will not be found.

Now when exporting a LAMS LD we embed Whiteboard image base64 data

directly in tool exported XML. When we import the LD, we check if image

already exists on the server. If it does not, we recreate it from the

exported data.

  1. … 2 more files in changeset.
LDEV-5204 Use separate file for each saved Whiteboard canvas

In original version all canvases were stored in a single JSON file. The

file would grow indefinitely. It would have to be stored in memory

whole. If it got corrupted, all canvases' data would be lost.

For all these reason now we store each canvas in its own file in

savedBoards/<whiteboard ID>.json

Each file is loaded only when corresponding canvas is used.

We can easily later do clean up - delete files which have not be used

for a year or so.

When doing a LAMS back up, the whole /savedBoards directory needs to be

backe up.

LDEV-5204 Add Whiteboard tool content export and import

  1. … 4 more files in changeset.
LDEV-5204 Initiate canvas copy on tool content copy on back-end

In previous version canvas was copied when an user opened it. Sometimes

in LAMS we copy content without opening a canvas. For example when using

Save As or Copy buttons in Authoring. We had to make sure that canvas is

always either copied on back-end or it gets opened and copied via

front-end.

    • -0
    • +140
    ./s_whiteboard.js
  1. … 12 more files in changeset.