1. User sees a listing of XLS or DOC files in the web app, stored in the web app's local storage, user clicks to open a file in a default native office application such as MS Office, and registers a "watchFile" callback to be notified of any changes to the underlying file data (when the user presses CTRL+S in the native office application), to enable syncing to the web app's local storage.
2. Web app is granted read/write access to a directory on the user's system, so that if a user opens a file in this directory from outside the web app, the web app can still watch changes made to these files to enable syncing to a backup server etc.
3. Packaged apps as complete binary installs, without requiring Chrome to be installed on the user's machine, and without requiring the user to visit a proprietary web store or sign up as a Google user. The user should not know that they are installing a packaged app. This binary would need to be able to be marketed and installed from outside of proprietary web stores if packaged apps are to be a success. i.e. a website could offer a .dmg or .exe download link depending on the platform. The app would include the Chrome updater and auto-update to track the latest packaged app apis.
It would also be a huge help if the POSIX, TCP, UDP APIs could match that of Node.js and have similar performance characteristics and capabilities (fsync etc).
1. User sees a listing of XLS or DOC files in the web app, stored in the web app's local storage, user clicks to open a file in a default native office application such as MS Office, and registers a "watchFile" callback to be notified of any changes to the underlying file data (when the user presses CTRL+S in the native office application), to enable syncing to the web app's local storage.
2. Web app is granted read/write access to a directory on the user's system, so that if a user opens a file in this directory from outside the web app, the web app can still watch changes made to these files to enable syncing to a backup server etc.
3. Packaged apps as complete binary installs, without requiring Chrome to be installed on the user's machine, and without requiring the user to visit a proprietary web store or sign up as a Google user. The user should not know that they are installing a packaged app. This binary would need to be able to be marketed and installed from outside of proprietary web stores if packaged apps are to be a success. i.e. a website could offer a .dmg or .exe download link depending on the platform. The app would include the Chrome updater and auto-update to track the latest packaged app apis.
It would also be a huge help if the POSIX, TCP, UDP APIs could match that of Node.js and have similar performance characteristics and capabilities (fsync etc).