However, my product manager is bemoaning the loss of the index that he had in tripane. I've used HTML/CSS/Jquery (from here: http://inspirationalpixels.com/tutorial ... and-jquery) to get tabs to show either the nav-accordion (TOC) or another tab which I want to use to show the index. (doubtless when I get it working PM will want the index to be searchable which is a whole other world of pain)
However, I've put an indexProxy into the right div of the masterpage to no effect.
Indeed putting one in a standard topic isn't getting me anywhere either.
If I compile the same TOC with a target using an old-fashioned tripane HTML5 skin with an Index tab requested the Index in the skin is populated but not a topic containing an indexProxy. This leads me to think that there's something in Flare that won't allow non-skin content to have an Index generated from a proxy for HTML5 targets - but that sounds ridiculous!
For example:
Code: Select all
<?xml version="1.0" encoding="utf-8"?>
<html MadCap:lastBlockDepth="2" MadCap:lastHeight="103" MadCap:lastWidth="1069" xmlns:MadCap="http://www.madcapsoftware.com/Schemas/MadCap.xsd">
<head><title></title>
</head>
<body>
<h1><span style="font-size: 22pt;">Index</span>
</h1>
<MadCap:indexProxy />
</body>
</html>The Data/Index.js (and chunks) output files have index terms defined. I just need to get them into either a topic containing an index proxy or into the proxy I've put in a tab in my responsive.flmsp. Obviously classic HTML5 compilation does something that turns the contents of Index.js into a UL because I can see that in the top-level output file.
Anyone know how I can get that same UL into a topic?