I was describing how HyperCard was used as an authoring and runtime tool to implement one of the earliest interactive and graphical web applications.
It took a screen snapshot of the HyperCard stack, and showed you an image of it in the web browser. And you could click on the image, which would map back to a simulated click on the stack, run whatever handlers and make whatever changes to the card or stack that HyperCard was programmed to do (draw something, switch to the next page, etc), and then it would download the next screen snapshot showing the change. Also it rendered any user interface widgets (text input fields, checkboxes, dropdown menus, etc) as html form fields below the image, that you could fill out in the browser and submit, whose values were then stuffed back into the actual HyperCard control fields. So you could use HyperCard stacks over the web that created, updated, and queried HyperCard databases,
flipped between different cards and backgrounds, drew dynamic graphics, or did any arbitrarily programmed stuff like that.
It took a screen snapshot of the HyperCard stack, and showed you an image of it in the web browser. And you could click on the image, which would map back to a simulated click on the stack, run whatever handlers and make whatever changes to the card or stack that HyperCard was programmed to do (draw something, switch to the next page, etc), and then it would download the next screen snapshot showing the change. Also it rendered any user interface widgets (text input fields, checkboxes, dropdown menus, etc) as html form fields below the image, that you could fill out in the browser and submit, whose values were then stuffed back into the actual HyperCard control fields. So you could use HyperCard stacks over the web that created, updated, and queried HyperCard databases, flipped between different cards and backgrounds, drew dynamic graphics, or did any arbitrarily programmed stuff like that.