Skip to main content
quoc_nhat_hant54573164
quoc_nhat_hant54573164
Participant
November 20, 2017
Answered

Factorize HTML5 export

  • November 20, 2017
  • 2 replies
  • 359 views

Say, i'm having over twenty modules exported in HTML5 using a same theme. Now i want to integrate them into my website.

As i can see in the source code, there is a large number of common files among those modules which i want to group into a "global" resource folder in order to reduce the size consumed.

Is there a way to realize that wish?

P/s: i saw an other question about slimming down exported modules but it wasnt answered

This topic has been closed for replies.
Correct answer quoc_nhat_hant54573164

I have created myself a solution (for my case), which i think can help anyone interested in cluster Captivate modules.

GitHub - perfectstrong/CPCluster-example: Cluster of Captivate HTML5 modules

2 replies

quoc_nhat_hant54573164
quoc_nhat_hant54573164AuthorCorrect answer
Participant
January 30, 2018

I have created myself a solution (for my case), which i think can help anyone interested in cluster Captivate modules.

GitHub - perfectstrong/CPCluster-example: Cluster of Captivate HTML5 modules

RodWard
Community Expert
RodWardCommunity Expert
Community Expert
November 20, 2017

I understand your intention, and it would make perfect sense from a web development or software development perspective.  However, Captivate is not set up to allow you to set any kind of preference that would specify a common folder for all standard files that are published each time you create an HTML5 module.

You might be able to hack into the published HTML5 and JS code to manually change all the references to these files so that they all went to the same common folder.  But honestly, I think that's way more trouble than it's worth just for the sake of reducing the clutter.

Feel free to log an enhancement request with Adobe for something like this, but don't bet on it happening any time soon.  The focus right now is more on other areas of the app.

P
petern33480613
Inspiring
November 20, 2017

quoc,

I also would like to have have this facility.

I already use global features such as CSS and Java libraries to keep standards across my work, so using a global folder for assets would fit in perfectly.

The opportunity to reduce clutter is always worthwhile, and its a standard mantra in the computer world not to duplicate data unnecessarily.

Adobe may be forging ahead with other more advanced features, but they also need to address the basic foundations of Captivate, otherwise Adobe will be building on sand.

As Rod points out, it is high unlikely you will see this in the next few years.

Good luck.

Peter

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