Milovana.com

kerkersklave wrote: Mon Sep 30, 2024 12:55 pm Do you mean something like that: https://milovana.com/webteases/showteas ... d7eb3516cb
I made the example for 5 tasks, but it should be easy enough to scale up to 25.

Get source-code: https://milovana.com/webteases/geteossc ... d7eb3516cb

PlayfulGuy wrote: Tue Oct 01, 2024 2:55 pm You could even add a function to the init module like recordTask(name, page) to build two lists, one that holds the task name and the other the name of the page that implements that task. Then you just step through the list of page names going to the next one in sequence to perform the tasks.

var taskToPage = {"task 1": "pageSomething", "task 2": "pageWhatever"}

taskToPage["task 1"]

kerkersklave wrote: Wed Oct 02, 2024 4:55 pm

PlayfulGuy wrote: Tue Oct 01, 2024 2:55 pm You could even add a function to the init module like recordTask(name, page) to build two lists, one that holds the task name and the other the name of the page that implements that task. Then you just step through the list of page names going to the next one in sequence to perform the tasks.

Not sure what you want exactly. After the choice-step you've got a list currentChoices of the names of tasks. Do you want to use the goto-Action with a dynamic page name to go through the tasks? So you need a mapping from task names to page names, as you do not want to use the same name for both? In Javascript you can define a mapping like this:

Code: Select all

var taskToPage = {"task 1": "pageSomething", "task 2": "pageWhatever"}

and then look it up like this:

Code: Select all

taskToPage["task 1"]