3 ms·

1. The webOS app format needs to change away from the custom webOS framework (with its own directory layout etc.) to a single index.html (that can link to where

1. The webOS app format needs to change away from the custom webOS framework (with its own directory layout etc.) to a single index.html (that can link to wherever and include any resources via HTML 5 app cache). 2. First class support for IndexedDB and quota management, with performance on mobile at least an order of magnitude faster than desktop Chrome or Firefox. It may sound unthinkable but the Chrome and Firefox IDB implementations are at present rather buggy and slow. 3. Excellent Javascript interfaces to device hardware. 4. Bundler to enable any app targeting webOS device-specific apis to run natively on iPhone or Android. 5. Sell the printer division, it's distracted HP from making a technical contribution for too long already.

pacemkr 15y ago
Most of your points are already covered. 1. You could do this from day one. You didn't have to include Mojo or any other device specific framework. index.html was enough (you would also need appinfo.json for metadata and packaging.) With Enyo, even if you use the framework, there is no longer a need for any specific directory structure. 2. They have CouchDB (really not sure, it is a JSON object store though) running and accessible to all apps via a service bridge. This db is also backed up to the cloud for when user restores or changes devices. 3. Same service bridge. Which is nothing more than an AJAX call to a specific url. 4. They already run in Chrome with Enyo. With Enyo, I think this is actually possible. 5. Or keep it as a huge source of revenue. Nobody but HP's marketing dept wants webOS on printers though, I'll give you that. Think John Deere acquiring Ferrari and putting their engines into lawn mowers, because "it's the logical thing to do." I'll add 6. 6. You can write your own Node.js services that are accessible via the same service bridge mechanism. webOS is the mobile OS we should be cheering for to survive. It is slightly ahead of the curve and is about to be killed off. The news about Mozila WebAPI are an indicator.
- MatthewPhillips 15y ago
  If Enyo is open-sourced we can decouple the webos device APIs from the framework so you can plug-in the Mozilla WebAPIs or Phonegap APIs if so desired.
  - unwiredben 15y ago
    Enyo already has hooks to run on PhoneGap.
unwiredben 15y ago
I have a lot of Enyo test apps that are just an appinfo.json file, an index.html file (with the JS source in an inline script tag), and an icon file. The webOS app environment has a couple of quirks that are easily handled by a couple of calls (tell the system that the UI is ready for display). There's also no native scroller for apps, so they need to implement something like iScroll in order to show more content than fits in the on-screen card. Outside of that, HTML + JS just works.

pacemkr 15y ago

Most of your points are already covered. 1. You could do this from day one. You didn't have to include Mojo or any other device specific framework. index.html was enough (you would also need appinfo.json for metadata and packaging.) With Enyo, even if you use the framework, there is no longer a need for any specific directory structure. 2. They have CouchDB (really not sure, it is a JSON object store though) running and accessible to all apps via a service bridge. This db is also backed up to the cloud for when user restores or changes devices. 3. Same service bridge. Which is nothing more than an AJAX call to a specific url. 4. They already run in Chrome with Enyo. With Enyo, I think this is actually possible. 5. Or keep it as a huge source of revenue. Nobody but HP's marketing dept wants webOS on printers though, I'll give you that. Think John Deere acquiring Ferrari and putting their engines into lawn mowers, because "it's the logical thing to do." I'll add 6. 6. You can write your own Node.js services that are accessible via the same service bridge mechanism. webOS is the mobile OS we should be cheering for to survive. It is slightly ahead of the curve and is about to be killed off. The news about Mozila WebAPI are an indicator.

MatthewPhillips 15y ago
If Enyo is open-sourced we can decouple the webos device APIs from the framework so you can plug-in the Mozilla WebAPIs or Phonegap APIs if so desired.
- unwiredben 15y ago
  Enyo already has hooks to run on PhoneGap.

unwiredben 15y ago

I have a lot of Enyo test apps that are just an appinfo.json file, an index.html file (with the JS source in an inline script tag), and an icon file. The webOS app environment has a couple of quirks that are easily handled by a couple of calls (tell the system that the UI is ready for display). There's also no native scroller for apps, so they need to implement something like iScroll in order to show more content than fits in the on-screen card. Outside of that, HTML + JS just works.