Thinking caps on, guys. I am trying to reduce the overall size of a folio that contains a pop-out panel (a two-state MSO) that reveals image thumbnails in a vertical scrolling content frame. Each thumbnail is a button that takes the user to another article in the folio. The panel is repeated across all articles, which is handy for the user but wasteful in file size.
In theory, I ought to be able to reduce the file size of the pages containing these panels if I was to replace the vertical scrolling content frame with a tall Web Content frame that would point to an appropriately designed HTML doc in HTMLResources.zip. This would minimise repetition of all those thumbnails.
The problem, if you haven't already guessed it, is that DPS does not allow you to link from a Web Content overlay to folio articles. The 'navto://' convention simply won't work in this scenario.
Is there ANY way to jump a Web Content frame to other locations in the folio? A non-standard, non-supported workaround would do me just fine.
Thanks for reading this far.
Ali
Ali - Check out the new "Linking" article in the Advanced Overlays issue of DPS Tips. It explains how to use an unsupported method for cross-folio linking. I explained how to create buttons with this format, but the same format would work using <a href="URL"> in HTML.
Johannes also breaks down this method here:
http://digitalpublishing.tumblr.com/post/26564811021/cross-publication -linking-bonus-qr-codes
Thanks, Bob. That's what the scripting guys have been telling us but I wasn't sure. We were hoping to replace a Scrollable Frame with web content but doing so restricts us severely on what we can trigger within the page. The only reason we're trying to do this is because DPS seems to turn Scrollable Frame content into (in my opinion) unnecessarily huge PNGs.
Ali
North America
Europe, Middle East and Africa
Asia Pacific