lams-github / lams_build / conf / whiteboard

scripts

Clone Tools

Stats

Commits this week: 0
Total Committers: 2
Last Commit:
Commits this week: 0

Lines of code count not available

Commit Activity

Commits By Day In Week
52 week commits volume
Commits By Day In Week
Commits by day
Commits By Day In Week
Commits by hour
Commits By Hour In Day
Commit calendar
 

Most active committers (90 days)

loading
loading
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Tuesday 11 May 2021
6:57 am

Marcin Cieslak

LDEV-5204 Introduce imageURL config property

In vanilla Whiteboard all images are prefixed with current server URL.

If we move Whiteboard or export & import data, it will not work.

Now images have relative URL prefixed with whatever is in imageURL.

Options
    • -0
    • +105
    ./config/config-schema.json
  2. … 4 more files in changeset.
Monday 10 May 2021
3:32 pm

Marcin Cieslak

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.

Options
    • -2
    • +31
    ./s_whiteboard.js
    • -2
    • +17
    ./server-backend.js
  3. … 1 more file in changeset.
1:52 pm

Marcin Cieslak

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.

Options
    • -37
    • +58
    ./s_whiteboard.js
Sunday 02 May 2021
5:51 pm

Marcin Cieslak

LDEV-5204 Add Whiteboard tool content export and import

Options
    • -0
    • +9
    ./s_whiteboard.js
    • -0
    • +27
    ./server-backend.js
  3. … 3 more files in changeset.
5:08 pm

Marcin Cieslak

LDEV-5204 Fix image upload in Whiteboard

Options
    • -1
    • +1
    ./server-backend.js
10:36 am

Marcin Cieslak

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.

Options
    • -0
    • +140
    ./s_whiteboard.js
    • -0
    • +16
    ./server-backend.js
  3. … 11 more files in changeset.
Friday 30 Apr 2021
6:12 pm

Marcin Cieslak

LDEV-5204 Introduce improved security using hashing

In vanilla Whiteboard a global access token is configured on server and

must be present in all requests made to Whiteboard. It means that anyone

can modify any whiteboard ID (wid).

In LAMS we introduce a hash of wid + accesstoken. Users do not know

access token, so they can not generate the hash for another wid.

The hash is simple Java hashCode() function, sufficient for this

situation.

The hash does not include author name as it is not present in many use

cases.

The hash optionally has a different form: source wid + wid +

accesstoken. It is when copyfromwid parameter is present. In this case

the target canvas is using standard wid and hash, but for the extra call

to source canvas we use source wid and the modified hash. This modified

hash is only usable to copy content from this particular source wid to

this particular target wid, so users can not use the hash to draw on the

source canvas.

Options
    • -0
    • +403
    ./server-backend.js
  2. … 9 more files in changeset.
Friday 23 Apr 2021
12:07 pm

Marcin Cieslak

LDEV-5204 Set default port to 9003

Options
    • -0
    • +32
    ./server.js