A panel that counts down for like 10 seconds should pop up and say 'ui.done message received. Closing app in 5..4..3.. seconds'.

There should be a cancel button displayed that makes the pop-up panel disappear.

If not cancelled, the iframe is 'closed' and a 'reload app' button is displayed in its place. When clicked, the app is reloaded.

This is a minor issue, but it would be nice if the button that says Scratchpad instead said 'Show Scratchpad' until clicked, then changed to 'Hide Scratchpad' when visible.

• Replace the 'copy to clipboard' button with a fixed position translucent button over the textarea in the upper right corner.
• Add a 'copy to clipboard' feature to the scratchpad panel.

The images must be bundles with snowpack so they can be ES6 imported in the jsx files and referenced by the image tags in the src attribute. This works locally but fails when deployed for some reason. :\

• Update screenshot here: https://barabo.github.io/swm-dd-demo/ehr-users.html
• Update screenshot here: https://barabo.github.io/swm-dd-demo/app-users.html
• Add user information in the lib/README.md
• add a note to both EHR and App dev pages regarding the process for making a change to the library (bounce npm start, npm update swm-client-lib, etc).
• [ ]

The ehr and app both use a symlink lib -> ../lib for the library import. Instead, each app should npm install the library and it should be bundled by snowpack when deployed.

Incorporate the polyfill maintained by Google:
https://github.com/GoogleChrome/dialog-polyfill

Also, there should be a button in the EHR screen to make the hidden iframe visible again.

Eliminate wasteful creation of clients in the app (and EHR) code.

scratchpad.create should add a draft resource to the scratchpad portion of the screen.

For inspiration: https://stackoverflow.com/a/50773729/280708

We need to do a better job surfacing errors in the EHR and app (don't rely entirely on the console). Consider raising exceptions and letting them be caught and logged somewhere? Show a panel when the console is logged-to?

Both the EHR and app configs should have values that survive reloads.

The EHR currently hardcodes two important configuration settings
[ ] app iframe source (which is also appOrigin)
[ ] the session handle value (which must match the app value)

The UI must expose a way to change these settings.

The UI must indicate that the message is missing a valid messaging handle.

• swm.sendMessage('customEHR.watchClicks', {...payload}) - handle a stream of responses via generator
• swm.createClient - creates a client object using the messaging handle and target origin
• client.sendMessage('status.handshake') - or any other known types. returns a promise.
• client.sendResponseTo(message) - reads the messageId and sets responseToMessageId
• use new client in app and ehr
• swm.discover() - returns library details

Use snowpack to bundle a library, and provide instructions to install it manually until it can be loaded into npm for distribution.

Add a scratchpad.read option to the app and ehr.

• for all received messages, automatically insert the matching template response if possible
• replace list of buttons with an HTML select tag
• simplify the color scheme to make it more obvious what is EHR and what is embedded app
• clicking on a button in the app should reset the response message panel
• The configuration buttons should always be statically placed in the upper right corner of the screen
• App footer does not need to be there (or maybe only for non-embedded cases)

Currently the app uses a mock SMART client object to extract the smart_web_messaging_handle and smart_web_messaging_origin launch parameters. These values are currently hardcoded in the app code, and the UI provides no way for them to changed without a code change.

There must be a way to configure the app from the UI.

In the app, when the config changes to update the messaging handle, if there is a value already in the messaging panel, it may have a different handle in the message envelope. This can be confusing to the user if a new message is not generated after updating the client. We scratched our heads over this for at least 15 minutes during the code review.

Create a new demo app for the Tutorial session that has no swm capabilities yet.

During the session, the presenter will check out the app, launch it, install the client lib with npm, then implement heartbeat and ui.done functionality.

Preferably using snowpack, publish the contents of the app and ehr to a static site host (like github pages).

One way for the client to do it would be like this:

import * as swm from 'swm-client-lib';
...
swm.enablePostMessage('http://localhost:9999', someCallback);
...
swm.disablePostMessage();

Alternatively, the client user could do this:

import * as swm from 'swm-client-lib';
...
const x = swm.enablePostMessage('http://localhost:9999', someCallback);
...
swm.disablePostMessage(x);

Not sure which I like better.

fix: app panel should be forced to the bottom of the page, right above the footer.

The scratchpad should be a thin blue bar under the EHR heading that shows the # of entries and a button to expand the contents.

When expanded, it is a modal dialog that can be closed to return to the EHR.

When the messaging handle changes, the page needs to reload so it can correctly map the messaging handle to the incoming messages. If not reloading the page, the mapping needs to be updated.

It would be helpful to have two sets of instructions for participants. One for App developers and another for Ehr developers wishing to use the tool to test their implementations.

• Create a README.md for the lib folder
• Add details to the ehr and app READMEs

Deck: https://aka.ms/swm-dd
Outline: https://hackmd.io/@msft/swm-dd21-outline/edit