I've updated the ios-scrollfix readme and the example branch on trickle so that it reads correctly.

The patch instructions we correct, they just weren't clear.

By 'have a launch page' do you mean that when the learner clicked on the course title in the LMS it would launch, say, 'launch.html' (this would be set in the manifest file) and then that launch page would have a launch button linked to Adapt's index_lms.html?

Pretty much, yes. It actually tries to open Adapt's index_lms.html automatically. The link to do so is there as a fallback in case of popup blockers. There's an example here.

I also see there's adapt-launchNewWindow extension. Haven't had a chance to try it yet but does that do something similar?

Yes it does and quite frankly I would go for this option.

Finally, I looked at iOS-scrollFix this morning and it requires a patch in Trickle's .js and LESS files. Those Trickle files seem to have been completely re-written subsequently so the patch instructions are out of date and unuseable.

Which patch instructions?

Hi Ollie,

By 'have a launch page' do you mean that when the learner clicked on the course title in the LMS it would launch, say, 'launch.html' (this would be set in the manifest file) and then that launch page would have a launch button linked to Adapt's index_lms.html?

I also see there's adapt-launchNewWindow extension. Haven't had a chance to try it yet but does that do something similar?

Also, for anyone else who winds up in this thread there are a couple of related threads here and here which are very insightful. It seems Kallidus also uses an iframe, so the issue could be quite widespread.

Finally, I looked at iOS-scrollFix this morning and it requires a patch in Trickle's .js and LESS files. Those Trickle files seem to have been completely re-written subsequently so the patch instructions are out of date and unuseable.

Cheers,

Chris

I think it depends on the technical ability of the person building the course.

Anyone who's comfortable with editing JSON and doing basic HTML formatting might well find the Framework easier. Those who aren't will be more comfortable with the Authoring Tool.

You will be able to use the Trickle extension with the Authoring Tool.

There are some areas where using the Authoring Tool can be harder.. for example, say you want to have Trickle configuration that is different from the default... in the Authoring Tool you'll have to set this up each time. If using the Framework you can just copy-and-paste the settings. This is a known issue.

Best thing is just for you to give each a try and see for yourself. The Framework is very easy to get up and running if you follow these instructions. The Authoring Tool is harder to install - but some of the involved companies provide free trials you can use, canstudios have one for example.

What I will say is that if you want to develop new functionality for Adapt you're definitely better off doing that in the Framework, even if you are developing plugins to be used in courses built in the Authoring Tool. Get them working in the framework first then upload into the Authoring Tool and and make sure they work in there. Suspect the same thing applies to theming too...

Hi

I don't know if it helps, but we just launched a service for Adapt Authoring tool. You can get an instant trial here... https://canstudios.com/adapt-authoring-tool/

Regards,

Paul

https://github.com/cgkineo/adapt-iOSScrollFix

Possibly you were not testing within an iFrame previously and now are?

I believe there is an extension that may help improve the responsiveness when viewing on an IOS device but can't recall the name of it.

As always, thank you for your response AND for pointing that out! Good to know, thank you.

Hi Joe

That module must be a very old version of Adapt because that meta tag was removed back in June 2015.

I suggest you remove it from your course too.