Phillipus
commented
3 years ago User hints were only ever meant to be an in-app thing. The HTML report came later and wasn't intended to support this. But I've noted this for a possible future version of the HTML report.
Feature Request 1:
A canvas has a HINT under Properties. The Hint has a Title and Content. Neither of these appear to make it into the HTML output.
I was incorrectly assuming that if I populated the Hint on a canvas within my model, it would override the default/hints/canvas_diagram.html and use hint information stored within the canvas object itself when a user clicks on the (i) of the primary HTML frame.
Use case. This hint would be helpful to orient readers on what this canvas is. I understand "Documentation" could also be used but I think Hints are a brief, more concise piece of information where documentation could be very verbose.
Is this what canvas Hints (within the properties tab of the canvas) was intended to be but never implemented?
Feature Request 2: (related to number 1)
I plan to use this to orient readers on our Home View. This view is also symbolically linked to//elements/model.html (after backing up the original model.html) so that the home canvas loads within the body of the frame when first loading the HTML site. (I'd love to see this configurable within the model but that is another feature request i think).
example: set HTML home canvas: [browse and select canvas] <-- this then alters the index.html to point to the configured view instead of the default (blank) model.html.
Thanks Scott.