The Topic folder
Select any Topic from the publication folder and click on its folder icon in the first column. If you have selected the Hyper.Net Features publication, a good Topic to choose is 2.5 Graphics because it contains examples of embedded image objects. Your screen should look something like this:
This folder contains the elements comprising the content of the selected Topic. In this case you will find:
| |
· |
pubTOC: An XML document representing the publication's entire table of contents and its index. The current Topic within the TOC is identified for programmatic purposes.
|
| |
· |
Image files: Each image belonging to a Topic in a Rich Hypertext rendition is stored as a separate item in the topic folder. Note that all image files in a source document are converted into a Web-compatible format (JPG, PNG, GIF) in the document's Rich Hypertext rendition—even if the original image was not in a Web-compatible format.
|
| |
· |
topic: The aspx (based on the page layout Topic Structured, Topic Unstructured or Topic Binary) used to open the Topic. The aspx determines what type of topic is being displayed and presents its contents accordingly using items in the topic folder. As an example, the aspx for the Topic "2.5 Graphics" would generate an HTML file referencing the images in the topic folder.
|
To develop an even clearer understanding of how this is working, go back to the publication folder and open the Topic near the end of the list representing the PDF rendition. Your screen should look something like this:
This folder contains the elements comprising the content of the selected Topic. In this case you will find:
| |
· |
pubTOC: An XML file representing the publication's entire table of contents. The current Topic within the TOC is identified for programmatic purposes.
|
| |
· |
topic: The aspx (in this case based on the Topic Binary page layout) used to open the Topic. The aspx determines what type of topic is being displayed and presents its contents accordingly using items in the topic folder. In this case, the aspx would generate an HTML file referencing the PDF file in the topic folder. In fact, this aspx opens the PDF file directly inside the navigation environment.
|
| |
· |
PDF file: This is the actual binary PDF rendition generated by Hyper.Net.
|
| |
|
|
Note
|
Hyper.Net's sample WCMS application uses this approach to streamline its own code. You are free to access content created by Hyper.Net any way you please from within your own application. For example, you could develop a Web Part that selects a list of all PDF renditions belonging to a specific category. You do not need to work with the aspx Hyper.Net has generated in the topic folder.
|