See OpenFin API documentation & Inter Op Strawman document donated by Former user (Deleted)
...
General Feedback on the overall structure of the API
Name | Subject | Comment |
---|---|---|
naming convention |
| |
John de MurgaFormer user (Deleted) | API equivalence |
Should be noted that we abstract postMessage and use it to make it easier to run our apps on browser/container mode ... |
Modules
Name | API | Comment |
Former user (Deleted) | setTrayIcon | Not clear how to support more practical tray icon functionality like menus, animations and more complex events. We are used to tray icons being entities in their own right to which we can add menus and other behavior. |
Former user (Deleted) | General | No native dialogs ? Maybe I could not find them, but this seems very basic functionality |
Also need to preserve snippet tool for pulling in screenshots etc Former user (Deleted) - There are a couple of dedicated Electron modules for this. |
Name | API | Comment |
---|---|---|
Name | API | Comment |
---|---|---|
John de Murga | General | Seems like a positional wrapper around a standard sub-window, which is fine (we have one too) ... We cache and reuse hidden sub-window instances behind the scenes, would be interesting to see what OpenFin does. But we also have a native lightweight notification (think Notifications API (text) + a couple of bits (-browser window overhead)) |
Should we match the work already done in this area https://www.w3.org/TR/notifications/ Former user (Deleted) - This can (is) used by us on Electron for simple notifications ... |
Name | API | Comment |
---|---|---|
...