Points we can make when writing a paper on the Aura summer work:

1. What advice can we provide to application writers to support task-based computing? Design guidelines, desired functionality, programming model?

This would be a potential paper for SWP&E

Suggestions:

1. Restoring the window coordinates to their absolute values may not be the best choice. Consider relative coordinates, i.e. some normalization relative to the host environment.
2. Linux window managers are more complex: - concept of multiple desktops, - concept of tiles,

   How are we planning to handle these?

3. Have we tried running our code using Windows emulators on Linux, e.g. for internet explorer, office apps, etc?
4. When doing a setState, should the settings be those of the environment, i.e. settings of the application on that station, or those of the task? Should the user have some handles, via prism, to indicate which settings should prevaail? What is a reasonable set of settings to be included with the task?
5. Do we have an ability to trace user's actions during Joao's user studies, in order to mine the data and see how the user's used things.

Current Bugs, issues, etc:

1. Windows Media Player:
   • occasional, inconsistent error, stating "no suitable stream found", - opening files results in appending to the open file list,
2. Aura suppliers might not work if some Windows Services are disabled:
   • COM+ event, - some other COM / COM + thing,
3. Occasionally EM gets confused, and Prism reports: "EM communication timed out",
4. Outlook:
   • IMAP / HTTP store cleanup not handled upon deactivate,

Documents

• Yady's Suppliers
• How to write a supplier