Geertjan's Blog

  • April 20, 2007

Visual View for JavaHelp Table of Contents

Geertjan Wielenga
Product Manager
The start of a visual view on top of a JavaHelp toc file:

My starting point for creating this visual view was to generate the beans for traversing the XML file. I used the generator described yesterday, of which I uploaded a new version (1.1) to the plugin portal. Several bugs are fixed. Plus, when you hover the mouse over a checkbox, you'll see a tooltip with the Schema2Beans parameter that is executed if the checkbox in question is selected. That could be quite useful. So, if you're one of the people who downloaded the Schema2Beans Generator Template yesterday, make sure you get the latest version, i.e., 1.1, because this one is better.

Once the above scenario (i.e., one that provides a visual view and, later, an editor, on top of the JavaHelp toc file) is completed, I will use it as the basis of a tutorial on the XML MultiView API. The JavaHelp toc DTD isn't very complex, but just complex enough to be interesting. Two beans are generated when you use Schema2Beans, one called Toc and the other called Tocitem. The former doesn't provide much, it is just a container for the items. The latter is where all the headers for the JavaHelp topics are found. The interesting bit is working out how to iterate through all the levels of the Tocitem, which is the main part that I'm still working on.

In other news. Because of popular demand, we will be releasing the samples for the Rich Client Programming book next week. We're just putting the pieces together at the moment. We need to be careful how we release them, because we also want to be able to provide enhancements and bug fixes and so on. Probably we will use, among other means, the Plugin Portal to distribute one big NBM file that will install the samples. An NBM file with the samples will also accompany the book.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.