Understanding Storyline 360 vs 3 published zips
We are working on the Flash end-of-life and having to go back through thousands of Storyline published zip files to see if they contain Flash (swf or flv files). We also have packages created by other tools as well.
We've been developing a package sniffer to look inside the zips and check for any "flashy" files and also decode the tool and version used to create the course.
We've found that on our LMS and in our corporate environment HTML5-only from Storyline 3.18+ seem to work the best. (We still have a lot of users on IE11.) We want to scan the zip and then either give the package a fail/warning/pass. So for example something like this.
- SL2 Flash: FAIL (because of .swfs)
- SL2 dual publish: FAIL (because not supported by IE11 without Flash)
- SL 360 html5 only: If the build version is 18+ give it a PASS, if not then a WARNING that it should be carefully checked.
We've got most of this working, but SL3 and SL360 both report with versions/build numbers 3.x.
I've checked the version histories for SL3 and SL360 and can't see an easy (and future proof) way to tell if a package that reports as "Articulate Storyline 3.5" is published by someone using an old version of SL360 or an up-to-date version of SL3.
We could build a lookup list based on the current release history and the more detailed build numbers, but that would require updating every time there is an update to SL.
Is there some way to tell the difference between SL3 and SL360 published packages?
Do I even need to distinguish them? By that I mean, since we found issues in our environment with SL360 (build 3.5) does that mean SL3 (build 3.5) will have the same issues? If this is the case, how soon until SL3 gets to build 18?!?
Thanks for any help you can provide.