Skip to main content
B
Brett_Conlon
Inspiring
December 8, 2017
Answered

Converting from Glossary Widget to HTML5 alternative

  • December 8, 2017
  • 1 reply
  • 2055 views

Hiya Cappy-boffins,

I've recently been required to change tack with my eGuide project from originally exporting to exe file to now exporting to html5. Sadly, my rather large Glossary now doesn't appear because it uses the widget (Flash-based).

Aside from re-creating the whole thing manually (which would be an absolute nightmare, due to the sheer number of entries in there), is there another way I can deliver it with the least amount of labour as possible, and with the flexibility to readily update it without having to worry about re-flow issues (eg. adding a new "A" term means I have to manually push along all other entries after it)?

Does someone out there offer an HTML plug-in alternative? Can I use another software to build it then somehow integrate it into the project?

Your direction is most appreciated!

Regards,

Brett

    This topic has been closed for replies.
    Correct answer RodWard

    The WDGT file format is really just a renamed zip file.  Inside the package there can be code to support either SWF or HTML5 versions of the interaction/widget.  This is so that if you publish to SWF the SWF widget file gets used and if you publish to HTML5 then the HTML5 code gets used.

    I created a small test project and added a Glossary learning interaction (mine has the same create date from April 2017 as yours) and published out to HTML5.  Testing it locally on my PC showed that it played fine in Edge but Chrome wouldn't play it.

    However, the best way to test any HTML5 content is from a web server, so I uploaded the same files to my own web server and tested it in Chrome there and it played fine:

    http://www.infosemantics.com.au/downloads/wdgt/index.html

    1 reply

    RodWard
    Community Expert
    RodWardCommunity Expert
    Community Expert
    December 8, 2017

    As far as I am aware the Glossary widget that ships with current Captivate versions should be compatible with HTML5.  It's not ONLY for SWF.

    Which version of Captivate are you using?

    Have you tried deleting the Glossary widget from your Interactions_[version] folder and to force Captivate to download the current version?

    The Interactions folder is here for Captivate 2017:

    C:\Users\Public\Documents\Adobe\eLearning Assets\Interactions_10_0

    B
    Brett_ConlonAuthor
    Inspiring
    December 8, 2017

    Thanks for responding, Rod!

    I’m using Cp 2017

    We exported the project as HTML5 and the widget just never shows up in the page it’s sitting on.

    That’d be absolutely FANTASTIC if it could still work. At this point we won’t be delivering it from within an LMS (project is far too big and would take ages to load – besides it doesn’t require an LMS as a product eGuide, rather than formal guided training with assessments).

    I read on a similar post re: Glossary widget, that they had success when their project was imported into their LMS.

    I haven’t tried removing the Glossary widget. My current widget shows a creation date of 20th April, 2017 (do I still need to delete it?). If I delete it, how do you get it to download afresh? Does it happen automatically on launch of Cp?

    Chz,

    Brett

    RodWard
    Community Expert
    RodWardCommunity ExpertCorrect answer
    Community Expert
    December 8, 2017

    The WDGT file format is really just a renamed zip file.  Inside the package there can be code to support either SWF or HTML5 versions of the interaction/widget.  This is so that if you publish to SWF the SWF widget file gets used and if you publish to HTML5 then the HTML5 code gets used.

    I created a small test project and added a Glossary learning interaction (mine has the same create date from April 2017 as yours) and published out to HTML5.  Testing it locally on my PC showed that it played fine in Edge but Chrome wouldn't play it.

    However, the best way to test any HTML5 content is from a web server, so I uploaded the same files to my own web server and tested it in Chrome there and it played fine:

    http://www.infosemantics.com.au/downloads/wdgt/index.html

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices