Hi Andras,
Thanks so much for the link. This is exactly what I was looking for and also looks much preferable to using Bootstrap tours as well. I've been playing around with it, but so far am experiencing some weird issues. Using infoBox() in ui.R works great. But in my case I need to do it all in server.R by passing the steps option in the intorjs() options list, like in the second example on the repo page. This allows me to use the position option in the reactive data frame, steps(), for each step as well as more dynamic content. It also keeps ui.R much cleaner if it is a big app that would be littered with many introBox() calls.
I haven't posted an issue on github yet because I haven't reproduced a simple example. But what I am seeing happening is a couple dynamically generated steps display fine and many more tour steps display in the far top left corner of the screen, or sometimes in the top left of some other panel- but nowhere near the input or output whose ID is referenced. When I inspect the page in my browser, it looks like using infoBox() in ui.R properly inserts the correct div around the browser element so that introjs() can display the step near the element. But the same step if passed to the steps option list in server.R, will not insert a div at all, leading to the intro text box showing up somewhere else, usually the corner of the screen.
If I can come up with a small reproducible example, I'll share here and post a github issue, but for now I'm not sure what is really happening. I would love to pass a nice, clean set of vectors of element and intro in server.R and not insert a ton of infoBox() calls in ui.R, but it seems like at least for now that may be the only option. I haven't found any references online to people having a similar issue so I could be using introjs() incorrectly somehow.
Regards,
Matt