You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 6
Next »
See OpenFin API documentation & Inter Op Strawman document donated by Former user (Deleted)
Please comments in the sections below, please label your comments with your name for each of identification
General Feedback on the overall structure of the API
| Name | Subject | Comment |
|---|
| Matthew Gardner | naming convention | - new-window & new-context should be changed to window-new & context-new - I know this hurts when you read it but it makes the whole thing consistent with [object]-[action]
|
| John de Murga | API equivalence | - A lot more developers would be familiar with the more comprehensive Electron API (http://electron.atom.io/docs/api/)
- The Electron API is less restrictive and we currently use it in a similar way as what is described in the interop strawman.
|
Modules
| Name | API | Comment |
|---|
| John de Murga | 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. |
| John de Murga | General | No native dialogs ? Maybe I could not find them, but this seems very basic |
| 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)) |
Classes
Feedback Inter Op Strawman
| Name | Subject | Comment |
|---|
| Matthew Gardner |
| Looks good (certainly more listed than I could think of  ) - be good to use them - that's the real test of an API - when they get used |