P9/10

[IanMayo]

These two versions of the same document are used for operator training, focussing on the recognition and identification of features in an acoustic waterfall display.

The pages have a Java applet, configured with these params:

• URL of background image
• time axis limits
• frequency axis limits
• around a dozen other attributes

The java applet is represented as a .class file.

In order to restore this capability, one option is to convert the applet from Java to JavaScript, with an intermediary step of running a Java decompiler.

It looks-like these are the steps:

• find a way of viewing the working interactive document, maybe in IE, or maybe via an applet plugin
• decompile the .class file
• inspect the sources, determine the role of all of the attributes
• translate the Java to JS
• trial new component

[IanMayo]

It's proving challenging to learn more about
JS Component route:

• Document existing physical & logical structures, including
  • hierarchy
  • welcome bumf
  • supporting media
• Create mock structure, including:
  • gram page: title, metadata, gram, guidance
  • index page: title, grams
• duplicate pub-5
• modify structure to give each pub their own copy of templates
• duplicate pub-5 template, rename it
• strip out content from document
• update to pub-10 welcome matter
• create mock gram page, with gram-config table
• in Dita Maps / Profiling Attributes specify audience value of -trainee.
• remove harmonics and sorttable from template/page-templates-fragments/libraries/topic-page-libraries.xml
• include GramFrame.js in template/page-templates-fragments/libraries/topic-page-libraries.xml folder
• include GramFrame sources in template/resources
• introduce bare welcome metadata, grams index page, DITA doc
• trial publishing, verify GramFrame working
• develop strategy for bulk legacy data transformation