Hi All,
I have a query regarding the custom component/extension compatibility with the adapt framework versions.
Query: How can we ensure that the custom component which we have created compatible with all the adapt framework version? Also, what are the key things we have to keep in mind while developing the custom components and extensions which will support all the framework version.
Many Thanks,
Manish Agarwal
With (very) few exceptions*, it's not really possible to make a plugin that's compatible with all the different versions. The main reason is that the changes in Adapt v5 to the HTML/CSS were so extensive.
You could make an Adapt v3/4 compatible release (or releases) then do a v5 compatible release.
If you want to include proper accessibility support then you'll probably need different releases for v3 and v4 compatibility as accessibility support changed quite dramatically in v4. I'd be tempted to only include accessibility support for v4+ anyway as it's so much better (and easier to implement).
I don't suggest you support FW v2 - we don't actively maintain this any more. It was really only kept for those people who still wanted to support IE8/9/10 - hopefully no-one needs to do that any more! - and a few users of the authoring tool who couldn't upgrade their framework version for whatever reason.
* the keepScrollPosition extension is an example of one that is pretty much compatible with any version of Adapt (aside from this issue) as it's pure JavaScript and doesn't reference any of the Adapt HTML.
Echoing Matt's comments, don't expect to develop a single plug-in that is backwards compatible for all framework versions. As Matt implies, two versions (one for FW v3/4 and one for FW v5) will suffice for the vast majority of users. Build a version for v5 for longevity. Build a version for v3/4 for users who haven't found a way to update to v5. Let users request any other backwards-compatible versions that they need.