Within the body of the visual view, you see the outline of the help content. If a topic does not have a 'target' attribute set, the text field is outlined in red, because that means it is a 'bucket', containing help topics. If it is a help topic, the text field is outlined in blue. In that case, you can right-click, click a menu item, and then the topic itself opens in the IDE, so you can edit it right away. (This is made possible by parsing the Map file, via JAXB, and then comparing the target attribute in the Map file with the target attribute in the TOC file. By the way, I assume that the Map file is in the same folder as the TOC file, and that there is only one Map file in that folder, which I think are fair assumptions.) And what if the background is yellow? That signifies a broken link! In one glance, without needing to do anything at all, I can see all the broken links! That's about as useful as a JavaHelp Editor can be.
I learned quite a lot while making this JavaHelp Editor and I hope to continue with this series tomorrow, building on from yesterday, with the screenshot above as the target. In the meantime, I'll be sure to continue developing this tool. For example, a progress bar is needed, because the JAXB parsing sometimes take a little bit of time, especially the first time round. (Thus far, not more than 5 seconds. That time could be decreased if I focus on handling the JAXB parsing more efficiently. It definitely isn't a JAXB problem, just a coding issue.) Also, currently the link check is done for a tab whenever a tab is opened; maybe that should be deferred so that the user can choose when the link check should be done. And, as before, the synchronization hasn't been done yet, so that changes to the TOC source view do change the visual view, but not the other way round. Something else is that the visual view should be organized better—for example, the "Servers" text in the screenshot above should be in the top orange-backgrounded header, while what is there currently is superfluous, since it simply repeats the text in the button. Are there other things that could be added? I'd be glad to take suggestions.