Picture of Dan Jonsson
WebObject and progress
by Dan Jonsson - Monday, 30 November 2015, 1:08 PM
 

I don´t get any progress report in Adapt on the webObject component.

Is there anything I should add to the code to get this?

This is mainly the progress inside the chapter and on the mainmenu page.

 

Danne/

 

Picture of Niall Deighan
Re: WebObject and progress
by Niall Deighan - Monday, 30 November 2015, 1:58 PM
 

Hi Dan,

Do you mean that there is no entry for the webObject on the menu in the drawer? Adding the "page-level-progress" to the component has enabled me to see it in the menu.

"_pageLevelProgress": {
     "_isEnabled": true,
     "_isOptional": false
}

Picture of Dan Jonsson
Re: WebObject and progress
by Dan Jonsson - Monday, 30 November 2015, 2:47 PM
 

You are right it shows up in the menu and is clickable but it dosen´t register any progress!

And I have tried to add the _pageLevelProgress code with no result!

 

D

Picture of Niall Deighan
Re: WebObject and progress
by Niall Deighan - Monday, 30 November 2015, 3:25 PM
 

Ok, I think then it's not setting completion status. Whatever html content you're putting into the webObject needs to set a variable that the webObject is listening for so it can then set the completion status as 'Complete'.

Try adding,

parent.triggerVar=1;

to your html/js content.

Picture of Dan Jonsson
Re: WebObject and progress
by Dan Jonsson - Tuesday, 1 December 2015, 7:44 AM
 

I´ll try adding the_isOptional parameter.

Thanks!

D

Picture of Dan Jonsson
Re: WebObject and progress
by Dan Jonsson - Tuesday, 1 December 2015, 7:55 AM
 

I´m using the webObject component, wonder why it dosen´t connect with the _pageLevelProgress?

 

D

Picture of Paul MacIntyre
Re: WebObject and progress
by Paul MacIntyre - Tuesday, 1 December 2015, 8:43 AM
 

Hi Dan

The webObject component was written with the idea that content shouldn't be considered complete just because it has been loaded. With any of the other plugins for adapt that could handle html5 content, as soon as the page loaded, the section was considered to be complete. The only way around this is to have a component that will listen to the content for a sign that it is done. The webObject listens out for a variable called parent.triggerVar, and when this is equal to 1, the completion status is set. This means that if you are using trickle, trickle will not fire until this condition has been met. It also means that the content will not be marked as complete until this condition has been met.

If you include a simple piece of javascript at the end of your html5 piece that sets parent.triggerVar = 1, then both should fire fine (by the way, in case you're not used to javascript, this is vase sensitive).

Hope this helps

Paul

Picture of Dan Jonsson
Re: WebObject and progress
by Dan Jonsson - Tuesday, 1 December 2015, 9:40 AM
 

Yes, I think this a awesome idea!

Just keep it that way.

Now I´m using it as an vimeo player for the movies I want to connect from the web.

It´s just a vimeocode. Perhaps there is possible to add the javascript at the end of the url!?

 

D

Picture of Matt Leathes
Re: WebObject and progress
by Matt Leathes - Tuesday, 1 December 2015, 4:52 PM
 

Note sure if this helps - but we recently updated contrib-media to have much better support for Vimeo videos... including only marking the component as completed when the video reaches the end.

Picture of Dan Jonsson
Re: WebObject and progress
by Dan Jonsson - Wednesday, 2 December 2015, 7:44 AM
 

Thanks I´ll try this!

Do I have to reinstall the component or just swap the files?

 

D

Picture of Dan Jonsson
Re: WebObject and progress
by Dan Jonsson - Wednesday, 2 December 2015, 9:39 AM
 

Now I know, it works just fine!

Had to swap the component!

Thanks!

Danne/