Thanks again. I still can't figure out why in the particular case of using the variable in the context of a path it does not work. When I type in the path name, it just works, but if I use a variable (that contains EXACTLY the same thing I typed) it does not. Isn't ckeditor doing its thing in both cases? I'm still confused, but now on a higher level :-)
Anyway, I hope we'll get a cleaner implementation of variables in the next version of Xerte. They come in very handy indeed. I've been using them to personalise my course (the "=..." syntax), e.g.:
Enter your first name and click the button: [=Name][+submit:OK]
.. works fine.
Come to think of it: another user story that you might consider is
persistent variables. I have been playing around with that a bit, and with some success. I wanted the personalisation that I just had wrought out of the learner to be persistent between sessions. So I wrote a snippet of code that I dropped in the Script container on the main LO page (the one where you define the theme). That code is run each time the LO is run. In my case the code tries to retrieve a cookie from the user's disk. If it finds it, the contents of that cookie are used to overwrite the contents of the Xerte variable. It works, but it's a bit iffy: I don't check the contents of the cookie (let alone sign it) for example, so perhaps the user might be able to fudge some Javacode in there and get it executed. And for now you can only have one persistent name, as I only store one username in one cookie. Also, to STORE the cookie, I'm relying on code that is executed on the page that follows the page that asks the user for his/her name (the next page), as I haven't figured out yet how to trigger my own code when the user presses the OK button. Currently there is a xenith event connected to that button, I'd like to insert my own code before or after that event ends, but am not sure how to do that. Yet.
I will probably work on it later on - but would welcome any suggestions :-)