Replacement for the DBI ctHtml ActiveX control (HTML viewer)¶

Project: User Interface

Problem¶

ctHtml (ctHtml.ocx 2.0) displays HTML files. Applications typically write a generated chart or gauge page to a file and call NavigateTo(file), use PrintPage, and use DocumentComplete and TitleChange as loading guards.

FWD's HTML-BROWSER renders a live iframe, navigates to a URL, loads HTML from a string and prints. In a converted system the file is written on the server, so the browser cannot load it from a local path.

Work¶

1. Map ctHtml onto HTML-BROWSER with an alias table.
2. Make NavigateTo of a server-side file work, by serving the file to the client or loading its content as a string, including the relative resources it references.
3. Map PrintPage, DocumentComplete and TitleChange.
4. Register the control's CLSID in the OCX registry (ocx-registry.xml), mapping it to the target widget, as #11919 did for ctToolBar.
5. Decode the design-time state the control keeps in the .wrx storage at conversion time, so that it exists after conversion.
6. Implement the members and events listed above on the target, with the vendor's semantics: argument types, return values, defaults, and the order in which events fire. Members of the type library that are not used become no-ops with a conversion warning, as the OCX pipeline already does.
7. Follow the OCX emulation playbook attached to #11919: an OpenEdge test program with goldens for each member and event, recorded input sequences for the interactive parts, and Lyra automation.
8. Update the gap marking and the OCX registry documentation.

Testcases¶

Each member and event above, exercised on Windows OpenEdge with the real control to produce goldens, then run against the FWD replacement on the web and Swing clients. The vendor help files are the reference where behaviour cannot be observed directly.