Hi everybody,
here are my testing notes for Chrome on PC and Safari on iPad iOS 8.1
Petra
Search results: 259
Hi David
Does the 'big buck bunny' mp4 file that comes with Adapt work in this situation? If so, and the mp4 file you have created does not, then that certainly suggests it's something to do with video encoding.
If the big buck bunny video doesn't play either, that suggests it might be a server problem - the first thing I usually check for is the mp4 mime-type being correctly set on the server.
Video is one of those things that seems like it should be simple but actually frequently ends up being a massive pain in the wotsit.
Although HTML5 video has greatly simplified how you actually add video into a page, it has generated plenty of other issues to go along with it - starting from the most basic problem of some browsers needing different video formats (Firefox on most non-Windows platforms doesn't support MP4 for example) to all kinds of small things, such as:
- the 'moov atom' being in the wrong place in the video file (https://stackoverflow.com/questions/5058917/mediaelement-js-flash-video-wont-play-until-fully-loaded)
- security/authentication applied at the server level stopping videos loading in iOS (but only for our client, not for us!!)
- a client's network blocking playback of videos via IE's standard HTML video player (yet same file would load fine using Flash-based video player)
- Firefox suddenly not loading .ogv files for videos served through Moodle, and then several days later suddenly working again... (possibly caused by a bug in a release of Firefox although the release notes claim there were no changes to video handling)
- Videos not playing in Android when served via Moodle because you have the Moodle setting 'only http cookies' enabled (https://tracker.moodle.org/browse/MDL-44849)
And plenty more which I can't recall offhand!
Oh I see, sorry I didn't realise you meant Chrome on iPad
To be honest, we've always struggled with getting that to work as well and - for that reason - generally state that only Safari on iOS is supported.
I'm not sure Chrome on iPad is even part of the list of browsers supported by Adapt.
One interesting point to note - Apple actually don't allow any HTML rendering engine other than the 'webkit' engine built into iOS. So, when you use a browser like Chrome on iOS, it's not actually Chrome - it's still effectively Safari, only with a different interface. And, on iOS7 and below, somewhat slower than the 'real' Safari.
Hey everyone,
Does anyone want to work on an Adaptive Learning Platform? Interested in taking Learning beyond Scorm? Already experienced in Adapt development? What about building a system that filters learning paths to the users knowledge? What about an Adapt offline course wrapper?
Appitierre are looking for some Adapt developers who can work with Adapt - building extensions, themes, menus and components. They should also understand node.js and how to build SPA's using both Backbone (frontend) and node.js (backend).
We're currently building an Adaptive Learning Platform and need some developers who can come into our team and help push our product. Built like Adapt's plugin architecture, our Platform enables our Partners/clients to build a system they want. We believe in possibilities not features.
This position is a 6 month contract with the view to becoming permanent. We're looking for developers who are proficient in:
- HTML
- LESS/CSS
- Javascript (both frontend & backend)
- Backbone.js, Underscore.js & Handlebars
- Understanding of accessiblity in HTML
- Git
- Testing - both frontend (CasperJS) & backend (mocha.js) with experience using Postman
- Performance of DOM rendering - including animation libraries like Velocity.js
- D3.js & Raphael.js
- Ability to design themes with either Sketch or Photoshop.
Understanding of iOS or Android development would be a very nice bonus. Half days on Fridays working on Capsules, our product to bring Learning for free for people who don't have internet access.
If you would like to join our team - please contact me on the email address below, including salary expectations, CV and examples of work:
daryl.hedley@appitierre.com
Thanks,
Daryl
The following search terms occur only in the HTML markup of this message: ios
Hi Matt,
Thanks for your help. The changes is this adapt-contrib-confidenceSlider.js has removed the error and feedback now appears on screen as planned.
The submit on the linked slider is still an issue and on page load we now get this message:
Error: This component already exists in your project
...ction(e,t){if(n.componentStore[e])throw Error("This component already exists in ...
|
Hi,
I felt it is timely to start a thread about the next release of the Adapt framework and give everyone an overview of where we are at. Our last full release was version 1.1.0 at the end of May 2014. We are now focused on the release of the next release of the Adapt framework.
To answer the first question many of you will have:
When will it be released?
Soon. Sorry to be so vague on this. We have been opening some major cans of worms and it has at times been difficult to get an overview of all the work that needed doing and all of the edge cases that needed considering. Thank you for bearing with us while this work is being carried out.
To remind everyone of the process:
- We are currently still developing and one particular issue (soft+hard resets) is still in in the specification stage. While a fair amount of work on this has been done, we found that the code may need refactoring for the best of the stability of the framework.
- Once development finishes, we will call a feature freeze and engage in a thorough test cycle. This will include supplying a test package and testing brief to the community. As issues are found and recorded, they will be dealt with as a priority by the core team and anyone who is helping. This part of the cycle lasts for around one month.
- The intention of leaving a month for a thorough test cycle is that developers of non-core-bundle plug-ins also have plenty of time to update them so that they work with the new version of the framework. As the number of releases increases, we also strongly encourage developers to supply metadata saying which version of the framework the plug-in works for.
- After this period, we make the official release, alongside release notes and documentation. At this point, we'll shout to the world and ask everyone to help us with that and get using the new framework version.
What will be in it?
The scope of official releases is what we call the 'core bundle' - i.e. the core Adapt framework, the CLI and the components and extensions packaged with the standard installation script for the framework. These are currently defined near the top of this document.
At this point, we are working on five big 'buckets'. These are:
- WAI AA Accessibility
- Right to left (RTL) compatibility (Thanks to the Kineo Israel team for doing this work!)
- Overhauled assessment and SCORM tracking (spoor extension) functionality*
- Preparation of the framework for compatibility with the authoring tool
- Known bugs + any other work done to date
*item number three is proving by far the biggest can of worms and also depends on resolving the soft/hard reset functionality discussed here.
Will this release work with previous version of the framework?
There has been some discussion over what this version should be called. The current thinking of the core team is that it includes many major changes and significant new functionality and should hence be called version 2.0 rather than version 1.2.
As per our standards document, we aim to make this backwards compatible. This means that JSON data for courses using standard Adapt framework v1.1 'core bundle' components should be 'transferrable' to the next (version 2.0) release. 'Transferrable' may include automatic conversion of the JSON data into changed formats (which may mean that the converted data can't then be used with v1.1 anymore). There will more more careful elaboration on this point in the release notes.
Please note backwards compatibility is an aim rather than a promise or guarantee. There are also many scenarios, which will require manual updates when upgrading. For example:
- Themes
- Non core bundle components (including components classed as 'contrib')
- Any customisations
When will the authoring tool be released?
I'm sure this is a burning question for those of you who are following our work here. I'm afraid there isn't a straight forward answer to this at this point but it looks like we're delayed and won't be releasing in 2014 after all. We are currently working on putting up a sandpit of where we have got to, to give the community access and a proper view of progress. We're also working on an assessment of the outstanding work which needs to be done before our v0.1 release and will report back in due course.
I hope this gives you an insight. Please don't hesitate to ask any questions or add comments. And thanks everyone for supporting us.
Sven
Hi Sven, I have a Vagrant box with Chef provisioning that works for developer setup. I was working on it last week. I'll try and get it pushed to the Github Repo this week.
Ryan
CentOS instructions would be great, it sounds like you are already planning it out though
Thanks, Dan. Great that you are taking this forward! As you mention, I think the priorities are Linux / Heroku for now but keen to hear from the community on what the requirements might be.
As an aside, please could you also include "setting up on a local development machine" in your documentation?
Thanks,
Sven
Hi,
I am putting together some documentation about deploying the authoring tool onto a server and wanted to get some feedback about which deployment scenarios we should support. By this I mean which servers you will want to host the authoring tool on.
There may be some limitations to what environment we can deploy to due to the authoring tool being a node.js application. So far we have been testing deployments on Heroku and various Linux distributions.
Any suggestions, preferences or requirements for authoring tool deployment scenarios would be most welcome.