Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Neil_Enns_-_Ado
Neil_Enns_-_AdoAccepted solution
Adobe Employee
Aug 5, 2015 8:19 PM UTC

We do not currently have support for uploading shared resources via the UI.

Neil

5 replies

Neil_Enns_-_Ado
Adobe Employee
Neil_Enns_-_AdoAdobe EmployeeAccepted solution
Adobe Employee
Aug 5, 2015 8:19 PM UTC

We do not currently have support for uploading shared resources via the UI.

Neil

Translate
jeffreyp6484616
Level 2
Aug 7, 2015 5:29 PM UTC

Does that mean no HTML overlays on INDD pages? Just .oam's? Or am I missing something basic?

Translate
Neil_Enns_-_Ado
Adobe Employee
Adobe Employee
Aug 7, 2015 5:31 PM UTC

HTML overlays work just fine on InDesign pages, as do Edge files.

Neil

Translate
Adobe Employee
Aug 7, 2015 5:36 PM UTC

In DPS folios, a lot of publishers used the HTMLResources.zip file as a way to link to PDF files so that tapping a button would display the PDF file in an in-app browser. At this time, neither shared HTML resources nor linking to PDF files is supported in DPS 2015. But as Neil pointed out, InDesign-based HTML overlays work just fine in DPS 2015.

Translate
jeffreyp6484616
Level 2
Aug 7, 2015 5:43 PM UTC

Forgive my confusion: Does this mean that for HTML overlays, the content must be hosted somewhere and is loaded remotely, instead of contained in the HTMLResources.zip file and available even when the app is used without an internet connection?

Like I say, I may be missing something basic about the workflow.


Sorry--brain fart. I was thinking all of the supporting files were in the HTMLResources.zip. Forgot that they just had to be in the folder with the index.html file.

Translate