9 Replies
Michael Hinze

Hi Cheng, A quick Google search reveals a number of Javascripts and libraries that could be used to take a screenshot. Here is just one of several: http://html2canvas.hertzen.com/

So, taking a screenshot from within Storyline seems like a real possibility. My question would be: AND THEN WHAT? What do you want to use the screenshot for? Save it? (If yes, where; on the client side or server?) Display it? Print it?

It seems to me that getting a screenshot would only be the first step in what may turn into quite a development project.

Phil Mayor

Michael Hinze said:

Hi Cheng, A quick Google search reveals a number of Javascripts and libraries that could be used to take a screenshot. Here is just one of several: http://html2canvas.hertzen.com/

So, taking a screenshot from within Storyline seems like a real possibility. My question would be: AND THEN WHAT? What do you want to use the screenshot for? Save it? (If yes, where; on the client side or server?) Display it? Print it?

It seems to me that getting a screenshot would only be the first step in what may turn into quite a development project.


Agree with Michael getting the screenshot is simple (ash the user to press the print screen button?).  What then?  Storyline cannot import it, it could show it a s a web object.

Cheng Li

Michael Hinze said:

Hi Cheng, A quick Google search reveals a number of Javascripts and libraries that could be used to take a screenshot. Here is just one of several: http://html2canvas.hertzen.com/

So, taking a screenshot from within Storyline seems like a real possibility. My question would be: AND THEN WHAT? What do you want to use the screenshot for? Save it? (If yes, where; on the client side or server?) Display it? Print it?

It seems to me that getting a screenshot would only be the first step in what may turn into quite a development project.


Hi Michael,

One project that I am working on right now has a large audience, most of them are remote and they do not have much experience with Storyline and e-Learning. While they are taking my training/course, I would like to have a function in my course that allows them to take screenshots where they have trouble with. Troubles can be either technical or training content related. This way I can directly know what trouble they are facing with. 

I agree with you that screenshot might be only the first step. My second thought was after evaluating how hard this function is to be built, is it worthy devoting time to do this? I might need to talk with my clients and look for a way around. 

Thanks. I appreciate your input. 

Cheng

Michael Hinze

Cheng Li said:

Michael Hinze said:

Hi Cheng, A quick Google search reveals a number of Javascripts and libraries that could be used to take a screenshot. Here is just one of several: http://html2canvas.hertzen.com/

So, taking a screenshot from within Storyline seems like a real possibility. My question would be: AND THEN WHAT? What do you want to use the screenshot for? Save it? (If yes, where; on the client side or server?) Display it? Print it?

It seems to me that getting a screenshot would only be the first step in what may turn into quite a development project.


Hi Michael,

One project that I am working on right now has a large audience, most of them are remote and they do not have much experience with Storyline and e-Learning. While they are taking my training/course, I would like to have a function in my course that allows them to take screenshots where they have trouble with. Troubles can be either technical or training content related. This way I can directly know what trouble they are facing with. 

I agree with you that screenshot might be only the first step. My second thought was after evaluating how hard this function is to be built, is it worthy devoting time to do this? I might need to talk with my clients and look for a way around. 

Thanks. I appreciate your input. 

Cheng


This may be too simplistic, but before considering any custom development, I would simply add a slideNo  to the project and ask reviewers and/or learners to include it in their problem reports. It's not like a screenshot would completely eliminate the need for users to provide a text description of the problem they encountered, especially for content-related issues.