notebookEntry files

[martindusinberre]

Hi Hendrik: although you've spotted that we need a separate notebookEntry file every time there's a reference to something being saved in the Notebook, at the moment you've set them up without a page reference. This may well crash the importer. Use this as a template instead (here I've set it up for your 1.2.1)

{ "id": null, "title": "Frederic's object", "page": "chapter1/1.2.1/page.json", "dialogResponse": null, "mail": null }

I've actually never worked out why we have fields for dialogResponse or mail, so don't worry about those for the time being! The key thing is having a field for the page, which should always be filled in to link to the page the Notebook entry should appear in. Otherwise the showInNotebook field in a textExercise file won't find anything when you enter the string "pageExit"

Please change this for 1.2.1 and then, using this as a template, add a similar notebookEntry1.json file for all other pages where you have textExercises linked to notebooks (so far as I can see, 1.4.1, 1.4.2, 1.4.3, 1.5.1, but I may have missed some).

[henokemp]

Well spotted! I think herein lies the bug and why you couldn't proceed after 1.2.0, like I've mentioned in #5. I will go over it.

[interrogator]

@martindusinberre you can format blocks of code using three backticks and the file format. If you wanted to achieve something like this:

{
"id": null,
"title": "Frederic's object",
"page": "chapter1/1.2.1/page.json",
"dialogResponse": null,
"mail": null
}

You would write out:

```json
{
"id": null,
"title": "Frederic's object",
"page": "chapter1/1.2.1/page.json",
"dialogResponse": null,
"mail": null
}

(With three backticks at the end of the code block too, which can't be shown here for technical reasons.)

This can make it much easier for others to read blocks of code-like stuff.